Anima / rules
Cursor rule1k starsChanged 5 months agoApache-2.0View on GitHub
Keep every change tightly scoped to the requested goal. Solve the target problem completely, but do not let the task expand into unrelated cleanup, redesign, or opportunistic refactoring. You may extend scope slightly only when the additional work is: Do not expand scope just because you noticed: Ask internally: If not, leave it alone. A task is better completed with a focused, safe, reviewable diff than with a large diff that tries to improve everything.
We split this Change-Scope-Control.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 5
Keep every change tightly scoped to the requested goal.
- Distinctive: line 15
Avoid unrelated renames, formatting sweeps, moves, or cleanups.
- Distinctive: line 16
Avoid changing code that is not necessary for correctness, integration, validation, or compatibility.
- Distinctive: line 17
Do not introduce new dependencies unless required.
- Distinctive: line 31
Do not expand scope just because you noticed:
- Distinctive: line 49
If not, leave it alone.
≈ “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
--- alwaysApply: true --- Keep every change tightly scoped to the requested goal. ## Core rule Solve the target problem completely, but do not let the task expand into unrelated cleanup, redesign, or opportunistic refactoring. ## Scope rules - Implement the smallest sufficient change that correctly solves the task. - Fix directly related issues when needed to make the solution complete. - Avoid unrelated renames, formatting sweeps, moves, or cleanups. - Avoid changing code that is not necessary for correctness, integration, validation, or compatibility. - Do not introduce new dependencies unless required. ## Allowed scope expansion You may extend scope slightly only when the additional work is: - necessary to complete the task correctly - needed to prevent an obvious regression - required for compatibility - required to keep tests or builds passing - small, low-risk, and directly adjacent to the same root cause ## Disallowed scope expansion Do not expand scope just because you noticed: - old code you dislike - naming inconsistencies - possible future improvements - architectural ideas unrelated to the request - broad style issues - unrelated technical debt ## Before making extra changes Ask internally: - Is this required for the requested outcome? - Is it required for correctness or compatibility? - Is it required for validation to pass? - Is it directly tied to the same root cause? If not, leave it alone. ## Completion rule A task is better completed with a focused, safe, reviewable diff than with a large diff that tries to improve everything.
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 repository31 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/Architecture-Guardrails.mdcCursor rule
- .cursor/rules/Branch-And-Commit-Workflow.mdcCursor rule
- .cursor/rules/Changelog-And-Versioning-Discipline.mdcCursor rule
- .cursor/rules/Community-Standards-And-Contributor-Experience.mdcCursor rule
- .cursor/rules/Continuous-Execution-Until-Done.mdcCursor rule
- .cursor/rules/Dependency-And-Interface-Safety.mdcCursor rule
- .cursor/rules/Docs-And-Runbook-Sync.mdcCursor rule
- .cursor/rules/English-First-Engineering-Workflow.mdcCursor rule
- .cursor/rules/GitHub-MCP-Available.mdcCursor rule
- .cursor/rules/License-And-Dependency-Compliance.mdcCursor rule
- .cursor/rules/Migration-And-Backward-Compatibility.mdcCursor rule
- .cursor/rules/Open-Source-Contribution-Workflow.mdcCursor rule
- .cursor/rules/Pull-Request-Readiness-And-Reviewer-Hygiene.mdcCursor rule
- .cursor/rules/Repo-Navigation-And-Module-Ownership.mdcCursor rule
- .cursor/rules/Secrets-And-Environment-Safety.mdcCursor rule
- .cursor/rules/Self-Install-Tools-And-MCP-When-Necessary.mdcCursor rule
- .cursor/rules/Test-First-For-Bugs-And-Regression.mdcCursor rule
- .cursor/rules/Verification-And-Regression-Checks.mdcCursor rule
- custom_skill_bde0cedaSkill
- custom_skill_f4b0b238Skill
- your-skill-nameSkill
- Workday 8AM Smart Speaker WakeupSkill
- air_conditionerSkill
- air_purifierSkill
- coordinatorSkill
- device_discoverySkill
- humidifierSkill
- lightSkill
- skill_creatorSkill
- speakerSkill
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.

