figma-shaders
**MANDATORY prerequisite** — load this skill before calling `create_shader` or `update_shader`. Use when the user asks to create, author, change, fix, or iterate on a shader effect, shader fill, custom effect, custom fill, or procedural shader in Figma.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 82
- Forks
- 23
01 前言 Front Matter
- name
- figma-shaders
- description
- **MANDATORY prerequisite** — load this skill before calling `create_shader` or `update_shader`. Use when the user asks to create, author, change, fix, or iterate on a shader effect, shader fill, custom effect, custom fill, or procedural shader in Figma.
- disable-model-invocation
- false
02 资源文件 1
- 参考文档references/authoring.md10.7 KB
03 SKILL.md 正文
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:
effectsamples and transforms the rendered layer beneath it. Use it for blur, distortion, glow, color grading, pixelation, halftone, or other post-processing.fillgenerates 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
- Decide whether the request is an effect or fill. Ask only when the visual intent does not resolve the distinction.
- Resolve
planKey. Reuse one supplied by the user; otherwise callwhoami. Use the sole eligible plan automatically, or ask the user to choose when several materially different plans are available. - Call
create_shaderonce with a concise name, description, selectedkind, andplanKey. This creates a starter scaffold, not the requested final shader. - Call
get_shaderwith the returnedid, then read every source URI. If the client cannot read MCP resources, callget_shaderwithincludeSource: trueinstead. This establishes the runtime imports and the scaffold's fixed metadata contract. - Author the complete replacement
main.tsfor the requested result. - Call
update_shaderwith the returnedid, the samekind,files: [{ path: "main.ts", content: "..." }], and a specificcommitMessage. Usemetadatawhen changing the name, description, or animation capabilities. Setmetadata.isAnimated: truewhen the source reads time-related frame inputs andmetadata.usesMouse: truewhen it readsframe.mousePosition.
Never stop after create_shader: the starter scaffold is only a structural starting point.
Update workflow
- Identify the shader with
list_shaders, then callget_shader. Use itstype(effectorfill) as the required update kind. - Read every source URI returned by
get_shaderbefore editing. If the client cannot read MCP resources, call it withincludeSource: true. Treat those files as the current source of truth. - Preserve existing controls and behavior unless the user asks to change them.
- Call
update_shaderwith the complete replacementmain.tsin thefilesarray, not a diff or partial fragment. An emptyfilesarray is valid only for a metadata-only update.
Authoring rules
- Before writing the
main.tsreplacement, read Shader source authoring. It contains the required module shape, WebGPU lifecycle, supported parameter schemas, effect/fill alpha rules, and WGSL failure checklist. - Match animation metadata to the source. Set
metadata.isAnimated: trueifmain.tsreadsframe.time,frame.deltaTime, orframe.frame, and setmetadata.usesMouse: trueif it readsframe.mousePosition. Set the corresponding value tofalsewhen removing the last such use.update_shaderapplies these metadata fields to the fixedfeatures.jsonmanifest even though that file cannot be replaced directly. - Prefer
frame.timefor animation so skipped frames do not change the result. It is an absolute millisecond clock; convert it to seconds withNumber(frame.time) * 0.001when useful. - Expose controls for values users are likely to tune per layer; hardcode implementation details.
- Keep numeric ranges bounded and defaults visually useful.
- For effects, sample the input raster intentionally. For fills, do not assume an input raster exists.
- Treat a non-error
update_shaderresult as success. Record the returned version when present; a successful response may omit it. - On a build error, use the returned compiler output to make the smallest source correction and retry once. If it still fails, surface the error instead of repeatedly rewriting the shader.
- If the tool reports that animation or mouse input is unavailable, treat that as a terminal capability gate: do not retry or attempt to bypass it. Offer to author a static shader whose exposed properties can be keyframed in Motion mode instead.
Completion
Report the shader name, kind, and id, plus the returned version when present. Briefly identify the controls or behavior that were added. Construct and include a clickable URL that opens a new Design file with the unpublished shader ready to try, using the exact shader id as try-tool-resource-content-id. Set try-tool-resource-type from the shader kind: gen_effect for an effect and gen_fill for a fill.
https://www.figma.com/file/new?try-tool-resource-content-id=<id>&try-tool-resource-type=<gen_effect|gen_fill>&type=design&mode=design
After presenting the new-file link, ask whether the user wants to open the shader in an existing Figma Design file instead. If yes, reuse a file URL already provided or ask for one, then add the same try-tool-resource-content-id and resolved try-tool-resource-type query parameters to that URL. Never guess the file URL.
Replace the type placeholder with exactly one value; do not include angle brackets or the pipe in the returned URL.
04 同仓库更多 Skills
figma-use
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.
figma-use-slides
This skill helps agents use Figma's use_figma MCP tool in the Slides context. Can be used alongside figma-use which has foundational context for using the use_figma tool.
figma-use-motion
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
figma-use-figjam
This skill helps agents use Figma's use_figma MCP tool in the FigJam context. Can be used alongside figma-use which has foundational context for using the use_figma tool.
figma-swiftui
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.
figma-implement-motion
Translates Figma motion and animations into production-ready application code. Use when implementing animation/motion from a Figma design — user mentions "implement this motion", "add animation from Figma", "animate this component", provides a Figma URL whose node is animated, or when `get_design_context` returns motion data or instructs you to call `get_motion_context`.