annotations-figma
/annotations-figma
Read and write designer annotations on Figma nodes — node-level design specs that pin properties (fills, width, fontSize, etc.) and carry plain or markdown notes. Use when the user wants to document or inspect interaction specs, animation timings, easing, accessibility requirements, or implementation notes attached directly to a node. Triggers: 'add an annotation', 'annotate this node/component', 'read the annotations on…', 'what specs are pinned to this element', 'list annotation categories', 'document the focus behavior on this button in Figma'. Annotations are distinct from comments (they p
- Author
- southleft ↗
- Repository
- skills-for-figma ↗
- Licence
- MIT
- Last repository change
- 01.06.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 2
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 01.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 2 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/get-annotations.js, scripts/set-annotations.js
What it does and when to use it
Read and write designer annotations on Figma nodes — node-level design specs that pin properties (fills, width, fontSize, etc.) and carry plain or markdown notes. Use when the user wants to document or inspect interaction specs, animation timings, easing, accessibility requirements, or implementation notes attached directly to a node. Triggers: 'add an annotation', 'annotate this node/component', 'read the annotations on…', 'what specs are pinned to this element', 'list annotation categories', 'document the focus behavior on this button in Figma'. Annotations are distinct from comments (they p
Triggers from the description
Original author description
Read and write designer annotations on Figma nodes — node-level design specs that pin properties (fills, width, fontSize, etc.) and carry plain or markdown notes. Use when the user wants to document or inspect interaction specs, animation timings, easing, accessibility requirements, or implementation notes attached directly to a node. Triggers: 'add an annotation', 'annotate this node/component', 'read the annotations on…', 'what specs are pinned to this element', 'list annotation categories', 'document the focus behavior on this button in Figma'. Annotations are distinct from comments (they p
How it works
- Skill boundaries
- Workflow
- Notes
SKILL.md preview
--- name: annotations-figma description: "Read and write designer annotations on Figma nodes — node-level design specs that pin properties (fills, width, fontSize, etc.) and carry plain or markdown notes. Use when the user wants to document or inspect interaction specs, animation timings, easing, accessibility requirements, or implementation notes attached directly to a node. Triggers: 'add an annotation', 'annotate this node/component', 'read the annotations on…', 'what specs are pinned to this element', 'list annotation categories', 'document the focus behavior on this button in Figma'. Annotations are distinct from comments (they pin to design properties) and from the description field. Requires the Figma Desktop app (Plugin API)." disable-model-invocation: false --- # annotations-figma — read & write node annotations Annotations are designer-authored specs attached to a node. Each can carry a **note** (plain `label` or rich `labelMarkdown`), a set of **pinned properties** (`fills`, `width`, `fontSize`, …) that link the note to specific design attributes, and an optional **category** (interactions, accessibility, dev notes, …). They live on the node, survive edits, and are undoable (`Cmd+Z`). They are the right place for animation timings, easing curves, interaction behavior, and a11y requirements that don't belong in the component description. ## Skill boundaries - **`use_figma` rules** — load the official **`figma-use`** skill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-level `await` + `return` (no IIFE, no `figma.closePlugin()`; `console.log` is not returned), inputs inlined as `const` at the top of each script, colors in 0–1 range, load fonts before any text op, `await figma.getNodeByIdAsync(...)`, and **atomic errors** (a failed script applies nothing — read the error, fix, retry). - **Valid property types + shapes** → [references/annotation-properties.md](references/annotation-properties.md). - **Comments** (file-level discussion threads, not node specs) are out of scope — use Figma's comments REST API instead. ## Workflow 1. **Get the node ID.** Use the current selection or a node ID the user gives you. Annotations only apply to nodes whose type supports them (frames, components, instances, shapes, text — not pages). 2. **List categories first when writing categorized annotations.** Run the categories snippet so you can pass a real `categoryId` (category names are per-file and not guessable). See the script. 3. **Read** with [`scripts/get-annotations.js`](scripts/get-annotations.js) — set `INCLUDE_CHILDREN` to walk a component tree for full-component documentation. 4. **Write** with [`scripts/set-annotations.js`](scripts/set-annotations.js). Choose `MODE`: `'replace'` (default — overwrites all annotations on the node) or `'append'` (keeps existing). Pass `ANNOTATIONS = []` with `'replace'` to clear all annotations. 5. **Validate.** Re-run the read script and confirm the annotation count and labels match what you set. ## Notes - **Note any text op needs a font load.** Annotations themselves don't render text you author, but if a workflow also writes text nodes, `await figma.loadFontAsync(...)` first (see conventions). - Figma auto-populates BOTH `label` and `labelMarkdown` on read, but **rejects writing both** — when appending, prefer `labelMarkdown` if present, else `label`. The append script already does this. - `properties` only pins *which* attributes the note is about; it does not set their values. Use the exact strings from [references/annotation-properties.md](references/annotation-properties.md). - These tools require the **Figma Desktop** app (the Plugin API isn't available in the browser).
Files in this package (4)
- SKILL.md 4 KB
- references/annotation-properties.md 2 KB
- scripts/get-annotations.js 2 KB
- scripts/set-annotations.js 2 KB
Versions
The database has no other skills named annotations-figma.
Database snapshot: 13.11.2026 · package version 37885ab746e3 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90figma-annotations
Read and write designer annotations on Figma nodes — node-level design specs that pin properties (fills, width, fontSize, etc.) and carry plain or markdown notes. Use when the user wants to document or inspect interaction specs, animation timings, easing, accessibility… - 90annotation-conversion
Convert manual annotation markers (numbered or lettered dots with connected descriptions) into Figma's native dev-mode annotations using figma-mcp-rust. Use when a design contains hand-placed annotation markers that should become real Figma annotations. - 100figma-use-motion
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node. - 100figma-use-motion
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node. - 90design-annotations
Use when dev notes need adding, placing, or rewriting next to Figma design screens, using a note component from the design system or a default template. Triggers include "place my dev notes by their screens", "add dev notes to these screens", "improve the copy on these notes",… - 90fix
Apply messages and annotations sent from the Clause Assist Figma plugin. Use when the user says "check the inbox", "fix the notes", "see what I sent", or asks to apply Figma annotations.