aidd-template-scale / rules
Cursor rule0 starsChanged 2 months agoMITView on GitHub
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,144 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 repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/CLAUDE.mdcCursor rule
- .cursor/rules/code-style.mdcCursor rule
- .cursor/rules/docker-compose-local.mdcCursor rule
- .cursor/rules/github-cli-pr.mdcCursor rule
- .cursor/rules/git-worktree.mdcCursor rule
- .cursor/rules/ticket-driven-workflow.mdcCursor rule
- address-pr-feedbackSkill
- agentic-e2eSkill
- close-ticketSkill
- docs-app-syncSkill
- review-dependabot-prSkill
- screen-to-specSkill
- spec-lookupSkill
- spec-to-screenSkill
- start-ticketSkill
- address-pr-feedbackSkill
- agentic-e2eSkill
- close-ticketSkill
- docs-app-syncSkill
- review-dependabot-prSkill
- screen-to-specSkill
- spec-lookupSkill
- spec-to-screenSkill
- start-ticketSkill
The file
We split this git.mdc into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
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 15
Create implementation branches with git worktree only (see git-worktree.md).
- Distinctive: line 31
Write commit messages in Japanese when the team uses Japanese PRs.
- Distinctive: line 35
Do not use git add -A. Stage files explicitly:
≈ “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
--- alwaysApply: true description: Git conventions globs: **/* --- # Git conventions ## Branch naming - `feature/<issue-number>` — features and enhancements (e.g. `feature/42`) - `fix/<issue-number>` — bug fixes - `chore/<issue-number>` — tooling, docs-only, dependency chores Create implementation branches with **git worktree** only (see `git-worktree.md`). Do not `git checkout -b` on the main working tree for ticket work. Base branch for PRs: **`main`**. ## Commit messages Conventional Commits: ``` <type>(#<issue>): <description> ``` Types: `feat`, `fix`, `refactor`, `test`, `docs`, `style`, `chore`. Example: `feat(#42): add user list API` Write commit messages in Japanese when the team uses Japanese PRs. ## Staging Do not use `git add -A`. Stage files explicitly: ```bash git diff --name-only git add path/to/file1 path/to/file2 ``` ## Pull requests - Title: `feat(#42): short summary` - Base: `main` - Body: follow [`.github/pull_request_template.md`](../../.github/pull_request_template.md) - Include `Fixes #<issue>` in the body so GitHub closes the issue on merge to `main`
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.