Cursor AI Indonesia: how I teach teams to ship with AI

Cursor AI Indonesia, for me, is not a feature tour. It is teaching teams a shipping practice they can repeat on Monday without me in the room.

I get asked for demos of Chat, Composer, and whatever shipped last week. Those demos look fine. They do not stick. The team still pastes a vague prompt, merges a diff nobody read, and calls it AI adoption. I want the opposite: one real repo, a short project rule, a review habit, and a stop when the loop is owned.

I’m Aris Setiawan. I run madebyaris from Sidoarjo, Indonesia. I have been shipping web work for 13+ years. I was the first Cursor Ambassador in Indonesia, and after SpaceXAI acquired Cursor I am a SpaceXAI ambassador. I am also a MiniMax Dev Community Expert. I teach Cursor workflows. This URL is Level up mentoring.

If you want the deeper how-to on the editor itself, start with my Cursor AI workflow for production. This post is the door: how I teach teams here, and where that teaching lives on the site.

What I teach

I do not start with a slide of every button. I start with four named steps. If a session cannot name those four by the end, we did not teach. We performed.

I have sat with teams that already bought seats and still shipped the same vague prompts. The fix was never another shortcut cheat sheet. It was putting one ticket on a real branch and refusing to move on until the review habit showed up in the PR.

One real repo. Not a toy sandbox. The product they already ship, or the next ticket on that product. If the practice never touches the real tree, it will not survive the first busy week.

Project rules. One short rule checked into the repo. What the agent may touch. What it must not invent. How we name a stop. I have written about project rules elsewhere. Here the point is simpler: a rule the team can point at when a diff goes sideways.

Review the diff. Before merge. File by file. Leftover util, second type file, a folder that does not exist elsewhere. Same instinct as a careful PR review. The model proposed. A human still owns the merge.

Stop when the loop is owned. The goal is not “more AI.” The goal is a team that can open a ticket, set the context, read the result, and ship without waiting for another workshop.

That is the whole loop. One repo. One rule. One review habit. I repeat it until someone on the team can teach it back without reading my notes.

I do not grade people on how many features they can name. I grade the first PR after the session. If the rule is ignored and the diff is unread, we schedule another pass on the same loop. We do not add a fifth shiny tool to cover the gap.

What I refuse

This is the part that keeps Cursor AI Indonesia from turning into theater.

Tool dump workshops. A two-hour tour of every panel is entertainment. It is not a practice. If the session ends and nobody can name the rule or the review step, we wasted the afternoon.

Blending mentoring with Build hire. Level up is mentoring. Build is product work on a different door. I do not sell a hire inside a teaching session, and I do not pretend mentoring is a free scoping call for a build. Different offers. Different URLs.

Metric theater. I will not invent student counts, team sizes, or case studies to make this page look louder. If I cannot name the proof, I leave the number out.

I also refuse to chase every new model announcement as the curriculum. Models change. The shipping loop does not. Teach the loop first.

The Level up door

This URL exists so people searching Cursor AI Indonesia find a mentoring path, not another generic how-to stacked on top of the pillar.

The commercial door is Vibe Code Friend. That is Level up: Cursor mentoring, workflows, the practice above. If you want product builds (Next.js, WordPress, AI wiring), that is a different offer on a different page. I keep them apart on purpose.

I also keep a public note on the ambassador path at Cursor Ambassador. Useful context. Not a substitute for the mentoring door.

If your team is in Indonesia, or remote and shipping with Cursor, and you want the practice owned, start at Vibe Code Friend. Bring one real repo and the ticket you care about. We will set the rule, review the first diffs together, and stop when your team can run the loop without me.

For the editor-side craft, keep Cursor AI workflow for production open next to this page. This one is the door. That one is the practice depth.