Menú
Describes how to use abilities. Read before any conversation.
IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
Use when implementing user interfaces or user experiences - guides through exploration of design variations, frontend setup, iteration, and proper integration
Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.
Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts
Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
| name | using-skills |
| description | Describes how to use abilities. Read before any conversation. |
After you've read a ability with Read tool, announce you're using it:
"I've read the [Skill Name] ability and I'm using it to [what you're doing]."
Examples:
Why: Transparency helps your human partner understand your process and catch errors early. It also confirms you actually read the ability.
Many abilities contain rigid rules (TDD, debugging, verification). Follow them exactly. Don't adapt away the discipline.
Some abilities are flexible patterns (architecture, naming). Adapt core principles to your context.
The ability itself tells you which type it is.
