figma-annotationslisted

# figma-annotations — 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) → use the `figma-comments` skill 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, ins