design-handoff

design-handoff is a command for Claude Code from Adityaraj0421/naksha-studio. It costs 27 tokens per session (2,012 once invoked), scanned A, original, MIT.

A command that creates a developer handoff document from a Figma file. It extracts details such as spacing, design tokens, component interfaces, and code examples so engineers can implement the design.

In plain words
What is it for?
Use it to prepare implementation specifications for selected Figma screens or all high-fidelity screens in a file.
Why use it?
It reduces guesswork between designers and developers. The document collects implementation details that are otherwise easy to miss when reviewing a design file manually.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the naksha-studio plugin — 47 commands, 7 agents shipped together

Good fit Use it to prepare implementation specifications for selected Figma screens or all high-fidelity screens in a file.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/adityaraj0421/naksha-studio/design-handoff
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/Adityaraj0421/naksha-studio

Made for: Claude Code.

Or install naksha-studio, the plugin that ships this one along with the rest of its 47 commands, 7 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for design-handoff

README.md
[![agentmods](https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-handoff/github.svg)](https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-handoff)
Your own site
<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-handoff"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-handoff/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for design-handoff

Your own site · 80×15
<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-handoff"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,012 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.02012
Opus 5 $0.00014 $0.01006
Sonnet 5 $0.00005 $0.00402
Haiku 4.5 $0.00003 $0.00201

Measured 9d ago against content hash 1b599d4d5f0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

design-handoff scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/design-handoff.md · 294 lines

How it starts

The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/design-handoff

You are generating a developer handoff document from a Figma file. This bridges the gap between design and engineering by extracting everything a developer needs to implement the design accurately.

Input: $ARGUMENTS

Process

1. Connect & Identify Target

figma_get_status → verify connection
figma_get_file_data(depth: 1, verbosity: 'summary') → get file overview

If the user provided a Figma URL, parse the file key and node ID. If they said "current file", use the active file. If not connected, guide Desktop Bridge setup.

Identify which screens/pages to generate handoff for. If unspecified, generate for all hi-fi screens.

2. Extract Design System Foundations

Color Tokens
figma_execute: `
  const paintStyles = (await figma.getLocalPaintStylesAsync()).map(s => {
    const paint = s.paints[0];
    let hex = '';
    if (paint?.type === 'SOLID') {
      const c = paint.color;
      hex = '#' + [c.r, c.g, c.b].map(v => Math.round(v * 255).toString(16).padStart(2, '0')).join('');
    }
    return { name: s.name, hex, opacity: paint?.opacity ?? 1 };
  });
  return paintStyles;
`

Map each token to CSS custom property format:

--color-primary: #2f49d8;
--color-primary-light: #eef1fb;
--color-background: #fffcf7;
--color-surface: #ffffff;
--color-text-primary: #0a1020;
Typography Scale
figma_execute: `
  const textStyles = (await figma.getLocalTextStylesAsync()).map(s => ({
    name: s.name,
    fontFamily: s.fontName.family,
    fontWeight: s.fontName.style,
    fontSize: s.fontSize,
    lineHeight: s.lineHeight,
    letterSpacing: s.letterSpacing
  }));
  return textStyles;
`

Map to CSS/Tailwind:

/* Heading/L */
font-family: 'Space Grotesk', sans-serif;
font-weight: 700;
font-size: 24px;
line-height: 32px;

3. Extract Component Specifications

For each component set in the file:

figma_execute: `
  await figma.loadAllPagesAsync();
  const sets = figma.root.findAllWithCriteria({ types: ['COMPONENT_SET'] });
  return sets.map(cs => ({
    name: cs.name,
    id: cs.id,
    variants: cs.children.map(v => ({
      name: v.name,
      width: v.width,
      height: v.height,
      padding: { top: v.paddingTop, right: v.paddingRight, bottom: v.paddingBottom, left: v.paddingLeft },
      itemSpacing: v.itemSpacing,
      cornerRadius: v.cornerRadius,
      layoutMode: v.layoutMode
    }))
  }));
`

Read the full file on GitHub · 294 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 294 lines · 27 tokens per session scan A 1b599d4d5f0b

Subscribe to this mod's changes

design-handoff is a command published in the GitHub repository Adityaraj0421/naksha-studio (317 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 2,012 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.