[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EN0WH6M56RTNP5CCQEK9NP":3,"skill-same:01M7EN0WH6M56RTNP5CCQEK9NP":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"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":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EN0WH6M56RTNP5CCQEK9NP","ams-figma-pro-dev",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-figma-pro-dev\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: figma-pro-dev\ndescription: Developer-Figma collaboration: dev mode, design tokens, component inspection, handoff, and design-system alignment. Use when implementing designs from Figma or aligning code with a design system.\ncategory: development\n---\n\n# Figma Pro (Dev)\n\n## Overview\n\nFor developers, Figma is **the source of truth for what to build** — and the collaboration surface\nwith designers. Professional Figma usage from the dev side means: extracting specs efficiently (dev\nmode), consuming design tokens as code, implementing components to match the design system's\nintent (not just pixels), and giving designers feedback that improves the handoff both ways.\n\nThe through-line: implement the *system*, not the screenshot — tokens, components, and behaviors,\nnot one-off pixel values.\n\n## When to use\n\n- Implementing UI from Figma designs.\n- Extracting design tokens (colors, type, spacing) into code.\n- Reviewing designs for implementability before building.\n- Setting up design-token pipelines (Style Dictionary, Tokens Studio).\n- Giving designers developer-friendly feedback.\n\n## Core concepts\n\n- **Dev Mode as the interface.** Inspect mode: measurements, colors, typography, assets export,\n  and code snippets (CSS\u002FiOS\u002FAndroid). Compare designs vs implementation (visual diffing); focus\n  on tokens and components, not copying generated CSS verbatim.\n- **Design tokens, not hex codes.** Colors, typography scales, spacing, radii, shadows defined as\n  named tokens in Figma Variables — exported to code (Style Dictionary, Tokens Studio) as the\n  single source of truth. Hardcoded `#3B82F6` in code while Figma says `color\u002Fprimary\u002F600` is\n  drift waiting to happen.\n- **Components map to components.** Figma components (with variants, auto-layout, properties)\n  should correspond 1:1 with code components (props = Figma properties). Mismatched granularity —\n  Figma has 3 button variants, code has 12 — signals a broken handoff conversation.\n- **Auto-layout ≈ flexbox.** Figma's auto-layout maps directly to flexbox concepts (direction,\n  gap, padding, alignment). Designs built with auto-layout translate to responsive code naturally;\n  absolutely-positioned-everything designs fight responsiveness — flag it early.\n- **Behaviors, not just visuals.** Hover\u002Ffocus\u002Fdisabled\u002Ferror\u002Floading states, responsive behavior\n  at breakpoints, animation specs (duration, easing), and content edge cases (long names, empty\n  states). A design without states is a spec with holes — ask before assuming.\n- **Two-way feedback.** Developers reviewing designs for: implementability (custom vs system\n  components), accessibility (contrast, focus, touch targets), and edge cases. Designers need this\n  input *before* final sign-off, not after implementation starts.\n\n## Practical workflow\n\n1. **Before building: review the design.** Check: tokens used (not raw values)? components from\n   the library (not one-offs)? all states designed? responsive behavior specified? If not, ask —\n   assumptions now are rework later.\n2. **Set up the token pipeline.** Export Figma Variables → transform (Style Dictionary) → code\n   tokens (CSS custom properties, Tailwind theme, platform resources). Automated, versioned,\n   and the *only* way colors\u002Ftype\u002Fspacing enter the codebase.\n3. **Map components 1:1.** For each Figma component: the code component, its props (matching\n   Figma properties\u002Fvariants), and its states. Build the mapping explicitly for design-system\n   work; it becomes the contract.\n4. **Implement from tokens + components.** Compose screens from the component library using\n   tokens; new one-off styles are a design-system conversation, not a solo decision.\n5. **Verify visually.** Screenshot\u002Fsnapshot tests for components; side-by-side review with the\n   designer for key screens; check responsive breakpoints and states, not just the happy-path\n   desktop frame.\n6. **Close the loop.** Implementation discoveries (a state nobody designed, a breakpoint that\n   breaks) go back to the designer *and* into the design system. Handoff is a conversation, not\n   a handover.\n\nToken pipeline sketch:\n\n```text\nFigma Variables (color\u002Fprimary\u002F600, spacing\u002F4, radius\u002Flg, ...)\n   → Tokens Studio \u002F Variables export (JSON)\n   → Style Dictionary transform\n   → code: CSS custom props \u002F Tailwind @theme \u002F SwiftUI \u002F Compose resources\n   → consumed by components; CI verifies no raw values (lint rule)\n```\n\nDev checklist per screen:\n\n```text\n[ ] All colors\u002Ftype\u002Fspacing from tokens (no raw values)\n[ ] Components from the library (props match Figma variants)\n[ ] All states implemented (hover, focus, disabled, loading, error, empty)\n[ ] Responsive behavior verified at defined breakpoints\n[ ] Assets exported at right sizes\u002Fformats (SVG for icons, right densities)\n[ ] Accessibility: contrast, focus order, touch targets (44px+)\n```\n\n## Common pitfalls\n\n- **Pixel-copying screenshots.** Measuring pixels from a static frame instead of using tokens and\n  components — brittle, unresponsive, and drifts from the system on the next design update.\n- **Raw values in code.** Hardcoded hex\u002Fspacing \"to match the design\" while tokens exist. Lint\n  against it; tokens are the contract.\n- **Ignoring states.** Building only the default state — hover, focus, error, empty, and loading\n  get invented during implementation (inconsistently). Demand state coverage in design review.\n- **One-off components.** Building bespoke components for what the design system already covers\n  (or should). Every one-off is design-system debt — route it through the system conversation.\n- **No responsive spec.** Desktop frame only, \"we'll figure out mobile later.\" Later is rework.\n  Auto-layout-first designs + breakpoint specs before implementation.\n- **Copying generated code.** Pasting Figma's generated CSS verbatim — absolute positioning,\n  magic numbers, no responsiveness. Generated code is a *reference*, not an implementation.\n- **Silent divergence.** Implementation drifting from design with no conversation (or design\n  changing without telling devs). Regular design-engineering syncs; the mapping is a living contract.\n","# Figma Pro (Dev)\n\n## Overview\n\nFor developers, Figma is **the source of truth for what to build** — and the collaboration surface\nwith designers. Professional Figma usage from the dev side means: extracting specs efficiently (dev\nmode), consuming design tokens as code, implementing components to match the design system's\nintent (not just pixels), and giving designers feedback that improves the handoff both ways.\n\nThe through-line: implement the *system*, not the screenshot — tokens, components, and behaviors,\nnot one-off pixel values.\n\n## When to use\n\n- Implementing UI from Figma designs.\n- Extracting design tokens (colors, type, spacing) into code.\n- Reviewing designs for implementability before building.\n- Setting up design-token pipelines (Style Dictionary, Tokens Studio).\n- Giving designers developer-friendly feedback.\n\n## Core concepts\n\n- **Dev Mode as the interface.** Inspect mode: measurements, colors, typography, assets export,\n  and code snippets (CSS\u002FiOS\u002FAndroid). Compare designs vs implementation (visual diffing); focus\n  on tokens and components, not copying generated CSS verbatim.\n- **Design tokens, not hex codes.** Colors, typography scales, spacing, radii, shadows defined as\n  named tokens in Figma Variables — exported to code (Style Dictionary, Tokens Studio) as the\n  single source of truth. Hardcoded `#3B82F6` in code while Figma says `color\u002Fprimary\u002F600` is\n  drift waiting to happen.\n- **Components map to components.** Figma components (with variants, auto-layout, properties)\n  should correspond 1:1 with code components (props = Figma properties). Mismatched granularity —\n  Figma has 3 button variants, code has 12 — signals a broken handoff conversation.\n- **Auto-layout ≈ flexbox.** Figma's auto-layout maps directly to flexbox concepts (direction,\n  gap, padding, alignment). Designs built with auto-layout translate to responsive code naturally;\n  absolutely-positioned-everything designs fight responsiveness — flag it early.\n- **Behaviors, not just visuals.** Hover\u002Ffocus\u002Fdisabled\u002Ferror\u002Floading states, responsive behavior\n  at breakpoints, animation specs (duration, easing), and content edge cases (long names, empty\n  states). A design without states is a spec with holes — ask before assuming.\n- **Two-way feedback.** Developers reviewing designs for: implementability (custom vs system\n  components), accessibility (contrast, focus, touch targets), and edge cases. Designers need this\n  input *before* final sign-off, not after implementation starts.\n\n## Practical workflow\n\n1. **Before building: review the design.** Check: tokens used (not raw values)? components from\n   the library (not one-offs)? all states designed? responsive behavior specified? If not, ask —\n   assumptions now are rework later.\n2. **Set up the token pipeline.** Export Figma Variables → transform (Style Dictionary) → code\n   tokens (CSS custom properties, Tailwind theme, platform resources). Automated, versioned,\n   and the *only* way colors\u002Ftype\u002Fspacing enter the codebase.\n3. **Map components 1:1.** For each Figma component: the code component, its props (matching\n   Figma properties\u002Fvariants), and its states. Build the mapping explicitly for design-system\n   work; it becomes the contract.\n4. **Implement from tokens + components.** Compose screens from the component library using\n   tokens; new one-off styles are a design-system conversation, not a solo decision.\n5. **Verify visually.** Screenshot\u002Fsnapshot tests for components; side-by-side review with the\n   designer for key screens; check responsive breakpoints and states, not just the happy-path\n   desktop frame.\n6. **Close the loop.** Implementation discoveries (a state nobody designed, a breakpoint that\n   breaks) go back to the designer *and* into the design system. Handoff is a conversation, not\n   a handover.\n\nToken pipeline sketch:\n\n```text\nFigma Variables (color\u002Fprimary\u002F600, spacing\u002F4, radius\u002Flg, ...)\n   → Tokens Studio \u002F Variables export (JSON)\n   → Style Dictionary transform\n   → code: CSS custom props \u002F Tailwind @theme \u002F SwiftUI \u002F Compose resources\n   → consumed by components; CI verifies no raw values (lint rule)\n```\n\nDev checklist per screen:\n\n```text\n[ ] All colors\u002Ftype\u002Fspacing from tokens (no raw values)\n[ ] Components from the library (props match Figma variants)\n[ ] All states implemented (hover, focus, disabled, loading, error, empty)\n[ ] Responsive behavior verified at defined breakpoints\n[ ] Assets exported at right sizes\u002Fformats (SVG for icons, right densities)\n[ ] Accessibility: contrast, focus order, touch targets (44px+)\n```\n\n## Common pitfalls\n\n- **Pixel-copying screenshots.** Measuring pixels from a static frame instead of using tokens and\n  components — brittle, unresponsive, and drifts from the system on the next design update.\n- **Raw values in code.** Hardcoded hex\u002Fspacing \"to match the design\" while tokens exist. Lint\n  against it; tokens are the contract.\n- **Ignoring states.** Building only the default state — hover, focus, error, empty, and loading\n  get invented during implementation (inconsistently). Demand state coverage in design review.\n- **One-off components.** Building bespoke components for what the design system already covers\n  (or should). Every one-off is design-system debt — route it through the system conversation.\n- **No responsive spec.** Desktop frame only, \"we'll figure out mobile later.\" Later is rework.\n  Auto-layout-first designs + breakpoint specs before implementation.\n- **Copying generated code.** Pasting Figma's generated CSS verbatim — absolute positioning,\n  magic numbers, no responsiveness. Generated code is a *reference*, not an implementation.\n- **Silent divergence.** Implementation drifting from design with no conversation (or design\n  changing without telling devs). Regular design-engineering syncs; the mapping is a living contract.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-figma-pro-dev",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-figma-pro-dev",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-figma-pro-dev",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-figma-pro-dev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-figma-pro-dev\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]