agent-stack-template / rules
Cursor rule31 starsChanged 3 months agoMITView on GitHub
TDD contract for business logic
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,187 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/react-hook-form/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/git-flow.mdcCursor rule
- .cursor/rules/performance.mdcCursor rule
- .cursor/rules/prisma-schema.mdcCursor rule
- .cursor/rules/project.mdcCursor rule
- .cursor/rules/server-actions.mdcCursor rule
- .cursor/rules/ui-design-system.mdcCursor rule
- better-auth-best-practicesSkill
- better-auth-security-best-practicesSkill
- changelog-automationSkill
- frontend-designSkill
- interface-designSkill
- marketing-psychologySkill
- organization-best-practicesSkill
- react-hook-formSkill
- shadcnSkill
- vercel-react-best-practicesSkill
The file
We split this tdd-domain.mdc into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
No mocks. If a rule needs the clock, a random value or a database row, that input is a parameter — this is what keeps the domain testable.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
--- description: TDD contract for business logic globs: src/domain/**/*.ts,src/features/**/domain/**/*.ts alwaysApply: false --- # TDD — business logic Red → green → refactor. The test comes first, and it must fail for the right reason before you write the implementation. ## Tested - `src/domain/**` - `src/features/*/domain/**` - Any pure calculation or invariant ## Not tested React components, styles, layout, snapshots. A snapshot test of a component is a maintenance cost with no signal — do not add one, even "for coverage". ## Writing the test - One behaviour per `it`, named as the rule it protects, not as the function it calls: `"rejects a duplicate name regardless of casing"`, not `"works"`. - Assert on the error *type* from `src/domain/errors.ts`, not on the message — copy changes, semantics do not. - Cover the boundary, not just the happy path: empty input, the limit itself, one past the limit, and the case that must be rejected. - No mocks. If a rule needs the clock, a random value or a database row, that input is a parameter — this is what keeps the domain testable. ## Full workflow `docs/tdd-workflow.md`.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.