From meta
Scaffold a new .mdc Cursor rule with correct type and frontmatter, and check whether it should be a skill instead. Use when adding or restructuring a rule.
How this skill is triggered — by the user, by Claude, or both
Slash command
/meta:rule-authorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Capturing a persistent constraint or convention as a rule.
Capturing a persistent constraint or convention as a rule.
A rule is a standing constraint that should color behavior with no steps to run ("never alter a column type in place"). If it's a procedure with a beginning and end, use skill-author instead. If it's genuinely cross-tool baseline behavior (stack, voice, naming), put it in AGENTS.md, not an .mdc.
| Want | alwaysApply | description | globs |
|---|---|---|---|
| Always on (use sparingly) | true | — | — |
| Auto-attach on matching files | false | — | ["glob"] |
| Agent pulls in when relevant | false | required, specific | omitted |
Manual via @mention | false | omitted | omitted |
description is required for agent-requested rules and drives selection — make it specific.
@path) instead of pasting code that will go stale.cursor-rule entry to registry.json. 5. Run loadout doctor.skill-author, learning-from-chatsexternal-practicesnpx claudepluginhub naffis/loadout --plugin metaProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.