grant/standards
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add existing-repo on-ramp and Phase-D learning loop to /design

Browse Source 
- 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.
This commit is contained in:
Keysat
2026-06-16 10:48:03 -05:00
parent bb27e4c32a
commit 7f3b007e1a
2 changed files with 153 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files
adapters/claude/commands/design.md
+5 -4
View File
@@ -1,11 +1,12 @@
---
description: Design round-trip — scope a look interactively (inspiration-first), hand a well-formed brief to 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 "settings screen"]
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.
Optional surface from me (may be empty): $ARGUMENTS
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