[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BHX8WERKPYPY38CM9S5KFC":3,"skill-same:01M7BHX8WERKPYPY38CM9S5KFC":46},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7BHX8WERKPYPY38CM9S5KFC","principle-laziness-protocol",null,"Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.","gannonh\u002Fcodex-plugins","gannonh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1012888?v=4","01M725CQ84YM7074SNHKWKZ323","Gannon Hall","01M7BHVA7G558FKQNQ9449DTJE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fgannonh\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fpstack-codex\u002Fskills\u002Fprinciple-laziness-protocol\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: principle-laziness-protocol\ndescription: \"Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.\"\nuser-invocable: false\n---\n\n# Laziness Protocol\n\nWriting code is cheap for you, which makes over-engineering easy. Counter it by borrowing a human maintainer's fatigue. Aim for the most result with the least code and complexity.\n\n- **Prefer deletion.** When asked to refactor or improve, look for removals before additions.\n- **Maintain a flat call hierarchy.** Avoid deep call chains. A rich interface that hides substantial work is not a deep call chain. If answering a question requires tracing through more than 3 files or layers, flatten it.\n- **Consolidate decisions.** Do not repeat the same choice in several places. Put it behind one source of truth and pass the result as a simple flag.\n- **Minimize the diff.** Make the smallest change that solves the problem. Fewer lines beat \"elegant\" boilerplate.\n- **Question the threading.** If a task asks you to pass a new signal through types, schemas, pipelines, or similar layers, stop and look for a more direct path.\n- **Sweat the small leaks.** Remove tiny pass-throughs, representation leaks, and duplicated choices before they spread. Small leaks compound into permanent coordination costs.\n\n**Prime directive:** If a human developer would find the code exhausting to maintain, it is a bad solution. Be lazy. Stay simple.\n","# Laziness Protocol\n\nWriting code is cheap for you, which makes over-engineering easy. Counter it by borrowing a human maintainer's fatigue. Aim for the most result with the least code and complexity.\n\n- **Prefer deletion.** When asked to refactor or improve, look for removals before additions.\n- **Maintain a flat call hierarchy.** Avoid deep call chains. A rich interface that hides substantial work is not a deep call chain. If answering a question requires tracing through more than 3 files or layers, flatten it.\n- **Consolidate decisions.** Do not repeat the same choice in several places. Put it behind one source of truth and pass the result as a simple flag.\n- **Minimize the diff.** Make the smallest change that solves the problem. Fewer lines beat \"elegant\" boilerplate.\n- **Question the threading.** If a task asks you to pass a new signal through types, schemas, pipelines, or similar layers, stop and look for a more direct path.\n- **Sweat the small leaks.** Remove tiny pass-throughs, representation leaks, and duplicated choices before they spread. Small leaks compound into permanent coordination costs.\n\n**Prime directive:** If a human developer would find the code exhausting to maintain, it is a bad solution. Be lazy. Stay simple.\n",{"name":5,"description":7,"user-invocable":20},"main","1466ce6355abd331a82e9d9effd66d42bacb5978","pstack-codex\u002Fskills\u002Fprinciple-laziness-protocol","https:\u002F\u002Fgithub.com\u002Fgannonh\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002Fgannonh","gannonhall.com","product \u002F dev; ex-google","2026-08-28 03:55:17",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add gannonh\u002Fcodex-plugins --skill principle-laziness-protocol",{"tool":38,"command":39},"bunx","bunx skills add gannonh\u002Fcodex-plugins --skill principle-laziness-protocol",{"tool":41,"command":42},"pnpm","pnpm dlx skills add gannonh\u002Fcodex-plugins --skill principle-laziness-protocol","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgannonh\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fpstack-codex\u002Fskills\u002Fprinciple-laziness-protocol\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7BHZ35XF855R2QY1XDW7WKV","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fgannonh\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fpstack-codex\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7BHZ1JDZTKC9QNVDW8KV8K7","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002Fgannonh\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fpstack-codex\u002Fskills\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7BHZ00R1YG2BA0XHQ2ZW4EB","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Fgannonh\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fpstack-codex\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7BHYYKRMCFKQ8C08X1ZPRSZ","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fgannonh\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fpstack-codex\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"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":81,"publishedAt":19},"01M7BHYVM5D5C815M36BF1P13R","thermo-nuclear-code-quality-review","Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.","https:\u002F\u002Fgithub.com\u002Fgannonh\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fpstack-codex\u002Fskills\u002Fthermo-nuclear-code-quality-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7BHYQTEFR4H9882BM1FA4Y1","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Ftechnical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Fgannonh\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fpstack-codex\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[]]