forklift / rules
Cursor rule211 starsChanged 27 days agoApache-2.0View on GitHub
Keep code changes and commits small, simple, and focused.
We split this minimal-changes.mdc into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 14
keep all code changes and commits short and straight forward
- Distinctive: line 19
Keep it simple: no extra helpers, wrappers, or layers unless reuse or clarity clearly needs them.
- Distinctive: line 20
Prefer inline over a named helper.
- Distinctive: line 21
No drive-by refactors, renames, or formatting outside the lines you touch.
- Distinctive: line 33
Keep each commit focused on one logical change with a short, direct message.
- Distinctive: line 41
If yes to the last two, simplify further.
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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: Keep code changes and commits small, simple, and focused. alwaysApply: true --- # Minimal Changes Apply these principles to every change in this repository. ## Core rules - I want the changes to be as small as possible - as simple as possible, don't create many unnecessary functions - keep all code changes and commits short and straight forward ## Size and shape - Smallest correct diff: change only what the task needs. - Keep it simple: no extra helpers, wrappers, or layers unless reuse or clarity clearly needs them. - Prefer inline over a named helper. - No drive-by refactors, renames, or formatting outside the lines you touch. - Short, focused commits; one logical change each. ## Code 1. **Smallest correct diff** — Change only what the task requires. No drive-by refactors, renames, or formatting outside touched lines. 2. **Solve inline** — Prefer editing existing code over new helpers, wrappers, or abstractions. Add a function only when reuse or clarity clearly demands it. 3. **Match the file** — Follow naming, types, and patterns already in the surrounding code. 4. **Skip noise** — No extra comments, tests, or docs unless requested or required for the fix. ## Commits Keep each commit focused on one logical change with a short, direct message. For commit format and Jira linking, use the git-commit skill. ## Before finishing - Can anything be removed and still solve the problem? - Would a reviewer ask why unrelated lines changed? - Is there a helper that could be three inline lines instead? If yes to the last two, simplify further.
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 3,978 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 repository2 other files it gives its agents.
- git-commitSkill
- grill-meSkill
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.