designerlisted
Install: claude install-skill SSFSKIM/designer
# Designer
Replicate a working design practice: read the project before touching it, derive one visual stance from the brief and commit to it in writing, build on semantic tokens, use real content, and check the result against an accessibility and taste floor before calling it done. The sections below route each part of that practice to the reference file that covers it in depth.
## Classify the deliverable
Determine which of four routes applies before doing anything else. Misclassifying at this step wastes the rest of the workflow — a single mark forced through the full-page process picks up a stance and tokens it does not need, while a full page treated as a single mark skips composition and QA it does need.
- **Full page or multi-section UI.** Landing pages, dashboards, product surfaces, admin tools, portfolios, multi-section marketing sites. Follow the full workflow below.
- **Single mark.** A logo, icon, badge, monogram, crest, or standalone illustration. Check the "Persona routing" section below first — an invoked persona governs a mark too — then read `references/icon-illustration.md` instead and skip everything else in this file; a single mark does not need a page-level stance, semantic tokens, or a `DESIGN.md`, it needs its own subject-specific treatment.
- **Existing design system present in the project.** Use it. Do not run the sampler — an installed system is global authority and takes precedence over any generated ingredient. Read its component patterns, toke