design-inspector

Extract design tokens, component inventory, and interaction patterns from live websites via Playwright MCP browser automation.

6|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill design-inspector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-inspector
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/design-inspector
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill design-inspector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the extraction of design tokens, component inventories, and interaction patterns from a live website so teams can document and reproduce a design system without cloning or rebuilding the site.

Core Features & Use Cases

  • Design token extraction: harvest colors, typography, spacing, border radii, shadows, and breakpoints from computed styles.
  • Component inventory: capture DOM snapshots and computed styles for navigation, cards, forms, buttons, media, and layout primitives.
  • Interaction audit: record scroll behaviors, hover states, click-driven transitions, and animation libraries.
  • Tech stack detection & assets: detect framework, CSS approach, font sources, icon libraries, svg counts, and lazy-loading strategy. Use cases include design audits, migrating visual systems to new projects, creating developer-ready design references, and UX research prior to reimplementation.

Quick Start

Inspect https://example.com to generate a structured design system report with tokens, component inventory, and interaction notes.

Frequently Asked Questions about design-inspector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract design tokens from a live website?

To extract design tokens from a live website, you need a tool that analyzes computed DOM styles. This process harvests colors, typography, spacing, border radii, shadows, and breakpoints directly from the rendered page to document your design system.

What is the best way to generate a component inventory for a design system migration?

Generating a component inventory for a design system migration involves capturing DOM snapshots and computed styles for UI elements like navigation, cards, forms, and buttons. This creates a developer-ready reference of existing layout primitives for accurate reimplementation.

How do I audit interaction patterns and hover states on an existing web page?

To audit interaction patterns and hover states on a web page, you record scroll behaviors, click-driven transitions, and animation libraries. This interaction audit logs dynamic UI changes by simulating user events like hover and click on the target URL.

Can I use Playwright to capture UI styles and detect a website's tech stack?

Yes, you can use Playwright browser capabilities to navigate, evaluate, and snapshot a website. This detects the underlying framework, CSS approach, font sources, and icon libraries while gathering DOM styles for a comprehensive front-end audit.

Do I need to clone a website to document its design system?

No, you do not need to clone or rebuild a website to document its design system. You can automate the extraction of design tokens, component inventories, and interaction patterns directly from the live site URL using browser automation.

What limitations exist when extracting computed styles from a live site?

When extracting computed styles from a live site, limitations include relying on accessible DOM states and static snapshots. Complex client-side rendering or restricted dynamic interactions may require manual evaluation to fully capture all design tokens.