[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F2MHBH4TM1KWXJERCZX045":3,"skill-same:01M7F2MHBH4TM1KWXJERCZX045":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},"01M7F2MHBH4TM1KWXJERCZX045","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.","dinhtungdu\u002Fpstack-ports","dinhtungdu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5423135?v=4","01M7F2HN2HDZGG0QN36EJCB2F1","Tung Du","01M7F2HN342B7B73D1E62THDNT",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdinhtungdu\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fantigravity\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.\"\n---\n\n**Antigravity port.** Load the pstack-harness-adapter skill before following this skill. It replaces Cursor tool, model, history, scheduling, and authorization instructions below.\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","**Antigravity port.** Load the pstack-harness-adapter skill before following this skill. It replaces Cursor tool, model, history, scheduling, and authorization instructions below.\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",{"name":5,"description":7},"main","bc0864959633cc8e0b15de9eb854ebf18d20b960","antigravity\u002Fskills\u002Fprinciple-attack-the-premise","https:\u002F\u002Fgithub.com\u002Fdinhtungdu\u002Fpstack-ports","https:\u002F\u002Fgithub.com\u002Fdinhtungdu","tungdu.com","Software Engineer","2026-11-03 14:59:15",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add dinhtungdu\u002Fpstack-ports --skill principle-attack-the-premise",{"tool":38,"command":39},"bunx","bunx skills add dinhtungdu\u002Fpstack-ports --skill principle-attack-the-premise",{"tool":41,"command":42},"pnpm","pnpm dlx skills add dinhtungdu\u002Fpstack-ports --skill principle-attack-the-premise","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdinhtungdu\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fantigravity\u002Fskills\u002Fprinciple-attack-the-premise\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},"01M7F38VPCPT2S7GWN496R42YN","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\u002Fdinhtungdu\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\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},"01M7F38T3FTZJTSQW2RYHEA11Q","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fdinhtungdu\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\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},"01M7F38Q7G9VS9PF5VV7EH8JNG","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fdinhtungdu\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\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},"01M7F38HZTJ3XKB8PJG7KMQ6P3","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\u002Fdinhtungdu\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\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},"01M7F38DEPXAX50KAR8C44CYH5","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\u002Fdinhtungdu\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\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},"01M7F3899BP7D6ZEEV8V3JJCKT","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\u002Fdinhtungdu\u002Fpstack-ports\u002Fblob\u002Fmain\u002Fupstream\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]