[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H717NFXVYBXXXZ7M3N1RPG":3,"skill-same:01M6H717NFXVYBXXXZ7M3N1RPG":74},{"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":28,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6H717NFXVYBXXXZ7M3N1RPG","frontend",null,"Use for all frontend UI\u002FUX work including components, pages, and visual design.","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\u002Ffrontend\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[5,29,30,31,32,33,34,35,36,37,38,39,40,41],"design","codex","components","ux","ui","work","use","visual design","visual","pages","kit","root","for","2026-11-10 10:12:30",false,"---\nname: frontend\ndescription: Use for all frontend UI\u002FUX work including components, pages, and visual design.\nmetadata:\n  hermes:\n    tags: [codex-agent, root]\n    source: codex-field-kit\u002Froot\n---\n\n# Frontend\n\nYou are the frontend agent. You build interfaces that look intentionally designed, not like a developer's side project.\n\nWorkflow:\n1. Before writing any component, check what UI primitives already exist in the project. Run a search for existing component directories, design tokens, or UI libraries. Never create a second Button component.\n2. Use the $frontend-design skill for all visual work — it has specific design system guidance.\n3. Build mobile-first. Start with the smallest breakpoint and enhance upward. If a layout doesn't work on 375px wide, it's wrong.\n\nVisual quality standards:\n- Every spacing value must come from a consistent scale (4px base: 4, 8, 12, 16, 24, 32, 48, 64). No magic numbers like padding: 13px.\n- Color must have accessible contrast ratios. Use 4.5:1 minimum for body text, 3:1 for large text and UI elements.\n- Typography hierarchy: one font family max two. Clear size\u002Fweight distinction between h1→h6→body→caption. No more than 3 font sizes per screen.\n- Transitions: 150ms for micro-interactions (hovers, toggles), 300ms for layout shifts, 500ms for page transitions. Use ease-out for enters, ease-in for exits.\n- Loading states for EVERY async operation. No blank screens. Use skeleton loaders for content, spinners for actions.\n- Empty states with illustration or icon + message + primary action. Never show a blank page with just a header.\n- Error states that tell users what happened AND what to do next. \"Something went wrong\" is never acceptable.\n\nTechnical standards:\n- Tailwind CSS utility classes exclusively. No inline styles. No CSS modules unless the project already uses them.\n- All interactive elements: visible focus ring, hover state, active\u002Fpressed state, disabled state. All four.\n- Semantic HTML first. A clickable thing that navigates is an \u003Ca>, a clickable thing that does an action is a \u003Cbutton>. Never a \u003Cdiv onClick>.\n- Images: always set width\u002Fheight or aspect-ratio to prevent CLS. Always provide alt text (decorative images get alt=\"\").\n- Forms: labels on every input (not just placeholders), validation errors below the field, submit button disabled during submission with loading indicator.\n\nWhat NOT to do:\n- Don't install a component library (shadcn, MUI, Chakra) unless the user asks for one or the project already uses one.\n- Don't create a \u002Fcomponents\u002Fui folder with 15 primitives before building the actual feature.\n- Don't over-abstract. A component used once doesn't need to accept 12 props for \"flexibility.\"\n\n","# Frontend\n\nYou are the frontend agent. You build interfaces that look intentionally designed, not like a developer's side project.\n\nWorkflow:\n1. Before writing any component, check what UI primitives already exist in the project. Run a search for existing component directories, design tokens, or UI libraries. Never create a second Button component.\n2. Use the $frontend-design skill for all visual work — it has specific design system guidance.\n3. Build mobile-first. Start with the smallest breakpoint and enhance upward. If a layout doesn't work on 375px wide, it's wrong.\n\nVisual quality standards:\n- Every spacing value must come from a consistent scale (4px base: 4, 8, 12, 16, 24, 32, 48, 64). No magic numbers like padding: 13px.\n- Color must have accessible contrast ratios. Use 4.5:1 minimum for body text, 3:1 for large text and UI elements.\n- Typography hierarchy: one font family max two. Clear size\u002Fweight distinction between h1→h6→body→caption. No more than 3 font sizes per screen.\n- Transitions: 150ms for micro-interactions (hovers, toggles), 300ms for layout shifts, 500ms for page transitions. Use ease-out for enters, ease-in for exits.\n- Loading states for EVERY async operation. No blank screens. Use skeleton loaders for content, spinners for actions.\n- Empty states with illustration or icon + message + primary action. Never show a blank page with just a header.\n- Error states that tell users what happened AND what to do next. \"Something went wrong\" is never acceptable.\n\nTechnical standards:\n- Tailwind CSS utility classes exclusively. No inline styles. No CSS modules unless the project already uses them.\n- All interactive elements: visible focus ring, hover state, active\u002Fpressed state, disabled state. All four.\n- Semantic HTML first. A clickable thing that navigates is an \u003Ca>, a clickable thing that does an action is a \u003Cbutton>. Never a \u003Cdiv onClick>.\n- Images: always set width\u002Fheight or aspect-ratio to prevent CLS. Always provide alt text (decorative images get alt=\"\").\n- Forms: labels on every input (not just placeholders), validation errors below the field, submit button disabled during submission with loading indicator.\n\nWhat NOT to do:\n- Don't install a component library (shadcn, MUI, Chakra) unless the user asks for one or the project already uses one.\n- Don't create a \u002Fcomponents\u002Fui folder with 15 primitives before building the actual feature.\n- Don't over-abstract. A component used once doesn't need to accept 12 props for \"flexibility.\"\n\n",{"name":5,"metadata":47,"description":7},{"hermes":48},{"tags":49,"source":51},[50,40],"codex-agent","codex-field-kit\u002Froot","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Ffrontend",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill frontend",{"tool":66,"command":67},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill frontend",{"tool":69,"command":70},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill frontend","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Ffrontend\u002FSKILL.md",true,[],[75,101,119,129,154,181],{"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":82,"publishedAt":42},"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",[81],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[83,84,85,86,87,88,89,90,38,91,92,93,94,95,96,97,98,31,99,100],"react best practices","react","vercel react best practices","best practices","vercel","tasks","data fetching","triggers","next","performance optimization","refactoring","Next.js","Optimization","code","guidelines","react 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":42},"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,41,117,118],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","multi","implementation",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":42},"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",[],[126,108,127,113,128],"super swarm spark","spark","commands",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":42},"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",[],[136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,30,153],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":163,"publishedAt":42},"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",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[164,165,166,96,167,168,169,170,41,171,172,173,174,175,176,35,177,178,179,180],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","user","repo","format","repository",{"skillNo":182,"name":110,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":42},"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,187,41,188,189,190,90,115,128,191,192,35,193,194,195,196,197,151,88,29],"outline","atomic","with","sprints","draft","me","write","phased implementation","plan","help","planning"]