Troubleshooting shadcncraft Agent Skills

The skill does not trigger#

• Restart your agent after installing. Skills are loaded at startup; a new chat window or a restart picks them up.
• Check the install location. The skill folder must be in your tool's project skills directory (.claude/skills/, .cursor/skills/, .codex/skills/, and so on), or in ~/.claude/skills/ for global use. Run npx @shadcncraft/skills list to confirm what is available.
• Be specific. Agents consult skills for tasks they cannot trivially handle. "Build a pricing page from our shadcncraft blocks" triggers reliably; a one-word request may not.
• Confirm it loaded by watching for Launching skill: ... when you send the request.

npx @shadcncraft/skills is not found#

Make sure you are running it from a directory with network access and a recent Node. To install without the CLI, use the manual install.

Installing a block fails with a 401 / license error#

Pro blocks require a license key. Set it before installing:

export SHADCNCRAFT_LICENSE_KEY=your-key

The @shadcncraft registry sends this as an X-License-Key header (configured in your components.json). Free-tier blocks install without it.

Generate code cannot read my Figma frame#

• Connect the official Figma MCP and make sure you are signed in.
• Provide a node-specific URL (one that includes node-id=...) or select the frame in Figma first.
• The skill resolves frames by name and data-slot, not node ID, so a frame from a different file still maps, as long as its name matches a registry item.

Import variables changed the wrong thing / I lost customizations#

The skill only edits inside the shadcncraft:tokens:start / :end region. If your globals.css did not have that region yet, the first run carves your existing tokens into it. If anything outside the region changed, revert and re-run, and report it, because that is a bug.

Still stuck?#

See the getting started guide or reach out via support.