Create and update Figma shaders

Load this skill before every create_shader or update_shader call. It covers account-library shader authoring through the Figma MCP server. Reading or applying an existing shader does not require this skill.

Shaders have two kinds:

• effect samples and transforms the rendered layer beneath it. Use it for blur, distortion, glow, color grading, pixelation, halftone, or other post-processing.
• fill generates pixels without an input raster. Use it for gradients, patterns, noise, textures, and procedural backgrounds.

Do not silently switch kinds during an update. The kind passed to update_shader must match the existing shader.

Create workflow

1. Decide whether the request is an effect or fill. Ask only when the visual intent does not resolve the distinction.
2. Resolve planKey. Reuse one supplied by the user; otherwise call whoami. Use the sole eligible plan automatically, or ask the user to choose when several materially different plans are available.
3. Call create_shader once with a concise name, description, selected kind, and planKey. This creates a starter scaffold, not the requested final shader.
4. Call get_shader with the returned id, then read every source URI. If the client cannot read MCP resources, call get_shader with includeSource: true instead. This establishes the runtime imports and the scaffold's fixed metadata contract.
5. Author the complete replacement main.ts for the requested result.
6. Call update_shader with the returned id, the same kind, files: [{ path: "main.ts", content: "..." }], and a specific commitMessage. Use metadata when changing the name, description, or animation capabilities. Set metadata.isAnimated: true when the source reads time-related frame inputs and metadata.usesMouse: true when it reads frame.mousePosition.