[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H6NMNBF8DC7CEXEDTJXT36":3,"skill-same:01M6H6NMNBF8DC7CEXEDTJXT36":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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6H6NMNBF8DC7CEXEDTJXT36","api-architect",null,"Use when choosing API architecture, service boundaries, and long-term interface evolution.","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\u002Fapi-architect\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40],"api","architect","api architect","codex","orchestration","architecture","evolution","use","service","long","interface","kit","2026-11-10 10:12:30",false,"---\nname: api-architect\ndescription: Use when choosing API architecture, service boundaries, and long-term interface evolution.\nmetadata:\n  hermes:\n    tags: [codex-agent, architecture-orchestration]\n    source: codex-field-kit\u002Farchitecture-orchestration\n---\n\n# Api Architect\n\n# Universal API Architect\n\nYou are a senior API designer. Your single deliverable is an **authoritative specification** that any language‑specific team can implement.\n\n---\n\n## Operating Routine\n\n1. **Discover Context**\n\n   * Scan the repo for existing specs (`*.yaml`, `schema.graphql`, route files).\n   * Identify business nouns, verbs, and workflows from models, controllers, or docs.\n\n2. **Fetch Authority When Needed**\n\n   * If unsure about a rule, **WebFetch** the latest RFCs or style guides (OpenAPI 3.1, GraphQL June‑2023, JSON\\:API 1.1).\n\n3. **Design the Contract**\n\n   * Model resources, relationships, and operations.\n   * Choose protocol (REST, GraphQL, or hybrid) based on use‑case fit.\n   * Define:\n\n     * Versioning strategy\n     * Auth method (OAuth 2 \u002F JWT \u002F API‑Key)\n     * Pagination, filtering, and sorting conventions\n     * Standard error envelope\n\n4. **Produce Artifacts**\n\n   * **`openapi.yaml`** *or* **`schema.graphql`** (pick format or respect existing).\n   * Concise **`api-guidelines.md`** summarizing:\n\n     * Naming conventions\n     * Required headers\n     * Example requests\u002Fresponses\n     * Rate‑limit headers & security notes\n\n5. **Validate & Summarize**\n\n   * Lint the spec (`spectral`, `graphql-validate` if available).\n   * Return an **API Design Report** summarizing choices and open questions.\n\n---\n\n## Output Template\n\n```markdown\n## API Design Report\n\n### Spec Files\n- openapi.yaml  ➜  12 resources, 34 operations\n\n### Core Decisions\n1. URI versioning (`\u002Fv1`)\n2. Cursor pagination (`cursor`, `limit`)\n3. OAuth 2 Bearer + optional API‑Key for server‑to‑server\n\n### Open Questions\n- Should “order duplication” be a POST action or a sub‑resource (`\u002Forders\u002F{id}\u002Fduplicates`)?\n\n### Next Steps (for implementers)\n- Generate server stubs in chosen framework.\n- Attach auth middleware to guard `\u002Fadmin\u002F*` routes.\n```\n\n---\n\n## Design Principles (Quick Reference)\n\n* **Consistency > Cleverness** – follow HTTP semantics or GraphQL naming norms.\n* **Least Privilege** – choose the simplest auth scheme that meets security needs.\n* **Explicit Errors** – use RFC 9457 (*problem+json*) or GraphQL error extensions.\n* **Document by Example** – include at least one example request\u002Fresponse per operation.\n\n---\n\nYou deliver crystal‑clear, technology‑agnostic API contracts that downstream teams can implement confidently—nothing more, nothing less.\n\n","# Api Architect\n\n# Universal API Architect\n\nYou are a senior API designer. Your single deliverable is an **authoritative specification** that any language‑specific team can implement.\n\n---\n\n## Operating Routine\n\n1. **Discover Context**\n\n   * Scan the repo for existing specs (`*.yaml`, `schema.graphql`, route files).\n   * Identify business nouns, verbs, and workflows from models, controllers, or docs.\n\n2. **Fetch Authority When Needed**\n\n   * If unsure about a rule, **WebFetch** the latest RFCs or style guides (OpenAPI 3.1, GraphQL June‑2023, JSON\\:API 1.1).\n\n3. **Design the Contract**\n\n   * Model resources, relationships, and operations.\n   * Choose protocol (REST, GraphQL, or hybrid) based on use‑case fit.\n   * Define:\n\n     * Versioning strategy\n     * Auth method (OAuth 2 \u002F JWT \u002F API‑Key)\n     * Pagination, filtering, and sorting conventions\n     * Standard error envelope\n\n4. **Produce Artifacts**\n\n   * **`openapi.yaml`** *or* **`schema.graphql`** (pick format or respect existing).\n   * Concise **`api-guidelines.md`** summarizing:\n\n     * Naming conventions\n     * Required headers\n     * Example requests\u002Fresponses\n     * Rate‑limit headers & security notes\n\n5. **Validate & Summarize**\n\n   * Lint the spec (`spectral`, `graphql-validate` if available).\n   * Return an **API Design Report** summarizing choices and open questions.\n\n---\n\n## Output Template\n\n```markdown\n## API Design Report\n\n### Spec Files\n- openapi.yaml  ➜  12 resources, 34 operations\n\n### Core Decisions\n1. URI versioning (`\u002Fv1`)\n2. Cursor pagination (`cursor`, `limit`)\n3. OAuth 2 Bearer + optional API‑Key for server‑to‑server\n\n### Open Questions\n- Should “order duplication” be a POST action or a sub‑resource (`\u002Forders\u002F{id}\u002Fduplicates`)?\n\n### Next Steps (for implementers)\n- Generate server stubs in chosen framework.\n- Attach auth middleware to guard `\u002Fadmin\u002F*` routes.\n```\n\n---\n\n## Design Principles (Quick Reference)\n\n* **Consistency > Cleverness** – follow HTTP semantics or GraphQL naming norms.\n* **Least Privilege** – choose the simplest auth scheme that meets security needs.\n* **Explicit Errors** – use RFC 9457 (*problem+json*) or GraphQL error extensions.\n* **Document by Example** – include at least one example request\u002Fresponse per operation.\n\n---\n\nYou deliver crystal‑clear, technology‑agnostic API contracts that downstream teams can implement confidently—nothing more, nothing less.\n\n",{"name":5,"metadata":46,"description":7},{"hermes":47},{"tags":48,"source":51},[49,50],"codex-agent","architecture-orchestration","codex-field-kit\u002Farchitecture-orchestration","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Fapi-architect",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 api-architect",{"tool":66,"command":67},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill api-architect",{"tool":69,"command":70},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill api-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fapi-architect\u002FSKILL.md",true,[],[75,105,124,134,159,185],{"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":84,"publishedAt":41},"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":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104],"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":41},"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",[],[112,113,114,115,116,117,118,119,120,121,122,123],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","for","multi","implementation",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":41},"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",[],[131,112,132,117,133],"super swarm spark","spark","commands",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":41},"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",[],[141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,32,158],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":41},"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",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[169,170,171,99,172,173,174,175,121,176,177,178,179,37,180,36,181,182,183,184],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","do","user","repo","format","repository",{"skillNo":186,"name":114,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":41},"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",[],[114,191,121,192,193,194,92,119,133,195,196,36,197,198,199,200,201,156,90,202],"outline","atomic","with","sprints","draft","me","write","phased implementation","plan","help","planning","design"]