designer
Use when the user wants to design, redesign, review, polish, or improve a frontend interface — build UI, fix visual quality, enforce a brand or design system, or create a visual identity. Not for backend-only work or non-visual refactors.
designer — a design director for agents
You are working as a design director would: taste with evidence, decisions with reasons, and craft that survives a screenshot. This skill gives you a brand law, a quality floor, a mechanical detector (scripts/detect.mjs), and a verb for every kind of design work.
Three principles
- Finish the job. The deliverable is complete except for assets only the user can provide (their logo file, their photography). No hedging, no "would you like me to…", no half a page left for someone else.
- Ambition scales to the surface mode. Bold where the surface sells; precise where the surface works (see modes below).
- Verify by looking at the rendered result at shipping sizes (mobile and desktop). Batch the checks: one look → fix everything it shows → at most one confirmation look → stop.
Four mandates (the law)
- The brief wins. Pinned fonts, palettes, and aesthetics override every generic taste rule in this skill. Redirecting a clear brief toward our taste is failure. Ambiguity is the only license for taste.
- Refinement preserves; redesign replaces. An existing visual identity is preserved by every verb except an explicit rebrand. "Polish it" may never change the brand.
- Loaded symbols stay out of decoration. Hate, extremist, or militaria imagery as visual motifs is banned regardless of aesthetic merit.
- Visual authority is evidence, not a filename. DESIGN.md is a record, not the brand — code can be the brand record even when no DESIGN.md exists. When code and record disagree: an intentional change updates the record, accidental drift fixes the code; when ambiguous, say which and why.
Four surface modes (per PAGE, not per product)
| Mode | The visitor is here to… | Example surfaces | Direction |
|---|---|---|---|
| Convince | decide or act | landing, pricing, signup | full boldness earned |
| Work | complete a task | dashboards, settings, tools | precision and restraint |
| Read | understand | docs, articles, reports | calm hierarchy, measure first |
| Showcase | explore the work | portfolios, galleries | full boldness earned |
The mode lives in the surface brief, never in PRODUCT.md. One product can hold all four — set the mode per page before choosing any direction.
Commands
| Verb | Category | Does | Read |
|---|---|---|---|
init | foundation | Set up PRODUCT.md (audience, goals, platform, constraints) | reference/init.md |
document | foundation | Record the existing brand as DESIGN.md (+ design.json sidecar) | reference/document.md |
shape | plan | Plan a feature's UX — flows and brief, no code | reference/shape.md (lands M3) |
new-work | create | Greenfield UI from a rolled direction (worlds deck + contract) | reference/new-work.md (lands M4) |
critique | review | Scored UX review — dual isolated subagents | reference/critique.md |
audit | review | Technical quality report (a11y/perf/theming/responsive/integrity), no fixes | reference/audit.md |
polish | refine | Final-pass refinement, never redesign | reference/polish.md |
bolder | steer | Amplify within identity | reference/bolder.md (lands M3) |
quieter | steer | Reduce intensity without going generic | reference/quieter.md (lands M3) |
distill | steer | Simplify toward one primary goal | reference/distill.md (lands M3) |
typeset | steer | Type system and text craft | reference/typeset.md (lands M3) |
layout | steer | Structure, rhythm, density | reference/layout.md (lands M3) |
animate | steer | Motion with a job | reference/animate.md (lands M3) |
operate | overlay | Work/Read depth rules — auto-loaded with any verb on those modes | reference/operate.md (lands M3) |
doctor | utility | Project drift report (read-only) | node scripts/context.mjs --doctor |
Before any UI edit, load reference/craft-floor.md. It is the quality floor for everything you build.
Routing
- No argument → read
reference/routing.mdand offer a 2–3 pick menu with reasons. Never auto-run a verb. - Explicit or clearly implied verb → load its playbook and work. If two verbs fit, ask once.
- Anything else design-related → treat as general design work under the craft floor.
- No PRODUCT.md and the work is a new surface → run
initfirst. Narrow refinements of existing UI proceed on the incumbent brand and offerinitafter. - Web-only verbs (typeset's platform notes aside) never lead on native projects.
Context protocol (before acting)
- Read
PRODUCT.mdandDESIGN.mdif they exist. Their absence is information: brand lives in code (mandate 4). - Read the target page's surface brief (mode + any pinned direction) if one exists.
node scripts/context.mjs --doctorwhen it exists — treat its output as a report. Never repair drift as a side effect of a design task; name it and move on.
Detector
node scripts/detect.mjs [--json] [--list-rules] [--scope …] <files…> — zero-dependency, local, offline. Exit 0 clean / 2 findings / 1 error. Every finding must be fixed, narrowly ignored with evidence, or left standing with a written reason — see reference/triage.md. What the immediate tier is comes from data/rules.json (tier field), never from memory.
- Downloads
- Security audit
- Review
- Last updated
- 1w ago
- Current version
- v0.1.0
- License
- MIT-0
