[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74GC8ZCS612MPDEDXDTPA21":3,"skill-same:01M74GC8ZCS612MPDEDXDTPA21":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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M74GC8ZCS612MPDEDXDTPA21","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.","casualjim\u002Fpi-mimir","casualjim","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F456109?v=4","01M74FWNWVYZQ29YNASRYNTCG4","Ivan Porto Carrero","01M74FWNXE5R8481XV0Q8Q7EY0",16,"MIT","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fprinciple-build-the-lever\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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\nA codemod, generator, or script does the work the same way every time and reruns for free. 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\nDefault to building the lever. Skip it only when the task is 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.\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. 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.\n\nThe 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\nA codemod, generator, or script does the work the same way every time and reruns for free. 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\nDefault to building the lever. Skip it only when the task is 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.\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. 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.\n\nThe 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","86a206d111fba4ffc9c47c363486479262e63513","packages\u002Fpi-pstack\u002Fskills\u002Fprinciple-build-the-lever",9,"https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir","https:\u002F\u002Fgithub.com\u002Fcasualjim","http:\u002F\u002Fflanders.co.nz","2026-11-10 15:32:15",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add casualjim\u002Fpi-mimir --skill principle-build-the-lever",{"tool":39,"command":40},"bunx","bunx skills add casualjim\u002Fpi-mimir --skill principle-build-the-lever",{"tool":42,"command":43},"pnpm","pnpm dlx skills add casualjim\u002Fpi-mimir --skill principle-build-the-lever","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fprinciple-build-the-lever\u002FSKILL.md",[],[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},"01M74GK3CG2X0988XMHBKNC0HG","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\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\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},"01M74GK2A4034JSAN8BCGBEPVB","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Funslop\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},"01M74GK13302GXTR58TM47BQY1","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftypescript-best-practices\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},"01M74GJYB1DJCA4AQH22MWYM9J","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Fskill:technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftechnical-writing\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},"01M74GJW7794XM60AKH76941T0","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\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fteach\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},"01M74GJPQN3RW4FN7G78W2NFR1","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\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]