Agent Skills for the shadcncraft design system, for Claude Code, Cursor, and Codex. They turn shadcncraft Figma designs into React + shadcn/ui code, bring React UI back into your Figma kit, and keep your theme in sync with your design tokens.
Each skill follows the Agent Skills open standard: a folder with a SKILL.md and supporting references/. Full docs: shadcncraft.com/docs/agent-skills.
| Skill | What it does |
|---|---|
shadcncraft-generate-code |
Convert a selected shadcncraft Figma frame, component, or page into React + shadcn/ui code via the official Figma MCP. Reuses the matching registry block, stays on your project's tokens, and uses your configured icon library. |
shadcncraft-import-variables |
Sync design tokens into globals.css as a complete shadcn token set (light + dark). Reads from the Figma MCP or a local file and merges into a managed region without overwriting your customizations. |
| Skill | What it does |
|---|---|
shadcncraft-import-app |
Scan a React app built on shadcn/ui and write an import plan: what maps to existing kit components, what needs a custom Component or Block, which screens and app shell it has, plus token drift and code hygiene flags. Read-only: it never edits your code or your Figma file. |
shadcncraft-import-component |
Build one approved custom Component from the plan as a Figma component set, with variants and states taken from your React source and the rendered DOM. |
shadcncraft-import-block |
Build one approved Block, screen, or app shell from the plan. Blocks are composed from kit instances; screens are built at 1440 and 375. |
How the three work together:
import-appwritesimport-plan.mdfor you to review and approve, andimport-plan.jsonfor the build skills.import-componentandimport-blockbuild one approved unit per run, in dependency order. They first measure the running app in light and dark, saving captures under.shadcncraft/captures/. Progress is saved to the plan, so an interrupted build resumes instead of starting over.- Approving the plan approves the build order only. New variables, changes to existing kit components, and token substitutions are each proposed and wait for your approval.
- Claude Code, Cursor, Codex, or another agent that supports Agent Skills.
- The official Figma MCP, connected.
- Figma to React: a project set up for shadcncraft, with the
@shadcncraftregistry incomponents.jsonand aglobals.cssthat has the shadcn token block. - React to Figma: your own copy of the shadcncraft Figma kit, and a React app built on shadcn/ui (local folder or GitHub URL). The two build skills also need a Figma MCP that can write to the canvas and a running dev server. These are long workflows, so use the most capable model your editor offers.
npx skills add shadcncraft/skillsOr use the npm installer, which can target specific agent tools:
npx @shadcncraft/skills add allRestart your agent to pick up the new skills. More in the installation guide.
The skills are free to install. What each one can do depends on what it touches:
| Skill | Who can use it |
|---|---|
shadcncraft-import-variables |
Everyone. It only reads design tokens and writes globals.css. |
shadcncraft-import-app, shadcncraft-import-component, shadcncraft-import-block |
Anyone with a copy of the shadcncraft Figma kit. They work in your own code and your own Figma file, so no license key is needed. |
shadcncraft-generate-code |
Pro React or Pro Figma + React customers. It installs pro blocks from the shadcncraft registry, which requires SHADCNCRAFT_LICENSE_KEY. Without a key, the skill points you to pricing. |
- The skills in this repository (instructions and references) are MIT licensed.
- The registry blocks that
generate-codeinstalls are licensed separately. Free blocks work as is; pro blocks require a Pro React or Pro Figma + React license under the shadcncraft license.
- Figma plugin: generates code from inside Figma. These skills are its in-editor counterpart.
- UI Rules: a companion MCP for your design rules. Support in
import-variablesis coming soon and will never be required.