[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75B3K427PFQTYE8TKXW6NST":3,"skill-same:01M75B3K427PFQTYE8TKXW6NST":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75B3K427PFQTYE8TKXW6NST","figma-shaders",null,"**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.","sure-scale\u002Fdoc-haus","sure-scale","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F282511471?v=4","01M75B01D5K1FE0HVC061PM46S","01M75B01E8V6PACDS15PW1JQK0",82,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-shaders\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: figma-shaders\ndescription: \"**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.\"\ndisable-model-invocation: false\n---\n\n# Create and update Figma shaders\n\nLoad 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.\n\nShaders have two kinds:\n\n- `effect` samples and transforms the rendered layer beneath it. Use it for blur, distortion, glow, color grading, pixelation, halftone, or other post-processing.\n- `fill` generates pixels without an input raster. Use it for gradients, patterns, noise, textures, and procedural backgrounds.\n\nDo not silently switch kinds during an update. The `kind` passed to `update_shader` must match the existing shader.\n\n## Create workflow\n\n1. Decide whether the request is an effect or fill. Ask only when the visual intent does not resolve the distinction.\n2. 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.\n3. Call `create_shader` once with a concise name, description, selected `kind`, and `planKey`. This creates a starter scaffold, not the requested final shader.\n4. 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.\n5. Author the complete replacement `main.ts` for the requested result.\n6. 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`.\n\nNever stop after `create_shader`: the starter scaffold is only a structural starting point.\n\n## Update workflow\n\n1. Identify the shader with `list_shaders`, then call `get_shader`. Use its `type` (`effect` or `fill`) as the required update kind.\n2. Read every source URI returned by `get_shader` before editing. If the client cannot read MCP resources, call it with `includeSource: true`. Treat those files as the current source of truth.\n3. Preserve existing controls and behavior unless the user asks to change them.\n4. Call `update_shader` with the complete replacement `main.ts` in the `files` array, not a diff or partial fragment. An empty `files` array is valid only for a metadata-only update.\n\n## Authoring rules\n\n- Before writing the `main.ts` replacement, read [Shader source authoring](references\u002Fauthoring.md). It contains the required module shape, WebGPU lifecycle, supported parameter schemas, effect\u002Ffill alpha rules, and WGSL failure checklist.\n- Match animation metadata to the source. Set `metadata.isAnimated: true` if `main.ts` reads `frame.time`, `frame.deltaTime`, or `frame.frame`, and set `metadata.usesMouse: true` if it reads `frame.mousePosition`. Set the corresponding value to `false` when removing the last such use. `update_shader` applies these metadata fields to the fixed `features.json` manifest even though that file cannot be replaced directly.\n- Prefer `frame.time` for animation so skipped frames do not change the result. It is an absolute millisecond clock; convert it to seconds with `Number(frame.time) * 0.001` when useful.\n- Expose controls for values users are likely to tune per layer; hardcode implementation details.\n- Keep numeric ranges bounded and defaults visually useful.\n- For effects, sample the input raster intentionally. For fills, do not assume an input raster exists.\n- Treat a non-error `update_shader` result as success. Record the returned version when present; a successful response may omit it.\n- 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.\n- 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.\n\n## Completion\n\nReport 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.\n\n`https:\u002F\u002Fwww.figma.com\u002Ffile\u002Fnew?try-tool-resource-content-id=\u003Cid>&try-tool-resource-type=\u003Cgen_effect|gen_fill>&type=design&mode=design`\n\nAfter 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.\n\nReplace the type placeholder with exactly one value; do not include angle brackets or the pipe in the returned URL.\n","# Create and update Figma shaders\n\nLoad 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.\n\nShaders have two kinds:\n\n- `effect` samples and transforms the rendered layer beneath it. Use it for blur, distortion, glow, color grading, pixelation, halftone, or other post-processing.\n- `fill` generates pixels without an input raster. Use it for gradients, patterns, noise, textures, and procedural backgrounds.\n\nDo not silently switch kinds during an update. The `kind` passed to `update_shader` must match the existing shader.\n\n## Create workflow\n\n1. Decide whether the request is an effect or fill. Ask only when the visual intent does not resolve the distinction.\n2. 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.\n3. Call `create_shader` once with a concise name, description, selected `kind`, and `planKey`. This creates a starter scaffold, not the requested final shader.\n4. 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.\n5. Author the complete replacement `main.ts` for the requested result.\n6. 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`.\n\nNever stop after `create_shader`: the starter scaffold is only a structural starting point.\n\n## Update workflow\n\n1. Identify the shader with `list_shaders`, then call `get_shader`. Use its `type` (`effect` or `fill`) as the required update kind.\n2. Read every source URI returned by `get_shader` before editing. If the client cannot read MCP resources, call it with `includeSource: true`. Treat those files as the current source of truth.\n3. Preserve existing controls and behavior unless the user asks to change them.\n4. Call `update_shader` with the complete replacement `main.ts` in the `files` array, not a diff or partial fragment. An empty `files` array is valid only for a metadata-only update.\n\n## Authoring rules\n\n- Before writing the `main.ts` replacement, read [Shader source authoring](references\u002Fauthoring.md). It contains the required module shape, WebGPU lifecycle, supported parameter schemas, effect\u002Ffill alpha rules, and WGSL failure checklist.\n- Match animation metadata to the source. Set `metadata.isAnimated: true` if `main.ts` reads `frame.time`, `frame.deltaTime`, or `frame.frame`, and set `metadata.usesMouse: true` if it reads `frame.mousePosition`. Set the corresponding value to `false` when removing the last such use. `update_shader` applies these metadata fields to the fixed `features.json` manifest even though that file cannot be replaced directly.\n- Prefer `frame.time` for animation so skipped frames do not change the result. It is an absolute millisecond clock; convert it to seconds with `Number(frame.time) * 0.001` when useful.\n- Expose controls for values users are likely to tune per layer; hardcode implementation details.\n- Keep numeric ranges bounded and defaults visually useful.\n- For effects, sample the input raster intentionally. For fills, do not assume an input raster exists.\n- Treat a non-error `update_shader` result as success. Record the returned version when present; a successful response may omit it.\n- 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.\n- 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.\n\n## Completion\n\nReport 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.\n\n`https:\u002F\u002Fwww.figma.com\u002Ffile\u002Fnew?try-tool-resource-content-id=\u003Cid>&try-tool-resource-type=\u003Cgen_effect|gen_fill>&type=design&mode=design`\n\nAfter 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.\n\nReplace the type placeholder with exactly one value; do not include angle brackets or the pipe in the returned URL.\n",{"name":5,"description":7,"disable-model-invocation":19},"dochaus","4fa71c1afaa510e46a51760c035a6be7350a4bfe","packages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-shaders",23,"https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus","https:\u002F\u002Fdoc.haus","https:\u002F\u002Fgithub.com\u002Fsure-scale","2026-11-14 21:10:36",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add sure-scale\u002Fdoc-haus --skill figma-shaders",{"tool":37,"command":38},"bunx","bunx skills add sure-scale\u002Fdoc-haus --skill figma-shaders",{"tool":40,"command":41},"pnpm","pnpm dlx skills add sure-scale\u002Fdoc-haus --skill figma-shaders","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-shaders\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fauthoring.md","REFERENCE","参考文档",10995,"https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-shaders\u002Freferences\u002Fauthoring.md",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M75B44S57BSW28BPNSY32KM3","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\u002Fedit\u002Fdelete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-use\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M75B41F6YZ7GGZR11247RWP4","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.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-use-slides\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75B3XJZ4RQEVMRB8KJEZCXW","figma-use-motion","Motion \u002F 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.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-use-motion\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75B3TSPBY2M1V5RJGDYMP60","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.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-use-figjam\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75B3NXNVRF8RRK5771619D6","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 \u002F screens \u002F 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 \u002F an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-swiftui\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M75B3EXNG0J87H7BPNT36AZH","figma-implement-motion","Translates Figma motion and animations into production-ready application code. Use when implementing animation\u002Fmotion 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`.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-implement-motion\u002FSKILL.md",[],[]]