Review a design system with AI
Audit a component family, document an existing pattern or propose an extension that fits the system.
To review a design system with AI, give design-system a component people recognise and examples of how it is used. The guide covers auditing, documenting and extending the system. A primary button that behaves differently across checkout and account settings gives the team a concrete place to investigate naming, design tokens and interaction states.
A screenshot can reveal a visual mismatch. Implementation details explain whether two colours share a token or happen to look alike. Supply both when available and tell the agent whether you need findings for a designer, documentation for a developer or a proposal for a new pattern.
What it does
- Compare component variants across selected screens
- Spot inconsistent names and hard-coded token values
- Document visual and interaction states
- Describe keyboard and accessibility expectations
- Assess a new pattern against existing components
Install and use
- Install the skill and provide authorised component examples or system documentation. The Design plugin can optionally connect a permitted Figma or knowledge-base workspace.
- Ask “Audit the primary action on these three screens. Show the inconsistent states and names before suggesting a change.”
- Confirm which differences are intentional, then request documentation for the agreed convention.
FAQ
Source
Made by Anthropic. Original skill: design-system, published on GitHub under the Apache-2.0 licence.
View on GitHub