antigravity-kit / rules
Cursor rule50 starsChanged 10 months agoMITView on GitHub
We split this coding-style.mdc into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Use descriptive variable and function/const names.
- Distinctive: line 9
Avoid adding unnecessary comments to the code of your generated code.
≈ “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 --- - Type safety first: Prefer TypeScript with explicit types on public functions, props, and return values. Avoid any and implicit any. - Guard clauses over nesting: Use early returns and guard clauses instead of deeply nested if/else blocks; keep branches short and readable. - Use descriptive variable and function/const names. Also, event functions should be named with a "handle" prefix, like "handleClick" for onClick and "handleKeyDown" for onKeyDown. - Clear naming & structure: Use descriptive, consistent names (camelCase for variables/functions, PascalCase for components) and keep related logic grouped in hooks/, utils/, components/. - Avoid adding unnecessary comments to the code of your generated code. - Small, pure units: Write small, single-purpose functions/components. Keep them pure when possible and move side effects (API calls, logging) to the edges. - Refactor: Use the refactor command to improve the code quality without breaking existing functionality. Do not use it for simple code improvements.
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 repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/git.mdcCursor rule
- .cursor/rules/toc.mdcCursor rule
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.