design-skilllisted

# Design Skill Helps a user go from "I have a workflow I keep repeating" to a Skill Claude actually loads at the right time. The two failure modes this exists to prevent: a skill with a vague description that never triggers, and a skill that tries to do too much and either over-triggers or dilutes its own instructions. **The description field is the trigger, not a summary.** Claude decides whether to load a skill by matching the task against the `description` field alone, before reading anything else. Everything in this skill is in service of getting that one field right, then keeping the body focused. ## When to use this - The user wants to create a new skill from scratch - The user has a skill that isn't triggering and wants to fix it - The user wants feedback on a skill's description or scope before adding it Do NOT use this to fix a bug in a skill's instructions once it's already triggering correctly and producing the wrong output — that's a normal edit (see the fix-loop in step 5), not a full design pass. ## Process ### 1. Ask for the trigger condition and the workflow, in one batch Don't start drafting. Ask the user (batched, not one at a time): - **When should this fire?** What request, phrasing, or situation should cause Claude to load it? Ask for 2-3 example phrasings the user would actually type. - **What does it produce or apply?** A format, a checklist, a standard, a transformation — name the concrete output. - **What makes it distinct?** If there's