[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C1WH7890BE2P2CY2HPSAFA":3,"skill-same:01M7C1WH7890BE2P2CY2HPSAFA":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7C1WH7890BE2P2CY2HPSAFA","moe-dev",null,"Use when planning, implementing, or reviewing any feature or change to the Moe project itself — enforces integration-completeness and multi-harness awareness as non-negotiable development constraints","zak-keown\u002Fmoe","zak-keown","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F320717241?v=4","01M7BZFXME0NW6TQX0H7AZM2KS","01M7BZFXN32VR0JN5AATRD53H4",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fmoe-dev\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: moe-dev\ndescription: >-\n  Use when planning, implementing, or reviewing any feature or change to the\n  Moe project itself — enforces integration-completeness and multi-harness\n  awareness as non-negotiable development constraints\n---\n\n# Developing for Moe\n\nTwo tenets govern every piece of work on this project. They are not\nguidelines — they are acceptance criteria. Work that violates either is\nincomplete.\n\n## Tenet 1 — Integration is part of the feature\n\nA feature is not done if it is not integrated with the project.\n\n**Every plan must include integration steps.** A plan that ends at \"the code\nworks in isolation\" is a partial plan. Integration means:\n\n- The feature is reachable from an existing entry point (a hook, a skill\n  trigger, a CLI command, a consumer import).\n- Registration is updated: the skill registry for skills, `hooks.json` for\n  hooks, `package.json` exports for library code, mint yaml for plugin\n  surfaces.\n- Tests that guard the registration surface pass (`pnpm check`).\n- If the feature ships in a plugin, `pnpm mint` produces the correct output\n  and `pnpm mint:check` is clean.\n\nA branch that adds a file but does not wire it into the project has not\ndelivered a feature. It has delivered a file.\n\n## Tenet 2 — Multi-harness by default\n\nNo matter which harness you are running under, you are developing a project\nthat ships to eight harnesses: claude-code, codex, cursor, kimi, opencode,\npi, agent-plugins-1.0, and copilot.\n\n**Planning, exploration, and research must account for this at all times.**\n\n- A design that relies on a harness-specific capability (Claude Code's\n  `CLAUDE_PLUGIN_ROOT`, Cursor's `CURSOR_PLUGIN_ROOT`, Codex's agent\n  dispatch) must document the equivalent path for the others, or explain why\n  the feature is harness-scoped.\n- Hook output must use the harness-aware JSON envelope (see existing hooks\n  for the pattern: Claude Code's `hookSpecificOutput`, Cursor's\n  `additional_context`, the generic fallback).\n- Mint yaml is the packaging surface. A feature that works only because you\n  are running from a git clone and can see `.\u002Fpackages\u002F` is not portable.\n- When evaluating an approach, ask: \"does this work for the seven harnesses\n  I am not running under right now?\" If the answer is no, redesign before\n  building.\n\n## Applying the tenets\n\nWhen you write a plan, include a section called **Integration** that lists\nevery registration, wiring, and cross-harness consideration the feature\nrequires. When you review a plan, check for that section first.\n\nWhen you implement, treat the integration steps as blocking — not follow-up\nwork. The branch is not ready for review until integration is done and\n`pnpm check` and `pnpm mint:check` pass.\n\nWhen you review code, check that the feature is reachable from outside its\nown file, and that harness-specific assumptions are either absent or\nexplicitly scoped.\n","# Developing for Moe\n\nTwo tenets govern every piece of work on this project. They are not\nguidelines — they are acceptance criteria. Work that violates either is\nincomplete.\n\n## Tenet 1 — Integration is part of the feature\n\nA feature is not done if it is not integrated with the project.\n\n**Every plan must include integration steps.** A plan that ends at \"the code\nworks in isolation\" is a partial plan. Integration means:\n\n- The feature is reachable from an existing entry point (a hook, a skill\n  trigger, a CLI command, a consumer import).\n- Registration is updated: the skill registry for skills, `hooks.json` for\n  hooks, `package.json` exports for library code, mint yaml for plugin\n  surfaces.\n- Tests that guard the registration surface pass (`pnpm check`).\n- If the feature ships in a plugin, `pnpm mint` produces the correct output\n  and `pnpm mint:check` is clean.\n\nA branch that adds a file but does not wire it into the project has not\ndelivered a feature. It has delivered a file.\n\n## Tenet 2 — Multi-harness by default\n\nNo matter which harness you are running under, you are developing a project\nthat ships to eight harnesses: claude-code, codex, cursor, kimi, opencode,\npi, agent-plugins-1.0, and copilot.\n\n**Planning, exploration, and research must account for this at all times.**\n\n- A design that relies on a harness-specific capability (Claude Code's\n  `CLAUDE_PLUGIN_ROOT`, Cursor's `CURSOR_PLUGIN_ROOT`, Codex's agent\n  dispatch) must document the equivalent path for the others, or explain why\n  the feature is harness-scoped.\n- Hook output must use the harness-aware JSON envelope (see existing hooks\n  for the pattern: Claude Code's `hookSpecificOutput`, Cursor's\n  `additional_context`, the generic fallback).\n- Mint yaml is the packaging surface. A feature that works only because you\n  are running from a git clone and can see `.\u002Fpackages\u002F` is not portable.\n- When evaluating an approach, ask: \"does this work for the seven harnesses\n  I am not running under right now?\" If the answer is no, redesign before\n  building.\n\n## Applying the tenets\n\nWhen you write a plan, include a section called **Integration** that lists\nevery registration, wiring, and cross-harness consideration the feature\nrequires. When you review a plan, check for that section first.\n\nWhen you implement, treat the integration steps as blocking — not follow-up\nwork. The branch is not ready for review until integration is done and\n`pnpm check` and `pnpm mint:check` pass.\n\nWhen you review code, check that the feature is reachable from outside its\nown file, and that harness-specific assumptions are either absent or\nexplicitly scoped.\n",{"name":5,"description":7},"main","728894f3f85fbd4e788f015ddfd72bb6155d5dd5","plugins\u002Fmoe\u002Fskills\u002Fmoe-dev",1,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe","https:\u002F\u002Fgithub.com\u002Fzak-keown","2026-09-05 06:29:06",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add zak-keown\u002Fmoe --skill moe-dev",{"tool":36,"command":37},"bunx","bunx skills add zak-keown\u002Fmoe --skill moe-dev",{"tool":39,"command":40},"pnpm","pnpm dlx skills add zak-keown\u002Fmoe --skill moe-dev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fmoe-dev\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7C1Z5362Y8NVRZ69HWP0ZD0","write-skill","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-skill\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7C1YZ9966WK9R6ZRPCGWF3G","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7C1YMR4SJD7BPBBPXZCVGVH","write-clearly","Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-clearly\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7C1YH9805YSM0N20VQAVSXF","windows-vm","Create, manage, or connect to a headless Windows 11 VM running in Docker with SSH access. Use when the user wants to spin up, stop, restart, or SSH into a Windows VM.","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwindows-vm\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7C1YD87SCNEJ2C9B8HFR2NQ","verify-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating MRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fverify-completion\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7C1YARDEHT0TJ9BRG30ZCF4","using-moe","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fusing-moe\u002FSKILL.md",[],[]]