← ClaudeAtlas

patternlisted

Design creation: subject-grounded direction with HTML previews, tokens, states, voice → the project DESIGN.md. Triggers: 'pattern', 'design system', 'make it look good'.
dyasnurhakim/smithy-claude · ★ 0 · Testing & QA · score 67
Install: claude install-skill dyasnurhakim/smithy-claude
# Pattern — Design Creation (The patternmaker shapes the form before anything is cast. UI built without a pattern comes out template-shaped.) Read `${CLAUDE_PLUGIN_ROOT}/references/creed.md` and `${CLAUDE_PLUGIN_ROOT}/references/memory.md` first. Resolve memory first: `export SMITHY_MEM="$(bash ${CLAUDE_PLUGIN_ROOT}/scripts/paths.sh mem)"` — every smithy path below is relative to it, and it need NOT be inside the repo. If that dir does not exist, bootstrap per `${CLAUDE_PLUGIN_ROOT}/references/memory.md` § Location. Log: `bash ${CLAUDE_PLUGIN_ROOT}/scripts/ledger.sh append pattern <slug-or-'-'> design STARTED -` Output: `$SMITHY_MEM/DESIGN.md` — the project's design source of truth, consumed by blueprint/forge briefs for UI tasks, judged against by master-uiux and `/smithy:burnish`. ## Checklist (create a todo per item) 1. Understand the product, audience, and brand intent (ask, don't assume) 2. Propose 2–3 distinct directions with visual previews; user picks 3. Define the full system (tokens, type, states, motion, voice) 4. Write DESIGN.md + final preview; user approves 5. Log + tell consumers Adopt the `master-designer` persona (`${CLAUDE_PLUGIN_ROOT}/references/personas/masters/designer.md`) for the design thinking in this skill — its default-test and calibration bind here. ## 1. Understand Read the spec/README; look at any existing UI. Then ask (batched, with evidence-derived defaults): who uses this and in what context; three brand adjectives ("calm, clinical, tr