Menu
Author or maintain a design system's DESIGN.md + tokens.css (the contract). Use when fixing the SYSTEM rather than a component — adding tokens, tightening anti-patterns, or capturing visual rules. Adapted from open-design's design-md (Google Labs / Stitch).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Infer a design system's tokens + voice from a brand reference (screenshots or a URL) — vision-assisted. Use for /mds:system:create --mode extract, feeding the design-system-author skill.
Reason about color on-system — pick/adjust accent, surfaces, and status colors within a design system's palette, check contrast/accessibility, and propose token changes (not raw hex). Adapted from open-design's color-expert. Use for color decisions during build, review, or system edits.
Build a reusable, on-system React+Tailwind component from an intent. Use when creating or editing a component in emdesign. Composes design-system primitives from "@ds", references token roles only, emits a CSF story, and feeds the verify loop.
Designer-who-codes visual audit + fix. Use to tighten a component before shipping — run the four-source critique, then make atomic, on-system fixes with before/after screenshots. Adapted from open-design's design-review (gstack) to emdesign's code-first loop.
Create or update a design system to the emdesign quality bar — author the 9-section DESIGN.md + tokens.css + base primitives. Use for the System flow (/mds:system:create | :update). Knows the four sources: brief, blank, import, extract.
Master skill for design taste — embeds deliberate, opinionated design decisions into every agent interaction. Use at the START of any task to replace generic AI output with intentional design. Adapted from taste-skill (Leonxlnx) for emdesign's design system pipeline.
| name | design-md |
| description | Author or maintain a design system's DESIGN.md + tokens.css (the contract). Use when fixing the SYSTEM rather than a component — adding tokens, tightening anti-patterns, or capturing visual rules. Adapted from open-design's design-md (Google Labs / Stitch). |
Adapted from open-design's design-md. In emdesign the DESIGN.md is the contract the agent builds from and
the graph + lint enforce, so changes here ripple — use the graph to see the blast radius.
A finding's root cause is the system, not the component (e.g. a missing token role, a too-loose
anti-pattern, an under-specified component spec). consistency-auditor / graph_where_to_fix will say so.
design-systems/<id>/DESIGN.md (the 9 sections) + tokens.css. Follow
docs/spec.md and the rubric in docs/authoring-design-systems.md.tokens.css self-consistent (every role declared; every var() resolves).graph_find_affected('<ds>/--<token>') before changing a token: which primitives,
variants, stories, and artifacts move. Decide whether to re-baseline affected visual tests.emdesign test graph <id> --json to re-index, then re-verify affected components.