[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TN36F7GDRTPQJHWEEMDXH":3,"skill-same:01M79TN36F7GDRTPQJHWEEMDXH":53},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79TN36F7GDRTPQJHWEEMDXH","tailwind-architect",null,"Architect-level Tailwind guidance — token wiring from design tokens into the theme, component-layer boundaries, when utilities are wrong, dark mode and theming strategy, and the class-explosion failure modes that make utility CSS unmaintainable. Use when setting up or auditing a Tailwind codebase.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Ftailwind-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tailwind-architect\ndescription: Architect-level Tailwind guidance — token wiring from design tokens into the theme, component-layer boundaries, when utilities are wrong, dark mode and theming strategy, and the class-explosion failure modes that make utility CSS unmaintainable. Use when setting up or auditing a Tailwind codebase.\nlicense: MIT\ncompatibility: Tailwind CSS 3.4+\u002F4.x with a token source\nmetadata:\n  crusor-domain: website-architect\n  crusor-path: website-architect\u002Ffrontend-development-architect\u002Ftailwind-architect\n  crusor-origin: original\n  crusor-sources: \"tailwindcss.com\u002Fdocs; tailwindcss.com\u002Fblog\u002Ftailwindcss-v4\"\n  crusor-triggers: \"tailwind, tailwindcss, utility css, tailwind theme, design tokens, utility classes, tailwind config, design tokens css\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Tailwind Architect\n\nTailwind is a **token delivery mechanism**, not a styling philosophy. If the\ntheme is arbitrary and the components are long class strings, you have CSS with\nextra steps.\n\n## When to use\n\n- A design system exists or is being defined and must reach the codebase.\n- A component library needs consistent spacing\u002Fcolour\u002Ftype without a CSS-in-JS\n  runtime.\n- Replacing ad-hoc CSS with a constrained scale.\n\n## When NOT to use\n\n- Content-heavy documents where semantic CSS is the better abstraction.\n- A design system with no tokens — fix the tokens first.\n\n## Decision 1 — Tokens are the source of truth\n\n- `tailwind.config` (or `@theme` in v4) maps **semantic** tokens to utilities:\n  `bg-surface`, `text-muted`, `border-subtle` — not `bg-gray-100`.\n- Raw palette values are allowed only in components that are themselves the\n  system (Button variants), never in feature code.\n- Light\u002Fdark is a token swap (CSS variables), not `dark:` scattered through\n  every component. `dark:` is for exceptions.\n- Spacing\u002Fradius\u002Fshadow scales come from the token set; new arbitrary values\n  (`p-[13px]`) are a design decision that must go back into the tokens.\n\n## Decision 2 — Where utilities stop\n\n| Layer | Owns |\n|---|---|\n| tokens | values |\n| primitives (Button, Input, Card) | variant API + class composition |\n| features | composition and layout only |\n\n- A feature file with 40 classes is a primitive that hasn't been extracted.\n- Variants live in `cva`\u002Fmaps inside the primitive, not in call sites.\n- Conditional class merging goes through one helper (`cn()`), never scattered\n  template strings.\n\n## Decision 3 — Responsiveness and layout\n\n- Mobile-first breakpoints aligned to real layout shifts, not device names.\n- Container queries for component-level responsiveness (cards, panels).\n- Grid\u002Fflex utilities define layout; components do not carry their own margins\n  (spacing belongs to the parent — the \"no external margin\" rule).\n\n## Decision 4 — Build integration\n\n- Content paths explicit; no dynamic class construction (`bg-${color}-500`) —\n  it defeats extraction. Use a safelist or a variant map instead.\n- CSS variables for theme values that must change at runtime (user theme).\n- Purge in production, verified by size budget in CI.\n\n## Failure modes at scale\n\n- Every component re-inventing spacing because the tokens are too coarse.\n- `dark:` on 300 elements → theme changes are a refactor.\n- Arbitrary values everywhere → the design system no longer constrains anything.\n- Class strings duplicated across features → one visual change, 40 edits.\n\n## Verification receipts\n\n1. Grep audit: no raw palette utilities in feature files.\n2. `bg-${` \u002F dynamic class construction: zero occurrences.\n3. Production CSS size within budget after purge.\n4. Dark\u002Flight switch verified on 3 representative pages.\n5. A new feature can be built without adding a single arbitrary value.\n","# Tailwind Architect\n\nTailwind is a **token delivery mechanism**, not a styling philosophy. If the\ntheme is arbitrary and the components are long class strings, you have CSS with\nextra steps.\n\n## When to use\n\n- A design system exists or is being defined and must reach the codebase.\n- A component library needs consistent spacing\u002Fcolour\u002Ftype without a CSS-in-JS\n  runtime.\n- Replacing ad-hoc CSS with a constrained scale.\n\n## When NOT to use\n\n- Content-heavy documents where semantic CSS is the better abstraction.\n- A design system with no tokens — fix the tokens first.\n\n## Decision 1 — Tokens are the source of truth\n\n- `tailwind.config` (or `@theme` in v4) maps **semantic** tokens to utilities:\n  `bg-surface`, `text-muted`, `border-subtle` — not `bg-gray-100`.\n- Raw palette values are allowed only in components that are themselves the\n  system (Button variants), never in feature code.\n- Light\u002Fdark is a token swap (CSS variables), not `dark:` scattered through\n  every component. `dark:` is for exceptions.\n- Spacing\u002Fradius\u002Fshadow scales come from the token set; new arbitrary values\n  (`p-[13px]`) are a design decision that must go back into the tokens.\n\n## Decision 2 — Where utilities stop\n\n| Layer | Owns |\n|---|---|\n| tokens | values |\n| primitives (Button, Input, Card) | variant API + class composition |\n| features | composition and layout only |\n\n- A feature file with 40 classes is a primitive that hasn't been extracted.\n- Variants live in `cva`\u002Fmaps inside the primitive, not in call sites.\n- Conditional class merging goes through one helper (`cn()`), never scattered\n  template strings.\n\n## Decision 3 — Responsiveness and layout\n\n- Mobile-first breakpoints aligned to real layout shifts, not device names.\n- Container queries for component-level responsiveness (cards, panels).\n- Grid\u002Fflex utilities define layout; components do not carry their own margins\n  (spacing belongs to the parent — the \"no external margin\" rule).\n\n## Decision 4 — Build integration\n\n- Content paths explicit; no dynamic class construction (`bg-${color}-500`) —\n  it defeats extraction. Use a safelist or a variant map instead.\n- CSS variables for theme values that must change at runtime (user theme).\n- Purge in production, verified by size budget in CI.\n\n## Failure modes at scale\n\n- Every component re-inventing spacing because the tokens are too coarse.\n- `dark:` on 300 elements → theme changes are a refactor.\n- Arbitrary values everywhere → the design system no longer constrains anything.\n- Class strings duplicated across features → one visual change, 40 edits.\n\n## Verification receipts\n\n1. Grep audit: no raw palette utilities in feature files.\n2. `bg-${` \u002F dynamic class construction: zero occurrences.\n3. Production CSS size within budget after purge.\n4. Dark\u002Flight switch verified on 3 representative pages.\n5. A new feature can be built without adding a single arbitrary value.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"website-architect\u002Ffrontend-development-architect\u002Ftailwind-architect","website-architect","original","tailwindcss.com\u002Fdocs; tailwindcss.com\u002Fblog\u002Ftailwindcss-v4","tailwind, tailwindcss, utility css, tailwind theme, design tokens, utility classes, tailwind config, design tokens css","2026-10-30","Tailwind CSS 3.4+\u002F4.x with a token source","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Ftailwind-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill tailwind-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill tailwind-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill tailwind-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Ftailwind-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"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},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\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},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\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},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\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},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\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},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]