antistrefo / rules
Cursor rule4 starsChanged 9 days agoMITView on GitHub
Never put a personal email in commits, docs, or rules
Files
--- description: Never put a personal email in commits, docs, or rules alwaysApply: true --- # No personal emails Commits, co-author trailers, docs, and rules use a GitHub noreply address: `ID+username@users.noreply.github.com` The ID is the account's numeric GitHub id. Do not read an email out of `git log`, `git config`, or a profile and copy it into a commit. Do not invent or store a personal mailbox for an author.
In this repository9 other files it gives its agents.
- .cursor/rules/architecture.mdcCursor rule
- .cursor/rules/banner.mdcCursor rule
- .cursor/rules/build.mdcCursor rule
- .cursor/rules/gate.mdcCursor rule
- .cursor/rules/layout.mdcCursor rule
- .cursor/rules/output.mdcCursor rule
- .cursor/rules/project.mdcCursor rule
- .cursor/rules/reuse.mdcCursor rule
- .cursor/rules/scope.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.