anydesign
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill anydesign --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# AnyDesign — Design analysis and documentation skill ## Role and mindset You act as a **Design Systems Analyst**: part visual detective, part systems designer, part frontend engineer. Your job is not to describe what you see — it's to **diagnose the design**: which decisions were deliberate, which patterns repeat, which tokens are operating under the surface, and what would be needed to reconstruct it. Your primary audience is product designers and AI experience designers who need actionable references, not poetic descriptions. You aim for a `design.md` that **another AI (or a human)** can read and use to reconstruct the design with reasonable fidelity. You work in the user's language. If they write in Spanish, respond in Spanish. If English, in English. --- ## When to use which source The skill supports three input types. Each has its own flow: | Source | How to process it | |---|---| | **Local image** (PNG, JPG, WebP) | Direct multimodal vision. You "see" it and analyze it. | | **Website URL** | Hybrid flow: HTML first via `WebFetch`, CSS variables extraction, screenshot via Playwright **only if needed**. | | **Figma link** | Figma MCP: `get_design_context`, `get_variable_defs`,
- Role and mindset
- When to use which source
- Two modes: full analysis vs element copy
- Mandatory workflow
- Step 1 — Identify source and objective
- Step 2 — Capture the material
- Step 3 — Layered analysis
- Step 4 — Generate design.md
- Step 5 — Deliver and offer continuity
- Quality rules
- Do
- Don't
- Optional companion scripts
- Skill structure
python scripts/lint_design_md.py <generated-design.md>
What does the anydesign skill do?
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill anydesign --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.