← ClaudeAtlas

figma-to-componentlisted

Turn a Figma frame or node (via the Figma MCP) into production-grade Next.js + TypeScript + Tailwind + shadcn/ui components, WITHOUT creating duplicates — it scans MODULE_REGISTRY.md and the shared/feature trees first and reuses or extends what exists, places each new piece correctly (generic/reusable → components/shared, domain-specific → features/<name>/components), styles with Tailwind utilities + theme tokens, animates with Tailwind/CSS or framer-motion, exports assets, and registers new shared components. Use this whenever the user wants to build/implement/convert a Figma design, frame, screen, section, or component into React/Next.js code — phrases like "turn this figma frame into a component", "build this design", "implement this figma node", "code this screen from figma", "figma to react/next", or pasting a figma.com link and asking for components. This is the Figma design-to-code component builder — when the design source is an HTML file/URL use html-to-component, and when it is another existing code
vipincode/exr-agent-skills · ★ 0 · Web & Frontend · score 57
Install: claude install-skill vipincode/exr-agent-skills
# figma-to-component Convert a Figma frame/node into **Next.js + Tailwind + shadcn/ui** components that look production-grade *and* fit the project's existing structure — the headline being **no duplicate components**. The hard part isn't generating JSX from a design; current models do that well. The hard part is doing it *without* creating the third `Header`, the second `Avatar`, the duplicate `Card` — so this skill is built around a **dedup-first protocol**: read the registry, search the tree, reuse/extend what's there, and only then create, placing each new piece in its one correct home. This is the **component builder** of the frontend toolkit. It assumes the project is already scaffolded (`nextjs-bootstrap`) and ideally themed (`font-theme-setup`), so it can lean on shadcn primitives, the shared component library, and the oklch theme tokens instead of hardcoding. It does **not** set up the theme and does **not** scaffold. ## The core problem this skill solves Designs repeat. A Figma file has the same header on five frames, the same avatar in three places, cards everywhere. A naive frame→code pass re-emits all of them inline, and you drown in duplicates. The fix is to treat the project's `MODULE_REGISTRY.md` as a dedup ledger and the shared/feature trees as the source of truth: **before writing any component, check whether it already exists; if it does, import it; if a close cousin exists, extend/compose it; only genuinely new things get created** — and reusable ones