figma-component-propertieslisted

Add, edit, and delete Figma component properties (TEXT, BOOLEAN, INSTANCE_SWAP, VARIANT) on a COMPONENT or COMPONENT_SET, and instantiate a component then set its instance properties. Use when authoring or wiring up a component's API in Figma — triggers: 'add a component property', 'add a boolean prop to this component', 'make this text a component property', 'add an instance-swap slot', 'create a variant property', 'rename/delete a component property', 'place an instance of this component', 'instantiate this component and set its label/state', 'set properties on this instance'. Properties must be added to the parent COMPONENT_SET, not individual variants. NOT covered by the native MCP's read-only get_design_context/get_metadata.
whiskfernlowdensitylipoprotein154/figma-console-mcp-skills · ★ 0 · Web & Frontend · score 75

Install: claude install-skill whiskfernlowdensitylipoprotein154/figma-console-mcp-skills

# figma-component-properties — define a component's API + instantiate it Two related jobs: 1. **Author the component's property API** — add/edit/delete `TEXT`, `BOOLEAN`, `INSTANCE_SWAP`, and `VARIANT` properties so the component exposes the right knobs (the Figma equivalent of a React component's props). 2. **Use the component** — create an instance and set its properties (label text, boolean toggles, variant selection, swapped sub-instances). ## Skill boundaries - **`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). - **Reading a component's existing property definitions / state machine** → use `figma-analyze-component-set` or `figma-deep-component`. - These are **design-system authoring writes** the native MCP's `get_design_context` / `get_metadata` (read-only) do not cover. ## Property types | Type | What it controls | `defaultValue` | Notes | | --- | --- | --- | --- | | `TEXT` | A text-layer string override | `"Label"` | Bind in UI to a text node's characters | | `BOOLEAN` | Show/hide a layer | `true`/`false` | Bind to a layer's