figma-ops

# Figma Operations The front door for Figma work. The official Figma plugin ships eleven skills that own the Plugin API surface; the community ships fifty more for tokens, components, a11y and docs. **This skill does not replicate any of them.** It does three things they don't: 1. **Routes** — says which skill or tool to load for a given job (§1). 2. **Composes** — capture → curate → arrange workflows for moodboards, reference boards and any "put these images in Figma, beautifully" request (§3–§5). 3. **Guards** — the canvas craft rules that sit *above* the API rules: aspect ratio, z-order, overlap budgets, verification loops, page hygiene (§6). > **Always load `figma-use` before any `use_figma` call.** It is the source of truth > for the Plugin API and its gotchas. This skill assumes it is loaded and cites its > references rather than restating them. ## 1. Router — which skill for which job | The job | Load | Tool it wraps | |---|---|---| | Any script that mutates or reads the canvas | `figma-use` (mandatory prerequisite) | `use_figma` | | Design → code, implement a screen | the design-to-code guidance served as MCP resource `skill://figma/figma-design-to-code/SKILL.md` (not a plugin skill) | `get_design_context`, `get_screenshot` | | SwiftUI ↔ Figma, either direction | `figma-swiftui` | `get_design_context`, `use_figma` | | Build a page/screen *from* app code | `figma-generate-design` + `figma-use` | `use_figma`, `generate_figma_design` | | Tokens, variables, com...