design-system-analyzer
Analyze any website's UI style using ChromeDevTools to extract precise CSS tokens, animations, and interaction states. Handles complex sites and anti-bot measures by guiding the user. Triggers on "analyze this site", "extract UI style", "create design system from [URL]", or "learn visual style".
What this skill does
# Design System Analyzer
Analyze websites via ChromeDevTools to extract deep CSS logic (keyframes, transitions, tokens) and generate comprehensive Design System System Prompts.
## Critical Rules
1. **MUST** output the final prompt using EXACTLY the structure in `references/design-system-template.md`
2. **MUST** limit extraction data to prevent context overflow (see analysis-guide.md for limits)
3. **MUST** fill ALL template placeholders with extracted or observed values
4. **NEVER** skip sections - use "Not observed" if data unavailable
## Best Practice: Use Your Own Chrome
For the best experience (no CAPTCHAs, shared login cookies), advise the user to run Chrome with:
`chrome.exe --remote-debugging-port=9222`
(See **[references/setup-guide.md](references/setup-guide.md)** for details)
---
## Workflow Overview
```
[1. Navigate] → [2. Anti-Bot Check] → [3. Deep Extraction] → [4. Synthesize to Template]
```
**IMPORTANT**: Do NOT take screenshots. Screenshots consume excessive context and are unnecessary - all visual data is extracted from CSS.
---
## Step 1: Navigate & Anti-Bot Check
```
mcp__chrome-devtools__navigate_page (url: "<target-url>")
```
**Immediately check for bot challenges:**
```javascript
() => {
const text = document.body.innerText.toLowerCase();
const title = document.title.toLowerCase();
if (text.includes('cloudflare') || text.includes('verify you are human') || title.includes('just a moment')) {
return 'CHALLENGE_DETECTED';
}
return 'OK';
}
```
**IF CHALLENGE_DETECTED**:
1. **PAUSE** all actions.
2. Tell the user: "Bot protection detected. Please manually solve the CAPTCHA in the browser, then confirm here."
3. Wait for user confirmation before proceeding.
---
## Step 2: Deep CSS Extraction
Run the extraction scripts from `references/analysis-guide.md` **in order**:
| Order | Script | Purpose | Max Items |
|-------|--------|---------|-----------|
| 1 | CSS Variables & Tokens | Colors, spacing, typography variables | 50 tokens |
| 2 | Animation & Keyframes | @keyframes, animation usage, transitions | 10 KF, 15 trans |
| 3 | Interaction States | :hover, :focus, :active rules | 15 rules |
| 4 | Typography | Font stacks from key elements | 7 elements |
| 5 | Layout & Spacing | Border radius, gaps, shadows | 5 each |
| 6 | Tech Stack | Framework detection | - |
**IMPORTANT**: Each script has built-in limits. Do NOT modify to extract more data.
---
## Step 3: Synthesize to Template
**MANDATORY**: Generate output using EXACTLY the template structure from `references/design-system-template.md`.
### Template Mapping Table
| Extracted Data | Template Section | Notes |
|----------------|------------------|-------|
| `tokens.colors` | `Design Token System > Colors` | Format as table |
| `tokens.spacing` | `Spacing, Radius & Borders` | Include radius values |
| `tokens.typography` | `Typography` | Include font stacks |
| Typography script | `Typography > Font Stacks, Type Scale` | Computed styles |
| `keyframes` | `Animation & Motion > Key Animations` | Full keyframe definitions |
| `animationUsage` | `Animation & Motion > Timing` | Duration, easing |
| `transitions` | `Animation & Motion > Timing` | Common patterns |
| `interactions` | `Component Styling > State Transitions` | Hover/focus effects |
| Layout sampler | `Layout Principles` | Spacing system |
| Tech stack | `Implementation Notes` | Tailwind/CSS notes |
### Output Format Checklist
Before outputting, verify ALL these sections are present:
- [ ] `<role>` block (copy exactly from template)
- [ ] `<design-system>` wrapper
- [ ] `## Design Philosophy` with Core Principles, Vibe, Historical Context
- [ ] `## Design Token System` with Colors table, Typography, Spacing
- [ ] `## Component Styling Principles` with Buttons, Cards, Form Inputs
- [ ] `## Layout Principles` with Spacing System, Grid, Responsive
- [ ] `## The "Signature" Factor` with 3 mandatory elements
- [ ] `## Animation & Motion` with Philosophy, Timing, Key Animations
- [ ] `## Accessibility Constraints`
- [ ] `## Anti-Patterns` with Visual and Interaction no-nos
- [ ] `## Implementation Notes` with tech-specific guidance
- [ ] `## Aesthetic Checklist` with 4 verification items
- [ ] Closing `</design-system>`
---
## Resources
- **[references/design-system-template.md](references/design-system-template.md)**: The REQUIRED output template
- **[references/analysis-guide.md](references/analysis-guide.md)**: Deep extraction scripts with context limits
- **[references/setup-guide.md](references/setup-guide.md)**: Guide for reusing user's Chrome
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.