[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F71P7V997MSJD11D8VSDJW":3,"skill-same:01M7F71P7V997MSJD11D8VSDJW":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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7F71P7V997MSJD11D8VSDJW","principle-attack-the-premise",null,"Apply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.","thoriqakbar0\u002Fpstack","thoriqakbar0","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F41317726?v=4","01M79VA5KRJ0JGV5QVY39PZ5R3","thoriq","01M7F6YHPQFXN84EM04GNWA3T6",0,"MIT","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fprinciple-attack-the-premise\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: principle-attack-the-premise\ndescription: \"Apply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.\"\nuser-invocable: false\n---\n\n# Attack the Premise\n\nWhen two or more fixes that share one premise have failed the same gate, suspect the premise, not the fixes.\n\n**Why:** Each failed fix is evidence against the belief it assumed. A third fix on the same premise spends effort where the evidence already says the cause is not.\n\n**Pattern:**\n- **Write the premise down.** The premise is the one sentence that every failed fix assumed.\n- **Test the premise before the next fix.** Find an observation that would come out differently if the premise were false, and make it. Look at how the failures are distributed, not only at how large they are. Make the check rerunnable per [Build the Lever](..\u002Fprinciple-build-the-lever\u002FSKILL.md).\n- **Follow the evidence.** If it contradicts the premise, the cause is elsewhere. Look for what the failures have in common that the premise did not predict. If it confirms the premise, ask the next \"why\" per [Fix Root Causes](..\u002Fprinciple-fix-root-causes\u002FSKILL.md). The earlier fixes may have treated a consequence instead of the cause.\n- **Remove the condition instead of compensating for it**, per the [Laziness Protocol](..\u002Fprinciple-laziness-protocol\u002FSKILL.md). If the evidence shows that one part always lands on the losing side, change what puts it there. A mechanism that cleans up after it leaves the cause in place and adds work on every run.\n\n**Stop:** Do not start the next fix before the premise is written down and tested.\n\nThis principle is distinct from [Redesign from First Principles](..\u002Fprinciple-redesign-from-first-principles\u002FSKILL.md), which rebuilds a design around a new requirement. It questions a fact the current design assumes.\n","# Attack the Premise\n\nWhen two or more fixes that share one premise have failed the same gate, suspect the premise, not the fixes.\n\n**Why:** Each failed fix is evidence against the belief it assumed. A third fix on the same premise spends effort where the evidence already says the cause is not.\n\n**Pattern:**\n- **Write the premise down.** The premise is the one sentence that every failed fix assumed.\n- **Test the premise before the next fix.** Find an observation that would come out differently if the premise were false, and make it. Look at how the failures are distributed, not only at how large they are. Make the check rerunnable per [Build the Lever](..\u002Fprinciple-build-the-lever\u002FSKILL.md).\n- **Follow the evidence.** If it contradicts the premise, the cause is elsewhere. Look for what the failures have in common that the premise did not predict. If it confirms the premise, ask the next \"why\" per [Fix Root Causes](..\u002Fprinciple-fix-root-causes\u002FSKILL.md). The earlier fixes may have treated a consequence instead of the cause.\n- **Remove the condition instead of compensating for it**, per the [Laziness Protocol](..\u002Fprinciple-laziness-protocol\u002FSKILL.md). If the evidence shows that one part always lands on the losing side, change what puts it there. A mechanism that cleans up after it leaves the cause in place and adds work on every run.\n\n**Stop:** Do not start the next fix before the premise is written down and tested.\n\nThis principle is distinct from [Redesign from First Principles](..\u002Fprinciple-redesign-from-first-principles\u002FSKILL.md), which rebuilds a design around a new requirement. It questions a fact the current design assumes.\n",{"name":5,"description":7,"user-invocable":20},"main","0d3cd5ec21bc09acc255c7f3e790b2b605e08e05","plugins\u002Fpstack\u002Fskills\u002Fprinciple-attack-the-premise","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0","bismillah","2026-11-10 11:14:55",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add thoriqakbar0\u002Fpstack --skill principle-attack-the-premise",{"tool":37,"command":38},"bunx","bunx skills add thoriqakbar0\u002Fpstack --skill principle-attack-the-premise",{"tool":40,"command":41},"pnpm","pnpm dlx skills add thoriqakbar0\u002Fpstack --skill principle-attack-the-premise","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fprinciple-attack-the-premise\u002FSKILL.md",true,[],[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},"01M7F75WF76VEQDWXFYYYM8NTQ","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\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\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},"01M7F75SBDAE54RR5QXAX4D939","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fwhat-did-i-get-done\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},"01M7F75QGP7XC377PDZ96CBWVD","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Funslop\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},"01M7F75NXH5YRSZ5ZXVTMWM3Y0","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\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},"01M7F75JM31PC9HXGYDQWY6Y1R","thermos","Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug\u002Fsecurity and code-quality branch audits.","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fthermos\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},"01M7F75FH0Y9X4MDVXF1QQEM43","thermo-nuclear-review","Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch\u002FPR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fthermo-nuclear-review\u002FSKILL.md",[],[]]