agentleFS
TarasTsavolykTarasTsavolyk/claude-code-frontend/.claude/skills/from-figma/SKILL.md

from-figma

Skill1 starsChanged 4 months agoMITView on GitHub

Turn a Figma design into project components — pull the design via the Figma MCP, map it onto design tokens and shared/ primitives, build per scaffold conventions, then verify against the design. Use when implementing a screen or component from a Figma link.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. davision0102/fabrik★ 3same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

Files
SKILL.md

From Figma to component

Requires the Figma MCP server (connect via /mcp). Without it, ask for exported specs/screenshots and continue from step 2.

  1. Pull the design. Fetch the linked node — design context plus a screenshot. Read layout, spacing, type, color variables, variants, and any interaction notes; don't eyeball a thumbnail.
  2. Map, don't transplant. Translate raw values onto the project's design tokens (styling.md): nearest token wins; a Figma hex that matches no token is a finding to raise, not a value to hardcode. Match design components against shared/ and the UI kit before building anything new — reuse beats rebuild (architecture.md).
  3. Plan the split from the design's structure. Repeated regions → leaf components; overlays compose the shared overlay primitive; Figma variants → a variant/mode prop or separate components per the Component API rules (architecture.md).
  4. Build per /scaffold-component. The mock shows the happy path — implement loading/error/empty too (data-fetching.md), and the a11y baseline a mock can't show (accessibility.md).
  5. Verify against the design. Render the result (dev server / browser tooling) side by side with the Figma screenshot: spacing rhythm, type scale, states, responsive behavior at the design's breakpoints. Report deliberate deviations (token rounding, added states) explicitly.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.