skills / rules
Cursor rule1 starsChanged 48 days agoApache-2.0View on GitHub
Skills must not name specific clients or accounts
We split this no-client-names.mdc into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 11
Use placeholders: <account_id>, <parent_account_id>, <prefix>, engine9-accounts/<org>/<account>/export.
≈ “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
--- description: Skills must not name specific clients or accounts globs: "**/*.md" alwaysApply: true --- # No client names in skills Public skills are product documentation. Do not name specific **clients** or **accounts**. Use placeholders: `<account_id>`, `<parent_account_id>`, `<prefix>`, `engine9-accounts/<org>/<account>/export`. Fine to name: engine9 product terms, plugin/vendor integrations (paths, `plugin_id`), and table/column identifiers. ``` # ❌ BAD e9 exportworker export -a liftoff \ --definition_path=engine9-accounts/frakture/liftoff/hockeystick/export Email bundles (Hockeystick) typically ship EMAIL_* stores. # ✅ GOOD e9 exportworker export -a <account_id> \ --definition_path=engine9-accounts/<org>/<account>/export Email-oriented bundles typically ship EMAIL_* stores. ```
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 repository24 other files it gives its agents.
- .cursor/rules/skill-writing-standard.mdcCursor rule
- create-engine9-pluginSkill
- e9-api-keySkill
- e9-cliSkill
- e9-custom-fieldsSkill
- e9-delegate-domainSkill
- e9-dev-tasksSkill
- e9-eqlSkill
- e9-exportSkill
- e9-funnelSkill
- e9-global-messageSkill
- e9-inputSkill
- e9-inventorySkill
- e9-mcpSkill
- e9-modelSkill
- e9-person-idSkill
- e9-person-remoteSkill
- e9-pii-freeSkill
- e9-pluginSkill
- e9-reportsSkill
- e9-source-codeSkill
- e9-tasks-apiSkill
- e9-timelineSkill
- e9-upgradeSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.