design-compare
Compare Figma designs against implementation screenshots, identifying layout, typography, color, and sizing discrepancies. Generates a structured visual review table and an interactive HTML comparison page with swipe and side-by-side modes. Use when the user asks to compare design with preview, compare Figma with screenshot, check design implementation, or provides a Figma URL alongside a screenshot.
What this skill does
# Design Compare
Compare Figma design screenshots against local preview screenshots, producing a structured visual review and an interactive HTML comparison page. Supports multiple screens in a single report.
## Setup
`$SKILL_DIR` refers to the directory containing this SKILL.md file. Resolve it based on where the skill is installed (e.g. `.claude/skills/design-compare`, `.agents/skills/design-compare`, etc.).
## Prerequisites
The export script requires a `FIGMA_ACCESS_TOKEN` env var. Store it in `.env` at the repo root:
```
FIGMA_ACCESS_TOKEN=figd_...
```
The script auto-loads `.env` from the repo root. Get a token from https://www.figma.com/developers/api#access-tokens
**Important:** Ensure `.env` is listed in `.gitignore` to avoid committing tokens.
## Workflow
### Step 1: Obtain Images for Each Screen
Repeat for each screen being compared. Use a slug (e.g. `empty-state`, `list-view`) to name files.
Derive the report folder from the project or context name, e.g. `design-compare-reports/LayoutCheckExample/`. Within this folder, store images in per-view subfolders named after the source file (without extension), e.g. `ContentView/`, `SliderView/`. The report folder holds a single shared `config.js` and `report.html`.
**Figma design image:**
- Extract `fileKey` and `nodeId` from the Figma URL.
- Call `mcp__figma__get_screenshot` with the extracted parameters. The screenshot is returned inline for visual comparison in Step 2.
- To save it as a file for the HTML page, run the export script:
```bash
mkdir -p "design-compare-reports/<ReportName>/<ViewName>"
bash "$SKILL_DIR/scripts/export-figma-node.sh" "<fileKey>" "<nodeId>" "design-compare-reports/<ReportName>/<ViewName>/<slug>_figma.png"
```
The script validates that `fileKey` is alphanumeric (with hyphens/underscores) and `nodeId` matches digit-colon/hyphen patterns. Invalid inputs are rejected.
The script exports at 3x scale with `use_absolute_bounds=true` to match device pixel density and clip to exact frame bounds.
- If the script fails (no token), ask the user to provide a Figma screenshot file.
**Preview image:**
- If using Xcode MCP, call `mcp__xcode__RenderPreview` to render a fresh preview and use the returned `previewSnapshotPath`.
- Otherwise accept a preview image path from the user.
- Copy to the report folder:
```bash
cp "<preview_path>" "design-compare-reports/<ReportName>/<ViewName>/<slug>_preview.png"
```
### Step 2: Visual Comparison
Read/view both images (Figma inline screenshot + preview file) and analyze them. Evaluate:
1. **Layout** - positioning, alignment, spacing between elements
2. **Typography** - font sizes, weights, line heights, text content
3. **Colors** - backgrounds, text colors, tint colors, opacity
4. **Components** - buttons, toolbars, icons, navigation elements
5. **Sizing** - element dimensions, padding, margins
### Step 3: Output Comparison Summary
Produce a single markdown table ordered by visual importance:
| Status | Aspect | Detail |
|--------|--------|--------|
| ✅ | Layout alignment | Matches design |
| ❌ | Background color | Expected #1A1A1A, got #FFFFFF |
Use ✅ for matches, ❌ for mismatches. Keep each row concise (one line). For mismatches, include what differs and how to fix it.
### Step 4: Generate HTML Comparison Page
All shared artifacts (`config.js`, `report.html`) are stored in `design-compare-reports/<ReportName>/`. Images live in per-view subfolders (`<ViewName>/`).
1. Generate `config.js` with screen metadata. Image paths use the `<ViewName>/` prefix. Write the following JavaScript to `design-compare-reports/<ReportName>/config.js`:
```js
// config.js — generated by design-compare skill
const reportConfig = {
generatedAt: "TIMESTAMP", // replace with current date/time
screens: [
{
name: "SCREEN_NAME", // replace with human-readable name
figma: "VIEW_NAME/SLUG_figma.png",
preview: "VIEW_NAME/SLUG_preview.png",
figmaUrl: "FIGMA_URL" // replace with full Figma URL for the node
}
]
};
```
Replace placeholders: `TIMESTAMP` → current date/time, `SCREEN_NAME` → human-readable name, `VIEW_NAME` → source file name (without extension), `SLUG` → file slug, `FIGMA_URL` → full Figma URL.
For multiple screens, add entries to the `screens` array.
2. Copy the HTML template:
```bash
cp "$SKILL_DIR/assets/compare.html" "design-compare-reports/<ReportName>/report.html"
```
3. Open the file with `open design-compare-reports/<ReportName>/report.html`.
The HTML page provides swipe (default) and side-by-side comparison modes, screen tabs for multi-screen reports, and direct Figma links.
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.