design-md-workflowlisted

# DESIGN.md Workflow Use this skill when a project needs a durable, agent-readable visual identity that survives across sessions, agents and implementation passes. Google Labs' `DESIGN.md` project defines an alpha format that combines machine-readable design tokens in YAML front matter with human-readable design rationale in Markdown. Agentit treats that format as an **optional current external contract**, not a global dependency and not a replacement for the project's real source-of-truth design system. ## When to load Load when one or more are true: - a project already contains `DESIGN.md`; - a greenfield/redesign task needs a durable visual identity for future agents; - Figma/design tokens exist but the coding-agent handoff lacks concise project-level rationale; - several sessions/agents keep drifting in typography, color, spacing, radii or component styling; - a design-system change needs a reviewable token/rationale diff. Do **not** load for a one-off tiny UI edit where the existing component system already answers the visual question. ## Authority order Before writing or applying `DESIGN.md`, identify the real source of truth. Typical authority order: ```text explicit user/brand requirements -> existing production design system / tokens / Figma source -> canonical DESIGN.md when intentionally maintained -> project components/styles -> external design references -> model preference ``` If `DESIGN.md` conflicts with production tokens or an explicitly authoritat