figma-annotations
Skill83 starsChanged 6 months agoMITView on GitHub
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).
In this repository22 other files it gives its agents.
- figjam-create-contentSkill
- figma-analyze-component-setSkill
- figma-arrange-component-setSkill
- figma-audit-accessibilitySkill
- figma-blame-nodeSkill
- figma-check-design-paritySkill
- figma-commentsSkill
- figma-component-propertiesSkill
- figma-deep-componentSkill
- figma-design-system-inventorySkill
- figma-export-tokensSkill
- figma-extract-design-systemSkill
- figma-generate-changelogSkill
- figma-generate-component-docSkill
- figma-import-tokensSkill
- figma-library-variablesSkill
- figma-lint-designSkill
- figma-manage-variablesSkill
- figma-scan-code-accessibilitySkill
- figma-setup-design-tokensSkill
- figma-slidesSkill
- figma-version-historySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Get the node ID: Use the current selection or a node ID the user gives you.
- Very specific: line 25
List categories first when writing categorized annotations: Run the categories snippet so you can pass a real categoryId (category names …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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_figmarules — load the officialfigma-useskill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-levelawait+return(no IIFE, nofigma.closePlugin();console.logis not returned), inputs inlined asconstat 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.
- Comments (file-level discussion threads, not node specs) → use the
figma-commentsskill instead.
Workflow
- 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).
- 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. - Read with
scripts/get-annotations.js— setINCLUDE_CHILDRENto walk a component tree for full-component documentation. - Write with
scripts/set-annotations.js. ChooseMODE:'replace'(default — overwrites all annotations on the node) or'append'(keeps existing). PassANNOTATIONS = []with'replace'to clear all annotations. - 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
labelandlabelMarkdownon read, but rejects writing both — when appending, preferlabelMarkdownif present, elselabel. The append script already does this. propertiesonly pins which attributes the note is about; it does not set their values. Use the exact strings from references/annotation-properties.md.- These tools require the Figma Desktop app (the Plugin API isn't available in the browser).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

