agentleFS
tammaitammai/bigin-skills/skills/nuxt-ui-figma-handoff/SKILL.md

nuxt-ui-figma-handoff

Skill1 starsChanged 41 days agoMITView on GitHub

Turns a Nuxt UI Figma handoff (file/frame URL) into code — theme tokens into main.css, component overrides into app.config.ts. Triggers: 'implement this Figma design in our Nuxt UI app', 'sync our theme with the Figma handoff'.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the Figma MCP connector isn't authorized in this session, say so plainly and offer the fastest fallback instead of stalling: Nuxt's own …

    line 30
  2. Distinctive:

    Use Glob/Grep, don't assume paths:

    line 50
  3. Very specific:

    Check the installed @nuxt/ui version in package.json.

    line 56
  4. Distinctive:

    If a component override is needed, read that component's current default theme before writing anything, so the result is a diff, not a full …

    line 60
  5. Very specific:

    Read references/nuxt-ui-v4-theming.md before making edits — exact CSS variable names, the semantic color table, and worked examples of the …

    line 67
  6. Distinctive:

    If the designer only gave one swatch for a new brand color (not a full 50–950 ramp — the most common gap in a handoff), don't invent …

    line 83
  7. Very specific:

    If a project is connected: Read the existing main.css and app.config.ts, then Edit them — merge into the existing structure, don't …

    line 95
  8. Distinctive:

    If no project is connected, or the files don't exist yet: produce the same edits as clearly-labeled code blocks, one per file, with the …

    line 99

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

nuxt-ui-figma-handoff

Nuxt UI's official Figma kit mirrors the code library almost exactly — same semantic color roles, same radius/spacing scale, same component variants. A designer's tweaks in Figma map to a specific, small edit in one of two files, never a rewrite. The job here is finding that mapping precisely instead of guessing at pixel values or dumping a giant theme object where a three-line diff would do.

When not to use

Figma-to-code work unrelated to Nuxt UI theming — a different component library, or building a screen from scratch — is a plain design-to-code task, not this skill. Same if there's no Nuxt UI project in scope.

Step 1: Get the Figma link

This skill needs a real Figma file or frame URL, not a paraphrased description of what changed — the URL is what resolves the specific node so its actual variables and component variants can be read, rather than inferred secondhand. If the user hasn't given one, ask for it before doing anything else.

If the Figma MCP connector isn't authorized in this session, say so plainly and offer the fastest fallback instead of stalling: Nuxt's own recommended handoff tool is TemPad Dev (a Chrome extension + official Nuxt UI plugin that inspects a selected component in Figma dev mode and outputs its real Tailwind classes/props). An exported variables JSON or screenshots + a plain-language changelist also work. Still ask for the Figma URL alongside whichever of these the user provides — it's useful context even when the MCP itself can't reach it yet.

Step 2: Read the design

Once the connector is available, use Figma MCP tools (search for them via ToolSearch if deferred) against the given URL to pull the frame/node's local variables and component variant info — variable name, resolved value, and which component/variant it's scoped to. This is ground truth; prefer it over eyeballing a screenshot.

Your goal is a list of changed tokens, not the whole design — each tied to either a global role (a color, the radius, a font) or a specific component + variant.

Step 3: Locate the project's theme files

Use Glob/Grep, don't assume paths:

  • CSS entry point: usually app/assets/css/main.css, sometimes assets/css/main.css. Confirm with @import "@nuxt/ui".
  • Config: usually app/app.config.ts, sometimes app.config.ts at the root. Confirm with defineAppConfig.
  • Check the installed @nuxt/ui version in package.json. Everything below assumes v4 (Tailwind CSS v4, CSS-first @theme tokens). If the project is on v2 or v3, the shapes differ meaningfully — flag this rather than silently applying v4-shaped config to an older project.
  • If a component override is needed, read that component's current default theme before writing anything, so the result is a diff, not a full re-declaration. If @nuxt/ui is installed, its source is under node_modules/@nuxt/ui (look for a theme folder). Otherwise fetch from github.com/nuxt/ui/tree/v4/src/theme/<component>.ts, matching the tag to the installed version.

Read references/nuxt-ui-v4-theming.md before making edits — exact CSS variable names, the semantic color table, and worked examples of the component override shape. Small naming mistakes (e.g. inventing a variable instead of using --ui-radius) silently do nothing.

Step 4: Classify each changed token

What changed in FigmaWhere it goes
A brand color's full palette (new hex ramp)main.css, @theme block, --color-<name>-50 through -950
Which color fills a semantic role (e.g. "primary is now this purple")app.config.ts, ui.colors.<role>
Base corner radiusmain.css, :root { --ui-radius: ... }
Font familymain.css, @theme { --font-sans: ... }
Container max width / header heightmain.css, :root { --ui-container / --ui-header-height }
A specific component's padding, font weight, a variant's color/ring, default size/color/variantapp.config.ts, ui.<component>.{slots,variants,compoundVariants,defaultVariants}

If the designer only gave one swatch for a new brand color (not a full 50–950 ramp — the most common gap in a handoff), don't invent numbers by eye. Run:

node ${CLAUDE_SKILL_DIR}/scripts/generate_color_scale.mjs <hex> --name <color-name> [--anchor 500]

and say clearly in the summary that the ramp is algorithmically generated and worth a design sign-off, not a transcription of something the designer specified.

Step 5: Apply the changes

If a project is connected: Read the existing main.css and app.config.ts, then Edit them — merge into the existing structure, don't overwrite unrelated content. Only add the keys that actually changed; resist restating the whole default theme.

If no project is connected, or the files don't exist yet: produce the same edits as clearly-labeled code blocks, one per file, with the exact file path noted above each block.

Step 6: Summarize

Close with a short, concrete list of what changed and where (e.g. "primary role moved from green to violet — app.config.ts", "base radius 0.25rem → 0.5rem — main.css"). Flag anything inferred or generated — like an auto-generated color ramp, or a token that didn't map cleanly to an existing role — so it gets a design check before merging.

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.