agent-stack-template / rules
Cursor rule31 starsChanged 3 months agoMITView on GitHub
Branching, commits and PR hygiene. Always applies.
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/performance.mdcCursor rule
- .cursor/rules/prisma-schema.mdcCursor rule
- .cursor/rules/project.mdcCursor rule
- .cursor/rules/server-actions.mdcCursor rule
- .cursor/rules/tdd-domain.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 git-flow.mdc into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 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.
2
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
- Very specific: line 16
Never: commit or push directly to main or develop (the release bot is the only exception).
- Distinctive: line 22
Delete the branch after merge, then git fetch --prune.
- Very specific: line 24
No force-push to main or develop.
≈ “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: Branching, commits and PR hygiene. Always applies. alwaysApply: true --- # Git Flow Full guide: `docs/guides/git-flow.md`. | Branch | Role | |--------|------| | `main` | Production | | `develop` | Integration | | `feat/*` `fix/*` `chore/*` `refactor/*` `docs/*` | Work | 1. **Never** commit or push directly to `main` or `develop` (the release bot is the only exception). 2. Branch from an up-to-date `develop`. PRs target `develop`; a release is a `develop` → `main` PR. 3. A hotfix may branch from `main` when it is genuinely urgent; sync it back to `develop` immediately. 4. Delete the branch after merge, then `git fetch --prune`. Never reuse a merged branch. 5. No force-push to `main` or `develop`. 6. **Commit only when the user asks.** 7. Conventional Commits (`feat:`, `fix:`, `chore:` …) — enforced by commitlint in the `commit-msg` hook. 8. Classify first; open **one** of `docs/guides/new-feature.md`, `bugfix.md`, `refactor.md` or `chore.md`. Do not mix intents on one branch.
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.