How do I install the Figma Annotation Guide skill?

Run npx skillmds@latest add majiayu000/figma-annotation-guide in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Figma Annotation Guide safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Figma Annotation Guide?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Figma Annotation Guide free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Figma Annotation Guide?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Figma Annotation Guide by majiayu000

Name: Figma Annotation Guide
Rating: 4.2 (5 reviews)
Author: majiayu000

Figma Annotation Guide

Generate structured developer handoff annotations for a Figma screen or component. Use when asked to write Figma annotations, create dev handoff notes, document a Figma design for developers, or write specs for a screen. Produces a complete annotation set covering interactions, states, spacing, accessibility, and edge cases.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Figma Annotation Guide Skill

Produces a complete set of developer handoff annotations for a Figma screen or component — the notes that turn a visual design into a buildable spec.

Required Inputs

Screen or component description (describe or summarise what was designed)
Platform (iOS / Android / Web / React Native)
Interaction type (static / interactive / animated / form)
Developer audience (mobile / frontend / full-stack)

Output Structure

1. Screen/Component Overview

Name, purpose, entry points, exit points.

2. Interaction Annotations

[Element name]

Default state: [Visual description]
On tap/click: [Exact action — API call, state change, navigation]
Loading state: [Description]
Success state: [What happens after]
Error state: [What error looks like and user options]
Disabled condition: [When and why]

3. State Inventory

Element	States Required
[Element]	Default, Hover, Active, Disabled, Loading, Error, Empty

Flag missing designs: "Warning: Error state not designed — needed before build"

4. Spacing and Layout Notes

Fixed vs fluid elements, scroll behaviour, breakpoints, safe areas.

5. Content and Copy Rules

Character limits, dynamic vs static content, truncation rules, empty states.

6. Accessibility Annotations

Touch targets, screen reader labels, focus order, colour contrast, motion preferences.

7. Edge Cases and Developer Questions

[Unresolved question for developer to flag]

Quality Checks

Every interactive element has all states defined
State inventory flags missing designs
Accessibility covers touch targets and screen reader labels
Empty states specified
Edge cases listed as actionable questions

Example Trigger Phrases

"Write dev annotations for this Figma screen"
"Create developer handoff notes for [screen/component]"
"Document this design for the engineering team"
"Write the Figma spec for [feature]"
"What should I annotate before handing off this design?"

---name: figma-annotation-guidedescription: Generate structured developer handoff annotations for a Figma screen or component. Use when asked to write Figma annotations, create dev handoff notes, document a Figma design for developers, or write specs for a screen. Produces a complete annotation set covering interactions, states, spacing, accessibility, and edge cases.--- # Figma Annotation Guide Skill Produces a complete set of developer handoff annotations for a Figma screen or component — the notes that turn a visual design into a buildable spec. ## Required Inputs - **Screen or component description** (describe or summarise what was designed) - **Platform** (iOS / Android / Web / React Native) - **Interaction type** (static / interactive / animated / form) - **Developer audience** (mobile / frontend / full-stack) ## Output Structure ### 1. Screen/Component Overview Name, purpose, entry points, exit points. ### 2. Interaction Annotations **[Element name]** - Default state: [Visual description] - On tap/click: [Exact action — API call, state change, navigation] - Loading state: [Description] - Success state: [What happens after] - Error state: [What error looks like and user options] - Disabled condition: [When and why] ### 3. State Inventory | Element | States Required | |---|---| | [Element] | Default, Hover, Active, Disabled, Loading, Error, Empty | Flag missing designs: "Warning: Error state not designed — needed before build" ### 4. Spacing and Layout Notes Fixed vs fluid elements, scroll behaviour, breakpoints, safe areas. ### 5. Content and Copy Rules Character limits, dynamic vs static content, truncation rules, empty states. ### 6. Accessibility Annotations Touch targets, screen reader labels, focus order, colour contrast, motion preferences. ### 7. Edge Cases and Developer Questions - [ ] [Unresolved question for developer to flag] ## Quality Checks - [ ] Every interactive element has all states defined - [ ] State inventory flags missing designs - [ ] Accessibility covers touch targets and screen reader labels - [ ] Empty states specified - [ ] Edge cases listed as actionable questions ## Example Trigger Phrases - "Write dev annotations for this Figma screen" - "Create developer handoff notes for [screen/component]" - "Document this design for the engineering team" - "Write the Figma spec for [feature]" - "What should I annotate before handing off this design?"

Frequently asked questions