analyse-design — Claude Code skill for design system analysis
The analyse-design skill examines an app, website, or document’s code and screenshots to map its design system. Use it to audit UI consistency or guide new components.
Apache-2.0 ★ 173 updated 2026-10-24
npx skills add sammcj/agentic-coding --skill analyse-design -a claude-codeWhat analyse-design does
The skill scans theme tokens, global styles, component-library settings, layouts, and representative UI elements. It examines colour, type, spacing, component states, icons, motion, and responsive behaviour, tying findings to specific files and style definitions.
Its output can be a design reference in Markdown or a reply in the conversation. The reference may include token and type tables, a component inventory, consistency notes, and guidance for building matching UI. It can ask about the analysis scope and suggest supplying screenshots. For visual findings, screenshots add context that code alone may not show.
What it helps with
- extract design tokens and colour values from a codebase
- document an interface’s type and spacing scales
- identify recurring component patterns and their states
- audit consistency and flag outlier style values
- create a reference for building components that match a project
Example prompts for the agent
- Analyse this project’s design system and write a reference for building components.
- Use the codebase and screenshots to identify the colour palette, fonts, and spacing scale.
- Audit the UI for consistency and list unusual style values.
How to install analyse-design
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill analyse-design -a claude-code2Manually: put the files in place
~/.claude/skills/analyse-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/analyse-design/
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill analyse-design -a codex2Manually: put the files in place
.agents/skills/analyse-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill analyse-design -a cursor2Manually: put the files in place
.cursor/skills/analyse-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sammcj/agentic-coding Skills/analyse-design/SKILL.md2Manually: put the files in place
.github/skills/analyse-design/SKILL.md1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill analyse-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/sammcj/agentic-coding --path Skills/analyse-designManually: put the files in place
.devin/skills/analyse-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about analyse-design
How do I install analyse-design in Claude Code?
Run npx skills add sammcj/agentic-coding --skill analyse-design -a claude-code. The skill file is at ~/.claude/skills/analyse-design/SKILL.md.
What does analyse-design do?
It examines source code and screenshots, then documents the design system as a reference for building components that fit the application.
Which parts of a design system does the skill inspect?
It covers colour, typography, spacing, component patterns, icon style, motion, and responsive behaviour. Findings are tied to relevant files and style definitions.
Source text
SKILL.md · Apache-2.0
--- name: analyse-design description: Reverse-engineer an application, website or document's design system from its codebase and screenshots. Use when asked to analyse visual design, extract a colour palette, document UI patterns, identify typography and spacing systems, audit design consistency, or understand the design language of a frontend codebase. --- # Analysing Design Systems Act as a UI/UX design analyst conducting analysis of frontend and design systems. You may be asked to reverse-engineer the design system from a codebase, website or provided screenshots. Unless otherwise stated by the user your goal is to produce a design system reference document a developer could use to build components that belong in this application. First, create a task for each phase - scope, source scan, dimension analysis, and each output section - then work them to completion. ## Where to Look Scan for design-relevant sources in this priority order: 1. **Theme/token files** - tailwind.config, Tailwind v4 CSS-first tokens (`@theme` blocks in CSS), theme.ts/js, tokens.json, design-tokens, variables.css/scss 2. **Global styles** - global.css, app.css, index.css, _variables.scss, CSS custom properties (`:root` / `[data-theme]`) 3. **Component library config** - shadcn components.json, MUI theme, Chakra theme, Ant Design config 4. **Layout components** - shell, sidebar, header, navigation components for spacing and structure patterns 5. **Representative components** - buttons, inputs, cards, modals for recurring visual patterns ## Dimensions to Analyse For each dimension, cite specific files and style definitions. - **Design language** - visual school/philosophy (e.g., neo-brutalist, material, glassmorphism, minimal flat). Mood conveyed. Unique visual signatures - **Colour palette** - extract actual values. Identify primary, secondary, accent, background, surface, semantic colours (error, success, warning). Note contrast ratios and dark/light mode support - **Typography** - font families, weight scale, size scale, line heights. How hierarchy is established - **Spacing and layout** - spacing scale, grid system, whitespace usage, information density, consistent sizing patterns - **Component patterns** - common shapes, border radii, shadow treatments, interaction states across buttons, inputs, cards, navigation, status indicators - **Iconography** - icon style (outline, filled, duotone), library if identifiable - **Motion** - animation patterns, easing curves, transition durations found in code - **Responsive behaviour** - breakpoints, layout shifts, mobile adaptations ## Output Format Ask the user if they want your final output delivered in a markdown document (e.g. docs/DESIGN_LANGUAGE.md) or returned in the conversation. Structure findings as: 1. **Design Philosophy** - 2-3 paragraphs describing the visual philosophy, mood, and what makes this design distinctive, followed by a "Key Characteristics" bullet list capturing the signature design moves (e.g. "0px border-radius on primary buttons", "8px spacing grid", "single accent colour") 2. **Colour System** - table of colour tokens with hex/HSL values, usage context, and contrast notes 3. **Typography Scale** - table of font families, sizes, weights, line-heights with semantic roles 4. **Spacing Scale** - list of spacing values and where they apply 5. **Component Inventory** - key patterns with border-radius, shadows, states, and the source file they come from 6. **Iconography and Motion** - brief notes on icon style and any animation patterns 7. **Responsive Strategy** - breakpoints and layout behaviour 8. **Do's and Don'ts** - derive from observed dominant patterns. "Do" lists the conventions that should be maintained. "Don't" lists anti-patterns that would break consistency (e.g. "Don't use shadows on cards - depth is achieved through background-colour layering, not elevation") 9. **Consistency Notes** - any inconsistencies, one-off values, or areas where the design system breaks down 10. **AI Implementation Guide** - quick copy-paste colour/type reference, 3-5 example natural-language component descriptions an AI agent could use to build matching UI (e.g. "Create a card: #f4f4f4 background, 0px border-radius, 16px padding. Title at 20px weight 600..."), and iteration hints ## Tips - If you have the ability to ask the user questions using `AskUserQuestion` or similar you may ask the user multi-choice questions to clarify the scope of the analysis and their desired goals. - Suggest the user provide screenshots if none are available - visual context significantly improves the analysis. - Use sub-agents with clear operating boundaries to parallelise work.
© sammcj · Apache-2.0 · sammcj/agentic-coding