intlayer / rules
Cursor rule863 starsChanged 13 days agoApache-2.0View on GitHub
This project uses Conventional Commits and validates every commit with commitlint (see commitlint.config.ts). Exceeding these limits will cause commit validation to fail. Any other type will be rejected by commitlint. Provide context, motivation and contrast with previous behavior. Requirements: Used for metadata such as breaking changes or issue references. Requirements:
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 repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- intlayer-angularSkill
- intlayer-astroSkill
- intlayer-backendSkill
- intlayer-bundle-optimizationSkill
- intlayer-cliSkill
- intlayer-compatSkill
- intlayer-compilerSkill
- intlayer-configSkill
- intlayer-contentSkill
- intlayer-dev-toolsSkill
- intlayer-litSkill
- intlayer-markdownSkill
- intlayer-next-jsSkill
- intlayer-preactSkill
- intlayer-reactSkill
- intlayer-remixSkill
- intlayer-remote-contentSkill
- intlayer-solidSkill
- intlayer-svelteSkill
- intlayer-usageSkill
- intlayer-vanillaSkill
- intlayer-vueSkill
- intlayer-angularSkill
- intlayer-astroSkill
- intlayer-backendSkill
- intlayer-bundle-optimizationSkill
- intlayer-cliSkill
- intlayer-compatSkill
- intlayer-compilerSkill
- intlayer-configSkill
- intlayer-contentSkill
- intlayer-dev-toolsSkill
- intlayer-litSkill
- intlayer-markdownSkill
- intlayer-next-jsSkill
- intlayer-preactSkill
- intlayer-reactSkill
- intlayer-remixSkill
- intlayer-remote-contentSkill
- intlayer-solidSkill
- intlayer-svelteSkill
- intlayer-usageSkill
- intlayer-vanillaSkill
- intlayer-vueSkill
The file
We split this commit-message-guidelines.md into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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 47
Use the imperative mood: "add", "fix", "remove", not "added" or "adding".
- Distinctive: line 48
Must be lower-case (no sentence-case, start-case, pascal-case, or upper-case).
- Distinctive: line 49
Don't capitalize the first letter beyond what's required for acronyms.
- Distinctive: line 50
Don't end with a period.
- Distinctive: line 66
Must have a blank line before the body content (warning level).
- Distinctive: line 83
Must have a blank line before the footer content (warning level).
- Distinctive: line 117
Use git commit --amend to fix a rejected message.
≈ “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
Conventional Commit Message Guidelines
This project uses Conventional Commits and validates every commit with commitlint (see commitlint.config.ts).
1. Message Format
<type>(<scope>): <subject>
[optional body]
[optional footer]<type>: one of the allowed types below (lower-case)<scope>(optional): a package, app, or general scope (lower-case, no spaces)<subject>: short description in the imperative mood, no trailing period
2. Length Restrictions
| Component | Max Length | Rule Level |
| Header (entire first line) | 100 characters | Error |
| Body (each line) | 100 characters | Error |
| Footer (each line) | 100 characters | Error |
Exceeding these limits will cause commit validation to fail.
3. Allowed Types
| Type | When to use it |
| build | Changes to build system, tooling, or external dependencies |
| chore | Routine tasks (e.g., lockfile update, minor refactor with no behavior change) |
| ci | CI configuration or scripts |
| doc | Documentation-only changes |
| feat | Introducing new features |
| fix | Bug fixes |
| perf | Performance improvements |
| refactor | Code changes that neither fix a bug nor add a feature |
| style | Code style changes (formatting, whitespace, etc.) |
| test | Adding or updating tests |
Any other type will be rejected by commitlint.
4. Subject Rules
- Use the imperative mood: "add", "fix", "remove", not "added" or "adding".
- Must be lower-case (no sentence-case, start-case, pascal-case, or upper-case).
- Don't capitalize the first letter beyond what's required for acronyms.
- Don't end with a period.
- Cannot be empty (required).
5. Scope Rules
- Optional but recommended for clarity.
- Must be lower-case (enforced by commitlint).
- Hyphen-separated if multi-word.
- Examples:
react-intlayer,backend,website,scripts.
6. Body (Optional)
Provide context, motivation and contrast with previous behavior.
Requirements:
- Must have a blank line before the body content (warning level).
- Each line must not exceed 100 characters (error level).
<type>(<scope>): <subject>
<BLANK LINE>
Detailed explanation of **what** and **why**.
Each line in the body must be 100 characters or less.
<BLANK LINE>7. Footer (Optional)
Used for metadata such as breaking changes or issue references.
Requirements:
- Must have a blank line before the footer content (warning level).
- Each line must not exceed 100 characters (error level).
<type>(<scope>): <subject>
[optional body]
<BLANK LINE>
BREAKING CHANGE: describe the breaking change here
Closes #1238. Examples
feat(core): add version comparison utility
fix(website): correct 404 layout on nested routes
chore: update lockfile
style(backend): run eslint --fix on src directory9. Quick Checklist
- Correct type from the list above (lower-case)
- (Optional) concise scope in lower-case
- Subject in lower-case, imperative mood, ≤ 100 chars total header, no period
- Body with blank line before, each line ≤ 100 chars
- Footer with blank line before, each line ≤ 100 chars, for breaking changes/issue refs
10. Validation & Automation
- The
.husky/commit-msghook runsbun exec commitlint --edit "$1". - Any deviation from the rules aborts the commit with guidance.
- Use
git commit --amendto fix a rejected message.
Following these guidelines keeps the project history clean, makes changelogs automatic, and helps everyone understand why a change exists.
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.

