design-system-governancelisted

# Govern Product Design Treat design as an implementation contract, not final-stage decoration. Reuse an existing approved system before proposing a new one. ## Respond in the user's language Detect the user's language from their messages and use it for all prose addressed to them: questions, explanations, recommendations, status, and the closing summary. Keep every machine token verbatim — code, commands, file paths, schema field names, stable IDs, and the status or verdict values this skill returns — and convey their meaning in the surrounding prose rather than translating the tokens. If the user's language is unclear, ask once, then continue in the chosen language. Persisted artifacts are contracts, not chat. Keep their template headings, YAML keys, stable IDs, and status tokens exactly as specified so downstream skills and validators keep working. Narrative content inside an artifact may follow the user's language when the user asks for it. ## Load references and assets - Read [discovery-and-audit.md](references/discovery-and-audit.md) before concluding whether a system exists. - Read [selection-interview.md](references/selection-interview.md) only when no usable system is available. - Read [current-system-catalog.md](references/current-system-catalog.md) before recommending a starting system; verify linked official documentation because ecosystems change. - Read [design-quality-gates.md](references/design-quality-gates.md) before creating a development contract or