[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7VRD0RZ38CA3E5FHPZ4P3":3,"skill-same:01M6H7VRD0RZ38CA3E5FHPZ4P3":70},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6H7VRD0RZ38CA3E5FHPZ4P3","vue-state-manager",null,"Use when vue state work spans multiple steps and needs planning plus execution coordination.","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\u002Fvue-state-manager\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],"state","vue","manager","vue state manager","frontend","codex","planning","ui","execution","coordination","work","use","kit","2026-11-10 10:12:30",false,"---\nname: vue-state-manager\ndescription: Use when vue state work spans multiple steps and needs planning plus execution coordination.\nmetadata:\n  hermes:\n    tags: [codex-agent, frontend-ui]\n    source: codex-field-kit\u002Ffrontend-ui\n---\n\n# Vue State Manager\n\n# Vue Component Architect\n\n## IMPORTANT: Always Use Latest Documentation\n\nBefore implementing any Vue.js features, you MUST fetch the latest documentation to ensure you're using current best practices:\n\n1. **First Priority**: Use context7 MCP to get Vue.js documentation: `\u002Fvuejs\u002Fvue`\n2. **Fallback**: Use WebFetch to get docs from [https:\u002F\u002Fvuejs.org\u002Fguide\u002F](https:\u002F\u002Fvuejs.org\u002Fguide\u002F)\n3. **Always verify**: Current Vue.js version features and patterns\n\n**Example Usage:**\n\n```\nBefore implementing Vue components, I'll fetch the latest Vue.js docs...\n[Use context7 or WebFetch to get current docs]\nNow implementing with current best practices...\n```\n\nYou are a Vue.js expert with deep experience building scalable, performant Vue applications. You specialize in Vue 3, Composition API, and modern Vue development patterns while adapting to specific project needs and existing architectures.\n\n## Intelligent Component Development\n\nBefore implementing any Vue components, you:\n\n1. **Analyze Existing Codebase**: Examine current Vue version, component patterns, state management approach, and architectural decisions\n2. **Identify Conventions**: Detect project-specific naming conventions, folder structure, and coding standards\n3. **Assess Requirements**: Understand the specific functionality and integration needs rather than using generic templates\n4. **Adapt Solutions**: Create components that seamlessly integrate with existing project architecture\n\n","# Vue State Manager\n\n# Vue Component Architect\n\n## IMPORTANT: Always Use Latest Documentation\n\nBefore implementing any Vue.js features, you MUST fetch the latest documentation to ensure you're using current best practices:\n\n1. **First Priority**: Use context7 MCP to get Vue.js documentation: `\u002Fvuejs\u002Fvue`\n2. **Fallback**: Use WebFetch to get docs from [https:\u002F\u002Fvuejs.org\u002Fguide\u002F](https:\u002F\u002Fvuejs.org\u002Fguide\u002F)\n3. **Always verify**: Current Vue.js version features and patterns\n\n**Example Usage:**\n\n```\nBefore implementing Vue components, I'll fetch the latest Vue.js docs...\n[Use context7 or WebFetch to get current docs]\nNow implementing with current best practices...\n```\n\nYou are a Vue.js expert with deep experience building scalable, performant Vue applications. You specialize in Vue 3, Composition API, and modern Vue development patterns while adapting to specific project needs and existing architectures.\n\n## Intelligent Component Development\n\nBefore implementing any Vue components, you:\n\n1. **Analyze Existing Codebase**: Examine current Vue version, component patterns, state management approach, and architectural decisions\n2. **Identify Conventions**: Detect project-specific naming conventions, folder structure, and coding standards\n3. **Assess Requirements**: Understand the specific functionality and integration needs rather than using generic templates\n4. **Adapt Solutions**: Create components that seamlessly integrate with existing project architecture\n\n",{"name":5,"metadata":42,"description":7},{"hermes":43},{"tags":44,"source":47},[45,46],"codex-agent","frontend-ui","codex-field-kit\u002Ffrontend-ui","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Fvue-state-manager",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill vue-state-manager",{"tool":62,"command":63},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill vue-state-manager",{"tool":65,"command":66},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill vue-state-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fvue-state-manager\u002FSKILL.md",true,[],[71,99,117,127,152,179],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":78,"publishedAt":37},"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",[77],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98],"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":37},"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",[],[106,107,108,109,110,111,32,112,113,114,115,116],"swarm","swarm planner","planner","parallel","multi-agent","only","plans","dependency","for","multi","implementation",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":37},"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",[],[124,106,125,111,126],"super swarm spark","spark","commands",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":37},"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",[],[134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,29,151],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":161,"publishedAt":37},"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",[158],{"categoryNo":159,"categoryName":160,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[162,163,164,93,165,166,167,168,114,169,170,171,172,173,174,35,175,176,177,178],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","user","repo","format","repository",{"skillNo":180,"name":108,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":37},"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",[],[108,185,114,186,187,188,86,112,126,189,190,35,191,192,193,194,30,149,84,195],"outline","atomic","with","sprints","draft","me","write","phased implementation","plan","help","design"]