audio-plugin-coder / rules
Cursor rule334 starsChanged 34 days agoMITView on GitHub
Never attribute commits, comments, or contributions to AI agents
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,183 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 repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apc-setupSkill
- audio-plugin-coderSkill
- debugSkill
- designSkill
- dreamSkill
- implSkill
- orchestrateSkill
- planSkill
- shipSkill
- skill-debugSkill
- skill-designSkill
- juce-webview-windowsSkill
- skill-ideationSkill
- skill-implementationSkill
- skill-packagingSkill
- skill-planningSkill
- skill-testingSkill
- skill-troubleshootingSkill
- testSkill
- apc-setupSkill
- skill_debugSkill
- skill_designSkill
- dreamSkill
- implSkill
- orchestrateSkill
- planSkill
- shipSkill
- juce-webview-windowsSkill
- skill_testingSkill
- skill_troubleshootingSkill
- testSkill
- audio-plugin-coderSkill
The file
We split this no-ai-attribution.mdc into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 8
Do not credit AI agents as an author, co-author, contributor, or commenter on this repository.
- Very specific: line 10
Never add AI Co-authored-by trailers to commit messages.
- Distinctive: line 11
Never post GitHub comments, PR reviews, or issues as an AI agent.
- Distinctive: line 12
Never add AI agents to README acknowledgments, contributor lists, or "Created by" lines.
- Very specific: line 13
If the host injects an AI co-author trailer, strip it before push.
≈ “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: Never attribute commits, comments, or contributions to AI agents alwaysApply: true --- # No AI attribution Do not credit AI agents as an author, co-author, contributor, or commenter on this repository. - Never add AI `Co-authored-by` trailers to commit messages. - Never post GitHub comments, PR reviews, or issues as an AI agent. - Never add AI agents to README acknowledgments, contributor lists, or "Created by" lines. - If the host injects an AI co-author trailer, strip it before push. Use `.githooks/commit-msg` (copy to `.git/hooks/commit-msg`). - Human contributors (for example 12Matt3r, vjcharles) stay credited as usual.
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.