Help us improve
Share bugs, ideas, or general feedback.
Reads and writes designer annotations on Figma nodes — node-level design specs with pinned properties (fills, width, fontSize) and plain/markdown notes. Use for documenting interaction specs, animation timings, easing, accessibility requirements, or implementation notes.
npx claudepluginhub southleft/figma-console-mcp-skills --plugin figma-console-mcp-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/figma-console-mcp-skills:figma-annotationsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Annotations are designer-authored specs attached to a node. Each can carry a **note** (plain `label`
Posts generated design behavior questions as pinned comments on Figma frames using node IDs, file keys, and positioning from manifest.json. Used after generate-behavior-questions when user confirms posting.
Read, post, reply to, and delete comments on a Figma file via the REST API, including pinning to a node and threading replies. Requires a personal access token.
Teaches Claude Code how to use `use_figma` tool correctly, including prerequisite rules, API reference loading, and co-loading companion skills.
Share bugs, ideas, or general feedback.
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.
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).figma-comments skill instead.categoryId (category names are per-file and not guessable). See the script.scripts/get-annotations.js — set INCLUDE_CHILDREN
to walk a component tree for full-component documentation.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.await figma.loadFontAsync(...) first (see conventions).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.