Files
standards/adapters/claude/commands/design.md
T
Keysat 7f3b007e1a Add existing-repo on-ramp and Phase-D learning loop to /design
- Phase 0 routes a run by situation: refine / import prior guidelines
  (Case A) / extract the de-facto design from organic UI (Case B) / fresh,
  plus a document-as-is vs redesign posture. Lets /design backfill repos
  that grew a look organically, not just scope new ones.
- Phase D promotes generalizable PROCESS learnings back into this guide —
  harvested from both the pre-flight scoping conversation and the Phase-C
  distillation — with a Field notes section that accretes them. Brand facts
  stay in the repo's DESIGN.md; process knowledge improves the global standard.
- Seed Field notes with research-verified Claude Design export facts.
2026-06-16 10:48:03 -05:00

27 lines
1.7 KiB
Markdown

---
description: Design round-trip — establish a look (scope fresh inspiration-first, import prior guidelines, or extract the de-facto design from existing code), optionally round-trip through Claude Design in the cloud, then distill the result into the repo's durable design/ contract (DESIGN.md + DTCG tokens)
argument-hint: [optional: the surface to design, e.g. "landing page", or "backfill"]
allowed-tools: Bash, Read, Edit, Write, Grep, Glob, Agent
---
Run the design round-trip for this repo's user-facing interface — a fresh design, or
backfilling an existing repo by importing prior guidelines or extracting its as-built look.
Optional surface/mode from me (may be empty): $ARGUMENTS
Your complete orchestration guide — the `design/` folder contract, the inspiration-first
scoping conversation, the cloud-tool hand-off runbook, and how to distill the result back
into the repo — is at:
~/Projects/standards/guides/design.md
Read it in full first, then follow it exactly. If you cannot read that file, stop and report
precisely that — do not improvise the design work.
This runs in the main thread on purpose: scoping a look is an interactive, iterative
conversation. Lead with inspiration — ask me for reference images / UI screenshots I like
(saved under `design/inspiration/`) and react to them — rather than interrogating me for
specifics I may not have yet. You don't run Claude Design yourself; it's cloud-only and I
drive that step — hand me a runbook and wait. The repo's durable contract is
`design/DESIGN.md` + `design/tokens.tokens.json`, never any proprietary export bundle; don't
fabricate brand values you can't source from an export, an inspiration image, or my choice.