software-development-sketch

# Sketch Use this skill when the user wants to **see a design direction before committing** to one — exploring a UI/UX idea as disposable HTML mockups. The point is to generate 2-3 interactive variants so the user can compare visual directions side-by-side, not to produce shippable code. Load this when the user says things like "sketch this screen", "show me what X could look like", "compare layout A vs B", "give me 2-3 takes on this UI", "let me see some variants", "mockup this before I build". ## When NOT to use this - User wants a production component — use `claude-design` or build it properly - User wants a polished one-off HTML artifact (landing page, deck) — `claude-design` - User wants a diagram — `excalidraw`, `architecture-diagram` - The design is already locked — just build it ## If the user has the full GSD system installed If `gsd-sketch` is available as a sibling skill, prefer it for the full workflow: persistent `.planning/sketches/` with a manifest, frontier analysis, consistency audits across past sketches, and integration with the rest of GSD. This skill is the lightweight standalone version for one-off sketching without that state machinery. ## Core method ``` intake → variants → head-to-head → pick winner (or iterate) ``` ### 1. Intake (skip if the user already gave you enough) Before generating variants, get three things — one question at a time, not all at once: 1. **Feel.** "What should this feel like? Adjectives, emotions, a vibe." — *"...