personal-finance / rules
Cursor rule1 starsChanged todayMITView on GitHub
How a change moves from an issue to a pull request: Spec Lane or Fix Lane, research first, gates, git conventions
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,243 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 repository84 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/angular-coding-style.mdcCursor rule
- .cursor/rules/angular-patterns.mdcCursor rule
- .cursor/rules/angular-security.mdcCursor rule
- .cursor/rules/angular-testing.mdcCursor rule
- .cursor/rules/common-code-review.mdcCursor rule
- .cursor/rules/common-coding-style.mdcCursor rule
- .cursor/rules/common-security.mdcCursor rule
- .cursor/rules/common-testing.mdcCursor rule
- .cursor/rules/csharp-coding-style.mdcCursor rule
- .cursor/rules/csharp-data-access.mdcCursor rule
- .cursor/rules/csharp-patterns.mdcCursor rule
- .cursor/rules/csharp-security.mdcCursor rule
- .cursor/rules/csharp-testing.mdcCursor rule
- .cursor/rules/design-design-system.mdcCursor rule
- .cursor/rules/project-backend.mdcCursor rule
- .cursor/rules/project-security.mdcCursor rule
- .cursor/rules/project-testing.mdcCursor rule
- .cursor/rules/project-web.mdcCursor rule
- .cursor/rules/typescript-coding-style.mdcCursor rule
- .cursor/rules/typescript-patterns.mdcCursor rule
- .cursor/rules/typescript-security.mdcCursor rule
- .cursor/rules/typescript-testing.mdcCursor rule
- angular-guideSkill
- break-uiSkill
- dotnet-create-command-querySkill
- dotnet-create-entitySkill
- dotnet-create-moduleSkill
- dotnet-ef-migrationSkill
- emil-design-engSkill
- frontend-designSkill
- impeccableSkill
- review-animationsSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- ui-ux-pro-maxSkill
- angular-guideSkill
- break-uiSkill
- dotnet-create-command-querySkill
- dotnet-create-entitySkill
- dotnet-create-moduleSkill
- dotnet-ef-migrationSkill
- emil-design-engSkill
- frontend-designSkill
- impeccableSkill
- review-animationsSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- The first 60 shown.
The file
We split this common-development-workflow.mdc into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- could be automatic: a setting could enforce it
- Distinctive: line 19
Search the codebase for an existing implementation or pattern and follow it.
- Distinctive: line 20
Read the current docs of the library at the version the repo pins (official docs first).
- Distinctive: line 21
Prefer a maintained library over hand-rolled utility code.
- Distinctive: line 27
Never push to main, force-push, skip hooks or merge.
≈ “Common” is an estimate: at least 1 in 5 of the 6,809 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: "How a change moves from an issue to a pull request: Spec Lane or Fix Lane, research first, gates, git conventions" globs: alwaysApply: true --- <!-- Generated by armature from core/rules/common/development-workflow.md. Edit the source rule, not this file. --> # Development workflow The repo's `AGENTS.md` is the source for its workflow; this rule is the default. ## Pick the lane - **Fix Lane** (a fix, debt, one change): acceptance criteria in the issue, a failing test, the smallest fix, the gate, a pull request. - **Spec Lane** (a feature, more than one change): spec, plan and tasks with Spec Kit in `specs/<NNN-slug>/`, citing requirement IDs. Open a draft pull request with the spec and stop until a person approves it. Then the Task Loop runs one fresh session per task, test first, until each task's gate passes. ## Before writing new code - Search the codebase for an existing implementation or pattern and follow it. - Read the current docs of the library at the version the repo pins (official docs first). - Prefer a maintained library over hand-rolled utility code; check its licence. ## Git - Short-lived `<type>/<slug>` branch, Conventional Commits (`type(scope): summary`, at most 72 characters), one logical change per commit, small pull requests with `Fixes <ISSUE-ID>` in the body. - No `Co-Authored-By` trailers, agent names or AI tool references in commits or pull requests. - Never push to `main`, force-push, skip hooks or merge. A person merges. - Details: the `git-workflow` skill. ## Decisions - A decision with non-obvious trade-offs gets an ADR in `docs/adr/` before or with the change. <!-- Adapted from affaan-m/ECC rules/common/development-workflow.md and git-workflow.md (MIT) at d2ef268; merged with Armature's Spec Lane/Fix Lane and the owner's git rules (no attribution, a person merges). -->
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

