| name | dev.shortcuts |
| description | Mandatory shortcut trigger and usage guidance. ALWAYS check if shortcut applies before responding to ANY coding or development request. |
Context
Shortcuts are a small self-contained workflow that can be triggered via the keywords @shortcut:[shortcut] or trigger:[shortcut]
Shortcut Location
Shortcuts can be in the following locations
- Under shortcuts under skills directory
- Inlined in agent instructions under
## Shortcuts. Shortcut is header text. Can be followed by a space with argument hints enclosed in [arg_name]
Examples
## Shortcuts
### Foo [arg1] [arg2]
Invokes a foo with [arg1] and [arg2]
Shortcut Trigger and Usage
Any @shortcut:[shortcut] or trigger:[shortcut] invokes a shortcut and resolves either to the file with the same name in ./references/shortcuts/[shortcut].md or inlined in the agent instruction.
If the user asks to promote a shortcut to a skill, use @shortcut:promote-shortcut-to-skill.md.
If a shortcut doesn’t resolve, quickly scan the most relevant skill for similarly-named shortcuts before doing broader repo-wide searches.
Shortcut Chaining
This involves using multiple shortcuts in sequence. Shortcut chaining is denoted by [shortcut1] -> [shortcut2]
Example:
@shortcut:precommit-process.md -> @shortcut:create-pr.md
Mandatory Check Protocol
- Scan shortcuts in the
./shortcuts folder.
- If a shortcut matches -> Announce: "Using [shortcut name]"
- Follow the shortcut exactly
This is NOT Optional
If a shortcut exists for your task, you must use it.
Do not rationalize skipping it.
Common rationalizations to avoid:
- "This is simple, I don't need a shortcut" -> WRONG. Use the shortcut.
- "I know how to do this" -> WRONG. The shortcut may have steps you'll forget.
- "The user didn't ask for a shortcut" -> WRONG. Shortcuts are mandatory when applicable.
- "The shortcut is overkill" -> WRONG. Shortcuts ensure consistency and quality.
