[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7PXNKN2QDYX5N124F3XT3":3,"skill-same:01M6H7PXNKN2QDYX5N124F3XT3":72},{"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":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6H7PXNKN2QDYX5N124F3XT3","tailwind-css-expert",null,"Use when implementing tailwind css functionality with production-grade patterns and safeguards.","0xharryriddle\u002Fcodex-field-kit","0xharryriddle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100945007?v=4","01M6H686JV0QKZYP2RWG6B2B8T","harryriddle","01M6H686PVZ8JGKWEG7B3GM5PD",3,"MIT","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Ftailwind-css-expert\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"css","Tailwind","expert","Tailwind CSS","css expert","tailwind css expert","frontend","codex","ui","Production","use","patterns","with","kit","implementing","2026-11-10 10:12:30",false,"---\nname: tailwind-css-expert\ndescription: Use when implementing tailwind css functionality with production-grade patterns and safeguards.\nmetadata:\n  hermes:\n    tags: [codex-agent, frontend-ui]\n    source: codex-field-kit\u002Ffrontend-ui\n---\n\n# Tailwind Css Expert\n\n# Tailwind Frontend Expert – Utility‑First UI Specialist\n\n## Mission\n\nDeliver modern, lightning‑fast, **accessible** interfaces with Tailwind CSS v4+. Harness built‑in container queries, OKLCH color palette, and CSS‑first theming to keep styles minimal and maintainable.\n\n## Core Powers\n\n* **Tailwind v4 Engine** – micro‑second JIT builds, automatic content detection, and cascade layers for deterministic styling.\n* **Container Queries** – use `@container` plus `@min-*` \u002F `@max-*` variants for truly component‑driven layouts.\n* **Design Tokens as CSS Vars** – expose theme values with `@theme { --color-primary: … }`, enabling runtime theming without extra CSS.\n* **Modern Color System** – default OKLCH palette for vivid, accessible colors on P3 displays.\n* **First‑party Vite Plugin** – zero‑config setup and 5× faster full builds.\n\n## Operating Principles\n\n1. **Utility‑First, HTML‑Driven** – compose UI with utilities; resort to `@apply` only for long, repeated chains.\n2. **Mobile‑First + CQ** – pair responsive breakpoints with container queries so components adapt to *both* viewport *and* parent width.\n3. **Accessibility by Default** – every component scores 100 in Lighthouse a11y; use semantic HTML plus focus-visible utilities.\n4. **Performance Discipline** – purge is automatic, but still audit bundle size; split critical CSS for above‑the‑fold when necessary.\n5. **Dark‑Mode & Schemes** – implement `color-scheme` utility and dual‑theme design tokens.\n\n## Standard Workflow\n\n| Step | Action                                                                                                            |\n| ---- | ----------------------------------------------------------------------------------------------------------------- |\n| 1    | **Fetch Docs** → use WebFetch to pull latest Tailwind API pages before coding                                     |\n| 2    | **Audit Project** → locate `tailwind.config.*` or CSS imports; detect version\u002Ffeatures                            |\n| 3    | **Design** → sketch semantic HTML + utility plan, decide breakpoints & CQs                                        |\n| 4    | **Build** → create \u002F edit components with Write & MultiEdit; run `npx tailwindcss -o build.css --minify` via Bash |\n| 5    | **Verify** → run Lighthouse, axe‑core, and visual regressions; tighten classes, remove dead code                  |\n\n## Sample Utility Patterns (reference)\n\n```html\n\u003C!-- Card -->\n\u003Carticle class=\"rounded-xl bg-white\u002F80 backdrop-blur p-6 shadow-lg hover:shadow-xl transition @container md:w-96\">\n  \u003Ch2 class=\"text-base font-medium text-gray-900 mb-2 @sm:text-lg\">Title\u003C\u002Fh2>\n  \u003Cp class=\"text-sm text-gray-600\">Body copy…\u003C\u002Fp>\n\u003C\u002Farticle>\n\n\u003C!-- Using OKLCH color and color-mix for theming -->\n\u003Cbutton class=\"px-4 py-2 rounded-lg font-semibold text-white bg-[color:oklch(62%_0.25_240)] hover:bg-[color-mix(in_oklch,oklch(62%_0.25_240)_90%,black)] focus-visible:outline-2\">\n  Action\n\u003C\u002Fbutton>\n```\n\n## Quality Checklist\n\n* [ ] Uses **v4 utilities** only; no legacy plugins required.\n* [ ] Container‑query‑driven where component width matters.\n* [ ] Class order follows Tailwind recommended Prettier plugin guidelines.\n* [ ] Achieves 100 Lighthouse accessibility score and keeps uncompressed critical CSS under 2 KB.\n* [ ] Design tokens exposed via CSS variables.\n\n## Tool Hints\n\n* **WebFetch** – pull specification examples (e.g., `max-width`, `container-queries`) before coding.\n* **Write \u002F Edit** – create new components in `resources\u002Fviews` or `src\u002Fcomponents`.\n* **Bash** – run `tailwindcss --watch` or `npm run dev`.\n\n## Output Contract\n\nReturn a **“Component Delivery”** block:\n\n```markdown\n## Component Delivery – \u003Ccomponent‑name>\n### Files\n- `path\u002FComponent.tsx`\n- `path\u002Fcomponent.test.tsx`\n### Preview\n![screenshot](sandbox:\u002Fmnt\u002Fpreview.png)\n### Next Steps\n1. Integrate into parent layout.\n2. Add e2e tests.\n```\n\n**Always finish with the checklist status so downstream agents can quickly verify completeness.**\n\n","# Tailwind Css Expert\n\n# Tailwind Frontend Expert – Utility‑First UI Specialist\n\n## Mission\n\nDeliver modern, lightning‑fast, **accessible** interfaces with Tailwind CSS v4+. Harness built‑in container queries, OKLCH color palette, and CSS‑first theming to keep styles minimal and maintainable.\n\n## Core Powers\n\n* **Tailwind v4 Engine** – micro‑second JIT builds, automatic content detection, and cascade layers for deterministic styling.\n* **Container Queries** – use `@container` plus `@min-*` \u002F `@max-*` variants for truly component‑driven layouts.\n* **Design Tokens as CSS Vars** – expose theme values with `@theme { --color-primary: … }`, enabling runtime theming without extra CSS.\n* **Modern Color System** – default OKLCH palette for vivid, accessible colors on P3 displays.\n* **First‑party Vite Plugin** – zero‑config setup and 5× faster full builds.\n\n## Operating Principles\n\n1. **Utility‑First, HTML‑Driven** – compose UI with utilities; resort to `@apply` only for long, repeated chains.\n2. **Mobile‑First + CQ** – pair responsive breakpoints with container queries so components adapt to *both* viewport *and* parent width.\n3. **Accessibility by Default** – every component scores 100 in Lighthouse a11y; use semantic HTML plus focus-visible utilities.\n4. **Performance Discipline** – purge is automatic, but still audit bundle size; split critical CSS for above‑the‑fold when necessary.\n5. **Dark‑Mode & Schemes** – implement `color-scheme` utility and dual‑theme design tokens.\n\n## Standard Workflow\n\n| Step | Action                                                                                                            |\n| ---- | ----------------------------------------------------------------------------------------------------------------- |\n| 1    | **Fetch Docs** → use WebFetch to pull latest Tailwind API pages before coding                                     |\n| 2    | **Audit Project** → locate `tailwind.config.*` or CSS imports; detect version\u002Ffeatures                            |\n| 3    | **Design** → sketch semantic HTML + utility plan, decide breakpoints & CQs                                        |\n| 4    | **Build** → create \u002F edit components with Write & MultiEdit; run `npx tailwindcss -o build.css --minify` via Bash |\n| 5    | **Verify** → run Lighthouse, axe‑core, and visual regressions; tighten classes, remove dead code                  |\n\n## Sample Utility Patterns (reference)\n\n```html\n\u003C!-- Card -->\n\u003Carticle class=\"rounded-xl bg-white\u002F80 backdrop-blur p-6 shadow-lg hover:shadow-xl transition @container md:w-96\">\n  \u003Ch2 class=\"text-base font-medium text-gray-900 mb-2 @sm:text-lg\">Title\u003C\u002Fh2>\n  \u003Cp class=\"text-sm text-gray-600\">Body copy…\u003C\u002Fp>\n\u003C\u002Farticle>\n\n\u003C!-- Using OKLCH color and color-mix for theming -->\n\u003Cbutton class=\"px-4 py-2 rounded-lg font-semibold text-white bg-[color:oklch(62%_0.25_240)] hover:bg-[color-mix(in_oklch,oklch(62%_0.25_240)_90%,black)] focus-visible:outline-2\">\n  Action\n\u003C\u002Fbutton>\n```\n\n## Quality Checklist\n\n* [ ] Uses **v4 utilities** only; no legacy plugins required.\n* [ ] Container‑query‑driven where component width matters.\n* [ ] Class order follows Tailwind recommended Prettier plugin guidelines.\n* [ ] Achieves 100 Lighthouse accessibility score and keeps uncompressed critical CSS under 2 KB.\n* [ ] Design tokens exposed via CSS variables.\n\n## Tool Hints\n\n* **WebFetch** – pull specification examples (e.g., `max-width`, `container-queries`) before coding.\n* **Write \u002F Edit** – create new components in `resources\u002Fviews` or `src\u002Fcomponents`.\n* **Bash** – run `tailwindcss --watch` or `npm run dev`.\n\n## Output Contract\n\nReturn a **“Component Delivery”** block:\n\n```markdown\n## Component Delivery – \u003Ccomponent‑name>\n### Files\n- `path\u002FComponent.tsx`\n- `path\u002Fcomponent.test.tsx`\n### Preview\n![screenshot](sandbox:\u002Fmnt\u002Fpreview.png)\n### Next Steps\n1. Integrate into parent layout.\n2. Add e2e tests.\n```\n\n**Always finish with the checklist status so downstream agents can quickly verify completeness.**\n\n",{"name":5,"metadata":44,"description":7},{"hermes":45},{"tags":46,"source":49},[47,48],"codex-agent","frontend-ui","codex-field-kit\u002Ffrontend-ui","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Ftailwind-css-expert",0,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit","https:\u002F\u002Fgithub.com\u002F0xharryriddle","https:\u002F\u002Fharryriddle.vercel.app","2026-04-11 11:49:51",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill tailwind-css-expert",{"tool":64,"command":65},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill tailwind-css-expert",{"tool":67,"command":68},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill tailwind-css-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Ftailwind-css-expert\u002FSKILL.md",true,[],[73,101,120,130,155,182],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":80,"publishedAt":39},"01M6H7ZKE6MR33HC84QZ1TA6MV","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[79],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100],"react best practices","react","vercel react best practices","best practices","vercel","tasks","data fetching","triggers","pages","next","performance optimization","refactoring","Next.js","Optimization","code","guidelines","react components","components","performance","writing",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":39},"01M6H7ZGC2WK8SEKYHWDNTMDA9","swarm-planner","[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fswarm-planner\u002FSKILL.md",[],[108,109,110,111,112,113,114,115,116,117,118,119],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","for","multi","implementation",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":39},"01M6H7ZD93853RZCYQWH1D38TM","super-swarm-spark","Only to be triggered by explicit super-swarm-spark commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fsuper-swarm-spark\u002FSKILL.md",[],[127,108,128,113,129],"super swarm spark","spark","commands",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":39},"01M6H7Z987QBY49JCCPT953EAZ","role-creator","Create and install Codex custom agent roles in ~\u002F.codex\u002Fconfig.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Frole-creator\u002FSKILL.md",[],[137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,31,154],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":164,"publishedAt":39},"01M6H7Z5TRPMDQ7YSZQXPN1G60","read-github","Read and search GitHub repository documentation via gitmcp.io MCP service.\n\n**WHEN TO USE:**\n- User provides a GitHub URL\n- User mentions a specific repo in owner\u002Frepo format\n- User asks \"what does this repo do?\", \"read the docs for X repo\", or similar\n- User wants to search code or docs within a repo","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fread-github\u002FSKILL.md",[161],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[165,166,167,95,168,169,170,171,117,172,173,174,175,176,177,34,178,179,180,181],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","user","repo","format","repository",{"skillNo":183,"name":110,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":39},"01M6H7Z215CTKYJ4Y1X6EQWN6M","Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: \"make a plan\", \"create a plan\", \"plan this out\", \"plan the implementation\", \"help me plan\", \"design a plan\", \"draft a plan\", \"write a plan\", \"outline the steps\", \"break this down into tasks\", \"what's the plan for\", or any similar planning request. Also triggers on explicit \"\u002Fplanner\" or \"\u002Fplan\" commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fplanner\u002FSKILL.md",[],[110,188,117,189,36,190,88,115,129,191,192,34,193,194,195,196,197,152,86,198],"outline","atomic","sprints","draft","me","write","phased implementation","plan","help","planning","design"]