Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lord1egypt/sketch
Throwaway HTML mockups: 2-3 design variants to compare.
Passed 13 of 22 test cases with the skill, and 11 of 22 without it.
and 1 more in the full report
4 fixed9 passed either way7 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to explore UI directions for a mobile fitness tracker summary screen. I haven't given you any details on tone, references, or core user goal yet. How should we start?
| Checked | Without skill | With skill |
|---|---|---|
| Asks for the desired visual feel as the single first question rather than prompting for all intake details simultaneously. | Missed | Passed |
The instructions your model reads when the skill loads.
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".
claude-design or build it properlyclaude-designexcalidraw, architecture-diagramIf gsd-sketch shows up as a sibling skill (installed via npx get-shit-done-cc --hermes), prefer gsd-sketch for the full workflow: persistent .planning/sketches/ with MANIFEST, frontier mode analysis, consistency audits across past sketches, and integration with the rest of GSD. This skill is the lightweight standalone version — one-off sketching without the state machinery.
intake → variants → head-to-head → pick winner (or iterate)
Before generating variants, get three things — one question at a time, not all at once:
Reflect each answer briefly before the next question. If the user already gave you all three upfront, skip straight to variants.
Produce 2-3 variants in one go. Each variant is a complete, standalone HTML file. Don't describe variants — build them. The point is comparison.
Each variant should take a different design stance, not different pixel values. Three good variant axes:
test cases passed, vs 11 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.