[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AVPNAY168FRVX1MMP6AMWE":3,"skill-same:01M7AVPNAY168FRVX1MMP6AMWE":45},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":44},"01M7AVPNAY168FRVX1MMP6AMWE","principle-build-the-lever",null,"Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.","onhazrat\u002Fpstack-claude-code","onhazrat","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F31163775?v=4","01M7AVMH4F1PQE1MT9BETMJVYJ","Hossein Hazrati","01M7AVMH529TXWSSQC18JDFKD7",0,"MIT","https:\u002F\u002Fgithub.com\u002Fonhazrat\u002Fpstack-claude-code\u002Fblob\u002Fmain\u002Fpstack-claude-code\u002Fskills\u002Fprinciple-build-the-lever\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: principle-build-the-lever\ndescription: \"Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.\"\ndisable-model-invocation: true\n---\n# Build the Lever\n\nWhen the work isn't trivial, build the tool that does it instead of doing it by hand.\n\n**Why:** Two payoffs. Throughput: a codemod, generator, or script does the work the same way every time and reruns for free. Confidence: the tool is one artifact a reviewer can read and rerun to check the work. Hand-done changes can only be re-verified by redoing them. A deterministic script turns \"trust me\" into \"run this\".\n\n**Pattern:** Default to building the lever. Skip it only when the task is genuinely trivial, a couple of obvious edits you can see at a glance.\n\n- Do the first unit by hand to learn the recipe, then build the tool. Prove it by rerunning it on that unit and diffing against your hand-done version. Make the lever safe to rerun. A reviewer will.\n- Codemod or script for edits, generator for repetitive files, a dump-to-sqlite query for analysis, a rerunnable check for verification.\n- A deterministic lever beats fan-out. If the tool can process every unit in one pass, run it yourself; don't fan out delegates to hand-apply what a script can do.\n- When you fan work out to subagents, write the lever as a skill they all read: the recipe, the verification contract, and the do-not-touch fences in one artifact, so every delegate inherits the same hardened version instead of re-explaining it per prompt and watching each one drift. Keep it outside the delegates' write scope so they can't quietly edit the contract.\n- Applying this principle produces a file. If you cited it and there is no codemod, script, generator, or delegate skill in the diff, you didn't apply it.\n- Commit the lever when the work outlives the session, so the next run reruns it instead of redoing it.\n\n**Balance:** The bar is triviality, not repetition. A one-off still earns a lever when the lever is what makes the work checkable. Per the [Laziness Protocol](..\u002Fprinciple-laziness-protocol\u002FSKILL.md), build the smallest script that does or proves the job, never a framework.\n\nDistinct from [Encode Lessons in Structure](..\u002Fprinciple-encode-lessons-in-structure\u002FSKILL.md), which makes a recurring instruction a durable guardrail. This is throughput and reviewability on the work in front of you. For scripting the verification itself, see [Prove It Works](..\u002Fprinciple-prove-it-works\u002FSKILL.md).\n","# Build the Lever\n\nWhen the work isn't trivial, build the tool that does it instead of doing it by hand.\n\n**Why:** Two payoffs. Throughput: a codemod, generator, or script does the work the same way every time and reruns for free. Confidence: the tool is one artifact a reviewer can read and rerun to check the work. Hand-done changes can only be re-verified by redoing them. A deterministic script turns \"trust me\" into \"run this\".\n\n**Pattern:** Default to building the lever. Skip it only when the task is genuinely trivial, a couple of obvious edits you can see at a glance.\n\n- Do the first unit by hand to learn the recipe, then build the tool. Prove it by rerunning it on that unit and diffing against your hand-done version. Make the lever safe to rerun. A reviewer will.\n- Codemod or script for edits, generator for repetitive files, a dump-to-sqlite query for analysis, a rerunnable check for verification.\n- A deterministic lever beats fan-out. If the tool can process every unit in one pass, run it yourself; don't fan out delegates to hand-apply what a script can do.\n- When you fan work out to subagents, write the lever as a skill they all read: the recipe, the verification contract, and the do-not-touch fences in one artifact, so every delegate inherits the same hardened version instead of re-explaining it per prompt and watching each one drift. Keep it outside the delegates' write scope so they can't quietly edit the contract.\n- Applying this principle produces a file. If you cited it and there is no codemod, script, generator, or delegate skill in the diff, you didn't apply it.\n- Commit the lever when the work outlives the session, so the next run reruns it instead of redoing it.\n\n**Balance:** The bar is triviality, not repetition. A one-off still earns a lever when the lever is what makes the work checkable. Per the [Laziness Protocol](..\u002Fprinciple-laziness-protocol\u002FSKILL.md), build the smallest script that does or proves the job, never a framework.\n\nDistinct from [Encode Lessons in Structure](..\u002Fprinciple-encode-lessons-in-structure\u002FSKILL.md), which makes a recurring instruction a durable guardrail. This is throughput and reviewability on the work in front of you. For scripting the verification itself, see [Prove It Works](..\u002Fprinciple-prove-it-works\u002FSKILL.md).\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","9926ecfc3fc1e4c855421ee2b38f2585d8247705","pstack-claude-code\u002Fskills\u002Fprinciple-build-the-lever","https:\u002F\u002Fgithub.com\u002Fonhazrat\u002Fpstack-claude-code","https:\u002F\u002Fgithub.com\u002Fonhazrat","Software Engineer | Backend & Data Infrastructure | National Math Olympiad Gold Medalist","2026-08-20 03:30:10",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add onhazrat\u002Fpstack-claude-code --skill principle-build-the-lever",{"tool":38,"command":39},"bunx","bunx skills add onhazrat\u002Fpstack-claude-code --skill principle-build-the-lever",{"tool":41,"command":42},"pnpm","pnpm dlx skills add onhazrat\u002Fpstack-claude-code --skill principle-build-the-lever","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fonhazrat\u002Fpstack-claude-code\u002Fblob\u002Fmain\u002Fpstack-claude-code\u002Fskills\u002Fprinciple-build-the-lever\u002FSKILL.md",[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7AVSP4SKEHW5H7WKG214W0X","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\u002Fonhazrat\u002Fpstack-claude-code\u002Fblob\u002Fmain\u002Fpstack-claude-code\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7AVSMBX5DDHYN73Y3XR7MT2","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Fonhazrat\u002Fpstack-claude-code\u002Fblob\u002Fmain\u002Fpstack-claude-code\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7AVSJE524XTAY5JRSVKXY10","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fonhazrat\u002Fpstack-claude-code\u002Fblob\u002Fmain\u002Fpstack-claude-code\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7AVSERZFSC6RBASFZ97NS9N","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\u002Fonhazrat\u002Fpstack-claude-code\u002Fblob\u002Fmain\u002Fpstack-claude-code\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7AVSA9V44TDBC78RQ6A2WQN","teach","Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002Fonhazrat\u002Fpstack-claude-code\u002Fblob\u002Fmain\u002Fpstack-claude-code\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7AVS7FVBR8NKXSADKQ0BPJB","tdd","Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.","https:\u002F\u002Fgithub.com\u002Fonhazrat\u002Fpstack-claude-code\u002Fblob\u002Fmain\u002Fpstack-claude-code\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]