Agentic Design Systems

When this skill triggers, you're helping the user build, extend, or audit a component library whose primary consumer is an AI agent. The bar: given a prose request like "Build a confirmation modal with a destructive action," an agent picks the right component, the right variant, and the right tokens — without inventing patterns.

This skill gives you the schema, the workflow, and the principles. Adapt it to where the user is.

Diagnose first

Before producing anything, figure out which mode applies:

• Greenfield — user is starting a new system intended for agent consumption. Walk through the build workflow. Start with the schema and one worked component (Button is canonical); don't try to scaffold everything at once.
• Retrofitting — user has a component library and wants to make it agent-readable. Skip workspace setup. Add meta.types.ts, then write a .meta.ts per component, then build the index and validator. Anti-patterns first (see Step 5).
• Auditing — user has metadata already. Score each component against the four pillars and the validator checks. Flag missing relationships, prose anti-patterns, raw global tokens, and ungrounded variant axes.
• Single component — user wants to add or fix one component. Generate the full file set in Step 3. Metadata ships with the component or it doesn't ship.

If the prompt is ambiguous, ask one targeted question — don't guess.