Help us improve
Share bugs, ideas, or general feedback.
From claude2figma
Analyzes screenshots, URLs, or design descriptions to produce a structured Design Brief mapping visual observations to design system tokens. Waits for confirmation before building.
npx claudepluginhub senlindesign/claude2figma --plugin claude2figmaHow this skill is triggered — by the user, by Claude, or both
Slash command
/claude2figma:reference-interpreterThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze a reference (screenshot, URL, or description) and produce a **Design Brief** that maps visual observations to design system tokens. Output the Brief, then **stop and wait for user confirmation** before building anything.
Analyzes UI screenshots to extract design tokens, color palettes, typography scales, spacing patterns, components, and layout structures via eight-phase process.
Reverse-engineers design systems from screenshots or URLs, extracting colors, typography, spacing, and component patterns. Use before redesigning or auditing an existing page.
Extracts design DNA—colors, typography, spacing tokens, component patterns—from app screenshots, live URLs, or projects using Google Stitch. Outputs design-tokens.json, Tailwind config, or CSS vars for audits and design systems.
Share bugs, ideas, or general feedback.
Analyze a reference (screenshot, URL, or description) and produce a Design Brief that maps visual observations to design system tokens. Output the Brief, then stop and wait for user confirmation before building anything.
Prerequisite: figma-preflight should have run so the Token Map and Style Registry are available.
Examine the reference across these dimensions:
For each observation, identify the specific Token or Style from the session's Token Map:
"Large dark headline" → Text Style: heading/h1 · Color: text/primary
"Neutral section bg" → Variable: background/surface-2
"Tight card spacing" → Gap: gap/xs · Padding: padding/sm
If no token exists, flag it:
⚠️ Gap: [observation] — no matching token. Options: (a) nearest match: [name], (b) add token first.
## Design Brief
**Reference**: [source]
**Section**: [what this covers]
**Aesthetic**: [3-5 keywords]
### Layout
[structure, height, alignment]
### Typography
- Heading: [Style name] — [why]
- Body: [Style name]
### Colors
- Background: [Variable] — [context]
- Text: [Variable]
- Accent: [Variable] — [used for]
### Spacing
- Section padding: [Variable]
- Internal gap: [Variable]
### Components needed
- [Name]: [from library? source]
### Gaps
- [Gap description] — awaiting decision
- (none) [if all mapped]
Output exactly:
Brief complete. Type `confirmed` to begin building, or tell me what to adjust.
Do NOT call use_figma or place any nodes until user types confirmed.