
Project rules that stop Cursor from inventing bad architecture
Empty rules plus “build me X” is how Cursor invents a package your repo does not have. Project rules are the fence. Here is what I actually put in them on client work.
Hi, I'm Aris Setiawan. Cursor Ambassador in Indonesia. I build Next.js, WordPress, and AI products for teams worldwide — and coach developers on practical Cursor workflows. 13+ years.
Experience
13+ Years
Projects
50+ Delivered
Location
Indonesia

Next.js, WordPress, AI features, and performance work — shipped to production, remote-friendly.
Build blazing-fast React applications with server-side rendering, static generation, and modern web architecture.
Custom themes, plugins, and headless WordPress solutions for scalable content management systems.
Enterprise-grade PHP applications with Laravel, custom APIs, and database architecture.
Audit, analyze, and optimize your web applications for Core Web Vitals and user experience.
Mentoring, Cursor workflows, and community learning for teams and builders who want to ship faster with AI.
13+ years building scalable web products for startups, agencies, and enterprises.
Named collaborators include Hongkiat, SAB Digital, Raja Kreatif, and Ta-Wan.
Cursor Ambassador Indonesia and MiniMax Dev Community Expert.
Remote-first workflow with clear communication and timely delivery.
Previously worked with
Technical articles, tutorials, and thoughts on web development.

Empty rules plus “build me X” is how Cursor invents a package your repo does not have. Project rules are the fence. Here is what I actually put in them on client work.

Chat answers. Composer edits files. I mix them up when I am tired, and the PR pays for it. Here is when I use each on client work.

Effective Cursor use is not a greenfield demo. It is a messy client repo: monorepo, local conventions, folders you must not touch. Here is how I scope, rule, and review so the PR still looks like the codebase a month later.