[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C1WKR7SCKC59FN5KJA2S18":3,"skill-same:01M7C1WKR7SCKC59FN5KJA2S18":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},"01M7C1WKR7SCKC59FN5KJA2S18","moe-discipline",null,"Use during any implementation task to shape HOW you work — minimal changes, proportional responses, scope containment, and honest gap reporting; fires alongside the task itself rather than at completion time","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-discipline\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: moe-discipline\ndescription: >-\n  Use during any implementation task to shape HOW you work — minimal changes,\n  proportional responses, scope containment, and honest gap reporting; fires\n  alongside the task itself rather than at completion time\n---\n\n# Moe Discipline\n\n## Overview\n\n**Core principle: do exactly what was asked, nothing more, and say what you\ndid not do.**\n\n`verify-completion` fires when you are about to claim the work\nis done. This skill fires while you are doing it. The two are complements:\none shapes the work, the other gates the claim.\n\n## The Seven Rules\n\n1. **Smallest-change bias.** The correct change is the smallest one that\n   solves the stated problem. A refactor is not a fix; a rewrite is not a\n   refactor. If the task says \"fix the null check\", touch the null check.\n\n2. **Edit over create.** Before writing a new file, read what already\n   exists. An edit to an existing file is almost always better than a new\n   file that duplicates, shadows, or contradicts it.\n\n3. **Read before writing.** No file is created or edited without first\n   reading the files it will live beside. No function is added without\n   grepping for one that already does the job.\n\n4. **Match your response to the task.** A one-line fix gets a one-line\n   answer. A rename gets a rename, not a paragraph explaining why naming\n   matters. The length of the reply tracks the complexity of the work, not\n   the importance you assign to it.\n\n5. **Scope stays where it started.** If the task does not mention tests,\n   do not write tests. If it does not mention docs, do not update docs.\n   If you see something unrelated that needs fixing, name it; do not fix\n   it inside this task.\n\n6. **When uncertain, do less.** A change you are unsure about is a change\n   the reviewer has to debug. If you cannot tell whether a line should\n   change, leave it alone and say why you left it.\n\n7. **Name what you did not do.** Every task has edges you chose not to\n   cross. Say which edges and why. A gap you name is an informed decision;\n   a gap you hide is a latent defect.\n\n## Red Flags\n\n| Signal | What is happening |\n|---|---|\n| A diff that touches files the task did not name | Scope has escaped |\n| A new file where an existing one could have been edited | Create-over-edit bias |\n| An answer longer than the change it describes | Proportionality lost |\n| A \"while I was here\" aside that lands as code | Gold-plating |\n| A refactor folded into a bug fix | Two changes in one, neither reviewable |\n| Silence about what was left unchanged | Gap hiding |\n\n## Rationalization Prevention\n\n| Excuse | Reality |\n|---|---|\n| \"It was easy so I just did it\" | Easy changes still carry review cost |\n| \"They will need this eventually\" | Eventually is not now |\n| \"It was already broken\" | A separate finding, not this task |\n| \"The code was right there\" | Proximity is not a mandate |\n| \"I cleaned it up while I was in the file\" | A cleanup is a separate change |\n| \"It is only a few lines\" | Line count does not determine scope |\n| \"The tests needed updating too\" | Only if the task said so |\n","# Moe Discipline\n\n## Overview\n\n**Core principle: do exactly what was asked, nothing more, and say what you\ndid not do.**\n\n`verify-completion` fires when you are about to claim the work\nis done. This skill fires while you are doing it. The two are complements:\none shapes the work, the other gates the claim.\n\n## The Seven Rules\n\n1. **Smallest-change bias.** The correct change is the smallest one that\n   solves the stated problem. A refactor is not a fix; a rewrite is not a\n   refactor. If the task says \"fix the null check\", touch the null check.\n\n2. **Edit over create.** Before writing a new file, read what already\n   exists. An edit to an existing file is almost always better than a new\n   file that duplicates, shadows, or contradicts it.\n\n3. **Read before writing.** No file is created or edited without first\n   reading the files it will live beside. No function is added without\n   grepping for one that already does the job.\n\n4. **Match your response to the task.** A one-line fix gets a one-line\n   answer. A rename gets a rename, not a paragraph explaining why naming\n   matters. The length of the reply tracks the complexity of the work, not\n   the importance you assign to it.\n\n5. **Scope stays where it started.** If the task does not mention tests,\n   do not write tests. If it does not mention docs, do not update docs.\n   If you see something unrelated that needs fixing, name it; do not fix\n   it inside this task.\n\n6. **When uncertain, do less.** A change you are unsure about is a change\n   the reviewer has to debug. If you cannot tell whether a line should\n   change, leave it alone and say why you left it.\n\n7. **Name what you did not do.** Every task has edges you chose not to\n   cross. Say which edges and why. A gap you name is an informed decision;\n   a gap you hide is a latent defect.\n\n## Red Flags\n\n| Signal | What is happening |\n|---|---|\n| A diff that touches files the task did not name | Scope has escaped |\n| A new file where an existing one could have been edited | Create-over-edit bias |\n| An answer longer than the change it describes | Proportionality lost |\n| A \"while I was here\" aside that lands as code | Gold-plating |\n| A refactor folded into a bug fix | Two changes in one, neither reviewable |\n| Silence about what was left unchanged | Gap hiding |\n\n## Rationalization Prevention\n\n| Excuse | Reality |\n|---|---|\n| \"It was easy so I just did it\" | Easy changes still carry review cost |\n| \"They will need this eventually\" | Eventually is not now |\n| \"It was already broken\" | A separate finding, not this task |\n| \"The code was right there\" | Proximity is not a mandate |\n| \"I cleaned it up while I was in the file\" | A cleanup is a separate change |\n| \"It is only a few lines\" | Line count does not determine scope |\n| \"The tests needed updating too\" | Only if the task said so |\n",{"name":5,"description":7},"main","728894f3f85fbd4e788f015ddfd72bb6155d5dd5","plugins\u002Fmoe\u002Fskills\u002Fmoe-discipline",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-discipline",{"tool":36,"command":37},"bunx","bunx skills add zak-keown\u002Fmoe --skill moe-discipline",{"tool":39,"command":40},"pnpm","pnpm dlx skills add zak-keown\u002Fmoe --skill moe-discipline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fmoe-discipline\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",[],[]]