1 min lesson
Rules are the artifact you'll coach most
Use the example in "Rules are the artifact you'll coach most" to explain the main idea in plain words.
Step 1 of 2
Rules are the artifact you'll coach most
A good rules file is concrete and short. It names the stack, the patterns the team actually enforces and the traps to avoid. Here is the shape a platform team would recognize:
An example project rule a platform team might own (.cursor/rules or .cursorrules)
# Conventions for the payments service - Language: TypeScript, strict mode. No `any` without a comment justifying it. - HTTP: use the internal `httpClient`, never raw fetch - it handles retries + tracing. - Tests: colocate as `*.test.ts`; every new handler needs a failing-path test. - Money: integer cents only. Never floats for currency. - When unsure about a domain term, check `docs/glossary.md` before inventing one.