Ds Figma Handover

What it does

When your agent uses it

• The user says check Figma for changes
• Generate a handover
• Sync from Figma
• After a design update

Example prompts

• “check Figma for changes”
• “what drifted”
• “generate a handover”
• “/ds-figma-handover”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

1. 1Refresh the index: pnpm ds:registry. Note any specMissing / todo
2. 2For each figma-linked component, pull its Figma node and diff by tier
3. 3Tokens: diff Figma variables against design-tokens.json. Report
4. 4Flag tier problems: if a Figma node has variants but the spec says
5. 5Compute blast radius: for each changed primitive, list every component/

What it can do on your machine

Read from SKILL.md and the folder at commit 5a43d7c. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • pnpm

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ds Figma Handover loads about 990 tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 337 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~98

When it runs · the whole SKILL.md, loaded when a task matches

~990

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mqtt-viewer/mqtt-viewer at commit 5a43d7c, republished under its GPL-3.0 licence (© mqtt-viewer). 337 words, ~990 tokens.

name

ds-figma-handover

description

Diff the Figma component library against the MQTT Viewer frontend and produce a handover doc listing exactly what code needs to change. Use when the user says "check Figma for changes", "what drifted", "generate a handover", "sync from Figma", or after a design update. This skill DETECTS and DOCUMENTS only — it does not edit component code (that's /ds-implement-handover).

# Handover: <slug> — <date>

## Summary
<one paragraph: what changed in Figma, scope, risk>

## Token changes
| token | change | affected components |
|---|---|---|

## Component changes (bottom-up)
### <Name> (<tier>)  — status: <current>
- Figma node: <url>
- Drift: <variant `danger` added | child Icon swapped | frame relayout ...>
- Files to edit: `frontend/src/.../X.svelte`, `X.spec.json`, `X.stories.svelte`
- Concrete instructions: <exact prop/option/token edits>
- New `lastSyncedHash`: <hash>  (implement agent writes this on completion)

## Unlinked / needs authoring
- <components with no figma link or no spec>

## Out of scope / human decision needed
- <ambiguous composition or data-wiring changes the agent shouldn't guess>

© mqtt-viewer, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/ds-figma-handover of mqtt-viewer/mqtt-viewer.

Open the folder on GitHubat commit 5a43d7c