annotation-conversion
/annotation-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.
- Author
- alvinindra ↗
- Repository
- figma-mcp-rust ↗
- Licence
- MIT
- Last repository change
- 12.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Process Overview
- Step 1: Get Selection and Initial Setup
- Step 2: Scan Annotation Text Nodes
- Step 3: Scan Target UI Elements
- Step 4: Match Annotations to Targets
- Step 5: Verify Results
SKILL.md preview
--- name: annotation-conversion description: 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. --- # Automatic Annotation Conversion ## Process Overview Convert manual annotations (numbered/alphabetical indicators with connected descriptions) to Figma's native annotations: 1. Get selected frame/component information 2. Scan and collect all annotation text nodes 3. Scan target UI elements (components, instances, frames) 4. Match annotations to appropriate UI elements 5. Apply native Figma annotations ## Step 1: Get Selection and Initial Setup // Get the selected frame/component get_selection() // Note the selected node ID, then: get_annotations(nodeId: "selected-node-id") ## Step 2: Scan Annotation Text Nodes // Get all text nodes in the selection scan_text_nodes(nodeId: "selected-node-id") // Filter and group annotation markers and descriptions // Markers typically have these characteristics: // - Short text content (usually single digit/letter) // - Specific font styles (often bold) // - Located in a container with "Marker" or "Dot" in the name // - Have a clear naming pattern (e.g., "1", "2", "3" or "A", "B", "C") ## Step 3: Scan Target UI Elements // Get all potential target elements that annotations might refer to scan_nodes_by_types(nodeId: "selected-node-id", types: ["COMPONENT", "INSTANCE", "FRAME"]) ## Step 4: Match Annotations to Targets Match each annotation to its target UI element using these strategies in order of priority: 1. Path-Based Matching: - Look at the marker's parent container name in the Figma layer hierarchy - Remove any "Marker:" or "Annotation:" prefixes from the parent name - Find UI elements that share the same parent name or have it in their path 2. Name-Based Matching: - Extract key terms from the annotation description - Look for UI elements whose names contain these key terms - Particularly effective for form fields, buttons, and labeled components 3. Proximity-Based Matching (fallback): - Calculate the center point of the marker using its bounds - Find the closest UI element by measuring distances to element centers - Use this method when other matching strategies fail ## Step 5: Verify Results After converting annotations, verify with: get_annotations(nodeId: "selected-node-id") get_screenshot(nodeIds: ["selected-node-id"], format: "PNG", scale: 0.5) This strategy focuses on practical implementation based on real-world usage patterns, emphasizing the importance of handling various UI elements as annotation targets.
Versions
The database has no other skills named annotation-conversion.
Database snapshot: 13.11.2026 · package version 1c51bb56e064 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · 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… - 100figma-canvas-authoring
Legacy compatibility entry. Use only when design-in-figma is not installed; otherwise use design-in-figma. Create or update native, editable Figma designs with TemPad Dev MCP: screens, flows, components, and requested local design-system resources, including on an empty canvas.… - 92design-strategy
Best practices for creating and modifying Figma designs with the figma-mcp-rust tools. Use when building screens or UI in Figma (forms, login pages, cards, layouts), covering layout hierarchy, naming, containers, element creation order, and verification. - 90annotations-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… - 100design-in-figma
Create or update native, editable Figma designs with TemPad Dev MCP: screens, flows, components, and requested local design-system resources, including on an empty canvas. Use when asked to create, mock up, or edit native Figma layers, not Figma-to-code, critique without edits,… - 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",…