[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4B6TC1CW31NFSDDDFD2ZN":3,"skill-same:01M7F4B6TC1CW31NFSDDDFD2ZN":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},"01M7F4B6TC1CW31NFSDDDFD2ZN","principle-fix-root-causes",null,"Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.","kaelkkd\u002Fpstack-custom","kaelkkd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F102829149?v=4","01M7F3ZXJXZJ0D8Z22W9HC9DK9","Kael","01M7F3ZXMBECXYB7Z9XZFCC7P6",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkaelkkd\u002Fpstack-custom\u002Fblob\u002Fmain\u002Fpi\u002Fskills\u002Fprinciple-fix-root-causes\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: principle-fix-root-causes\ndescription: \"Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.\"\ndisable-model-invocation: true\n---\n\n> Platform port: read [the pi adapter](..\u002F..\u002Fdocs\u002Fadapter.md) once per session before following this skill. Its mappings override Cursor-specific tools, paths, models, and commands.\n\n# Fix Root Causes\n\nWhen debugging, fix the fault, not the place where it surfaced. The symptom is where a wrong state became visible. The root cause is the first place the system did something it should not do, or failed to handle a state it should handle.\n\n**Why:** A symptom fix hides the evidence and leaves the fault free to surface somewhere else. Each one makes the system harder to reason about, because the code now carries a workaround for a bug that nobody named.\n\n**Pattern:**\n- Reproduce first.\n- Ask \"why\" at each step until the answer is a wrong decision in the code, not a consequence of an earlier one.\n- When stuck, instrument. Read the actual error and the actual state. Do not guess.\n- Ask whether the state that triggered the symptom is legitimate. If the system may be in that state, the code that broke on it is the root cause, and handling the state there is the fix. If the state should never exist, a check where it broke hides the bug. Find what produced the state. Guards, retries, swallowed errors, clamped values, and discarded state are the usual ways to hide a bug.\n- When something fails only after a restart, suspect persisted state first: config files, caches, lock files, serialized state.\n- Check for the pattern, not just the instance. Find every place with the same fault and fix them all.\n- If a workaround needs a paragraph-long comment to justify it, the code is wrong. Fix the code, not the comment.\n- If the deciding fact took a deep dig to find, propose the cheap, always-on signal that would have shown it at first look.\n","> Platform port: read [the pi adapter](..\u002F..\u002Fdocs\u002Fadapter.md) once per session before following this skill. Its mappings override Cursor-specific tools, paths, models, and commands.\n\n# Fix Root Causes\n\nWhen debugging, fix the fault, not the place where it surfaced. The symptom is where a wrong state became visible. The root cause is the first place the system did something it should not do, or failed to handle a state it should handle.\n\n**Why:** A symptom fix hides the evidence and leaves the fault free to surface somewhere else. Each one makes the system harder to reason about, because the code now carries a workaround for a bug that nobody named.\n\n**Pattern:**\n- Reproduce first.\n- Ask \"why\" at each step until the answer is a wrong decision in the code, not a consequence of an earlier one.\n- When stuck, instrument. Read the actual error and the actual state. Do not guess.\n- Ask whether the state that triggered the symptom is legitimate. If the system may be in that state, the code that broke on it is the root cause, and handling the state there is the fix. If the state should never exist, a check where it broke hides the bug. Find what produced the state. Guards, retries, swallowed errors, clamped values, and discarded state are the usual ways to hide a bug.\n- When something fails only after a restart, suspect persisted state first: config files, caches, lock files, serialized state.\n- Check for the pattern, not just the instance. Find every place with the same fault and fix them all.\n- If a workaround needs a paragraph-long comment to justify it, the code is wrong. Fix the code, not the comment.\n- If the deciding fact took a deep dig to find, propose the cheap, always-on signal that would have shown it at first look.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","8cc6c7c646a9ed488b11a63eed77a03578acb721","pi\u002Fskills\u002Fprinciple-fix-root-causes","https:\u002F\u002Fgithub.com\u002Fkaelkkd\u002Fpstack-custom","https:\u002F\u002Fgithub.com\u002Fkaelkkd","Software Developer | Web & Machine Learning | Python | Django | FastAPI | SQL","2026-11-03 20:33:32",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kaelkkd\u002Fpstack-custom --skill principle-fix-root-causes",{"tool":38,"command":39},"bunx","bunx skills add kaelkkd\u002Fpstack-custom --skill principle-fix-root-causes",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kaelkkd\u002Fpstack-custom --skill principle-fix-root-causes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaelkkd\u002Fpstack-custom\u002Fblob\u002Fmain\u002Fpi\u002Fskills\u002Fprinciple-fix-root-causes\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},"01M7F4M6855B6ATZ4C4DKVAC2H","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\u002Fkaelkkd\u002Fpstack-custom\u002Fblob\u002Fmain\u002Fupstream\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},"01M7F4M4S35H0456EERFT72DNJ","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fkaelkkd\u002Fpstack-custom\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\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},"01M7F4M2Y3AHJ0ZAXA4V340SYK","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fkaelkkd\u002Fpstack-custom\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\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},"01M7F4KZ50FF7C758931JNFBPP","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\u002Fkaelkkd\u002Fpstack-custom\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\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},"01M7F4KTS31RCAS65300SBKZ9A","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\u002Fkaelkkd\u002Fpstack-custom\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\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},"01M7F4KQZPDJGWD2CDPJQNBVRY","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\u002Fkaelkkd\u002Fpstack-custom\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]