[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0HMMMKQ7CFEPEZ3F8ER4Z":3,"skill-same:01M7F0HMMMKQ7CFEPEZ3F8ER4Z":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F0HMMMKQ7CFEPEZ3F8ER4Z","figma-design-tool-workflows",null,"Figma mastery and design-to-code: Auto Layout, component architecture, variable modes, Dev Mode handoff, Figma MCP server integration, Code Connect, and token pipelines. Use when working in Figma, converting designs to code, or setting up a design-to-code flywheel.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Ffigma-design-tool-workflows\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: figma-design-tool-workflows\ndescription: \"Figma mastery and design-to-code: Auto Layout, component architecture, variable modes, Dev Mode handoff, Figma MCP server integration, Code Connect, and token pipelines. Use when working in Figma, converting designs to code, or setting up a design-to-code flywheel.\"\nallowed-tools: Read, Grep, Glob\n---\n\n# Figma Design Tool Workflows\n\nTreat Figma as the design system of record: every layer name, component property, and variable is data that flows into code generation, token pipelines, accessibility audits, and visual regression. A sloppy file produces sloppy code.\n\n## Component Architecture\n\n- **Property types map to code props:** boolean → optional boolean prop (conditional render); text → `label`\u002F`children`; instance swap → slot prop (`icon?: ReactNode`); preferred values curate the swap picker.\n- **Variants** for visually distinct states that change several properties at once (`variant` x `size`). **Component properties** for independent toggles (an icon on\u002Foff) so the variant count does not double. **Separate components** when there is no shared structure.\n- **Nested sub-components** (`CardHeader`, `CardBody`, `CardFooter`) via instance swap slots mirror React compound components.\n- **Naming:** `Category\u002FType\u002FState` (`Button\u002FPrimary\u002FHover`, `Input\u002FText\u002FError`), matching code directory structure.\n\n## Variable Modes\n\nThree collections: **primitive** (raw values, one mode), **semantic** (light\u002Fdark\u002Fhigh-contrast modes), **component** (bindings; modes for density or brand). Switching a frame's mode previews every permutation without duplicate frames. Variable names must match CSS custom property or token names in code.\n\n## Auto Layout Rules\n\n- Every component uses Auto Layout; if it can't, rethink the design.\n- Bind padding and gap to spacing variables so density modes work.\n- Fill container = `flex: 1`; Hug contents = `width: auto`.\n- Absolute positioning only for overlays such as avatar badges and FABs (`position: absolute` in a relative parent).\n\n## Dev Mode\n\nDevelopers see props, CSS values, variable names instead of raw values, annotations, snippets, and measurements. Output quality depends entirely on naming, variable binding, and Auto Layout.\n\n## Figma MCP and the Flywheel\n\nThe Figma MCP server lets an agent read file structure, component properties and variants, variables and modes, Auto Layout specs, styles, and prototype flows. The flywheel: **Design** with proper architecture → **Read** via MCP → **Generate** typed component, token-based styles, Storybook stories, tests → **Validate** with visual regression (Chromatic, Percy) and axe-core → **Iterate** on Figma changes → **Ship** through CI and the token pipeline. Later passes are cheaper than the first; measure the saving on your own components before quoting a number.\n\n## Routing\n\n| Question | Read |\n|---|---|\n| Auto Layout in depth, component architecture, variable modes, prototyping, Dev Mode, library management, naming and file organization, plugins, shortcuts, canvas-to-code mapping summary | `references\u002Ffigma-mastery-workflows.md` |\n| Pipeline architecture, Style Dictionary config, token transforms, CI\u002FCD, visual regression, Storybook, multi-brand, accessibility in the pipeline | `references\u002Fdesign-to-code-pipeline.md` |\n| MCP server setup and tools, the flywheel, Card walkthrough, Code Connect, token extraction, prompt templates, quality gates, ROI | `references\u002Ffigma-mcp-ai-flywheel.md` |\n\n## Cross-References\n\n- Component code patterns MCP output should follow: `component-patterns-code`\n- Token hierarchy, versioning, contribution and change management: `design-systems-architecture`\n- Color, type scale, spacing, and elevation behind variable collections: `visual-design-mastery`\n- Accessibility plugins, contrast, focus order and screen reader annotations: `accessibility-inclusive-design`\n- Prototyping, smart animate, motion tokens: `interaction-motion-design`\n\n## Key Sources\n\n- Figma official documentation: Components, Variables, Auto Layout, Dev Mode, Code Connect\n- Figma MCP server documentation and API reference\n- Style Dictionary documentation for multi-platform token transformation\n- Tokens Studio (Figma plugin) documentation for token management\n- Chromatic documentation for visual regression testing with Storybook\n- W3C Design Tokens Community Group specification for token format\n","# Figma Design Tool Workflows\n\nTreat Figma as the design system of record: every layer name, component property, and variable is data that flows into code generation, token pipelines, accessibility audits, and visual regression. A sloppy file produces sloppy code.\n\n## Component Architecture\n\n- **Property types map to code props:** boolean → optional boolean prop (conditional render); text → `label`\u002F`children`; instance swap → slot prop (`icon?: ReactNode`); preferred values curate the swap picker.\n- **Variants** for visually distinct states that change several properties at once (`variant` x `size`). **Component properties** for independent toggles (an icon on\u002Foff) so the variant count does not double. **Separate components** when there is no shared structure.\n- **Nested sub-components** (`CardHeader`, `CardBody`, `CardFooter`) via instance swap slots mirror React compound components.\n- **Naming:** `Category\u002FType\u002FState` (`Button\u002FPrimary\u002FHover`, `Input\u002FText\u002FError`), matching code directory structure.\n\n## Variable Modes\n\nThree collections: **primitive** (raw values, one mode), **semantic** (light\u002Fdark\u002Fhigh-contrast modes), **component** (bindings; modes for density or brand). Switching a frame's mode previews every permutation without duplicate frames. Variable names must match CSS custom property or token names in code.\n\n## Auto Layout Rules\n\n- Every component uses Auto Layout; if it can't, rethink the design.\n- Bind padding and gap to spacing variables so density modes work.\n- Fill container = `flex: 1`; Hug contents = `width: auto`.\n- Absolute positioning only for overlays such as avatar badges and FABs (`position: absolute` in a relative parent).\n\n## Dev Mode\n\nDevelopers see props, CSS values, variable names instead of raw values, annotations, snippets, and measurements. Output quality depends entirely on naming, variable binding, and Auto Layout.\n\n## Figma MCP and the Flywheel\n\nThe Figma MCP server lets an agent read file structure, component properties and variants, variables and modes, Auto Layout specs, styles, and prototype flows. The flywheel: **Design** with proper architecture → **Read** via MCP → **Generate** typed component, token-based styles, Storybook stories, tests → **Validate** with visual regression (Chromatic, Percy) and axe-core → **Iterate** on Figma changes → **Ship** through CI and the token pipeline. Later passes are cheaper than the first; measure the saving on your own components before quoting a number.\n\n## Routing\n\n| Question | Read |\n|---|---|\n| Auto Layout in depth, component architecture, variable modes, prototyping, Dev Mode, library management, naming and file organization, plugins, shortcuts, canvas-to-code mapping summary | `references\u002Ffigma-mastery-workflows.md` |\n| Pipeline architecture, Style Dictionary config, token transforms, CI\u002FCD, visual regression, Storybook, multi-brand, accessibility in the pipeline | `references\u002Fdesign-to-code-pipeline.md` |\n| MCP server setup and tools, the flywheel, Card walkthrough, Code Connect, token extraction, prompt templates, quality gates, ROI | `references\u002Ffigma-mcp-ai-flywheel.md` |\n\n## Cross-References\n\n- Component code patterns MCP output should follow: `component-patterns-code`\n- Token hierarchy, versioning, contribution and change management: `design-systems-architecture`\n- Color, type scale, spacing, and elevation behind variable collections: `visual-design-mastery`\n- Accessibility plugins, contrast, focus order and screen reader annotations: `accessibility-inclusive-design`\n- Prototyping, smart animate, motion tokens: `interaction-motion-design`\n\n## Key Sources\n\n- Figma official documentation: Components, Variables, Auto Layout, Dev Mode, Code Connect\n- Figma MCP server documentation and API reference\n- Style Dictionary documentation for multi-platform token transformation\n- Tokens Studio (Figma plugin) documentation for token management\n- Chromatic documentation for visual regression testing with Storybook\n- W3C Design Tokens Community Group specification for token format\n",{"name":5,"description":7,"allowed-tools":24},"Read, Grep, Glob","main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fdesign-ops\u002Fskills\u002Ffigma-design-tool-workflows","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill figma-design-tool-workflows",{"tool":39,"command":40},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill figma-design-tool-workflows",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill figma-design-tool-workflows","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Ffigma-design-tool-workflows\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fdesign-to-code-pipeline.md","REFERENCE","参考文档",41952,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Ffigma-design-tool-workflows\u002Freferences\u002Fdesign-to-code-pipeline.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Ffigma-mastery-workflows.md",42808,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Ffigma-design-tool-workflows\u002Freferences\u002Ffigma-mastery-workflows.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Ffigma-mcp-ai-flywheel.md",38976,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Ffigma-design-tool-workflows\u002Freferences\u002Ffigma-mcp-ai-flywheel.md",[62,68,75,82,89,96],{"skillNo":63,"name":64,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]