[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2SNQMDK5G90FZBC1FJD27":3,"skill-same:01M7B2SNQMDK5G90FZBC1FJD27":56},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7B2SNQMDK5G90FZBC1FJD27","how",null,"Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a change.","painhardcore\u002Fpstack","painhardcore","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4718161?v=4","01M7B2JS5QJR4B3VVXX0X6NKC5","Andrei Iurchenkov","01M7B2JS6S2BCFD0FCVZZNMEZZ",22,"MIT","https:\u002F\u002Fgithub.com\u002Fpainhardcore\u002Fpstack\u002Fblob\u002Fmaster\u002Fskills\u002Fhow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: how\ndescription: Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a change.\n---\n\n# How\n\nExplore the codebase to answer \"how does X work?\" questions. Produce architectural explanations at the level of a senior engineer onboarding onto a subsystem, enough to build a working mental model, not so much that it reads like annotated source code. Use **why** when the user wants historical motivation.\n\nEvery spawn is a read-only subagent that inherits the parent model. When the host supports model selection, a fast model suits explorers and a judgment-focused model suits the explainer. Pick each subagent's reasoning level for the job, per the Subagents section of the **poteto-mode** skill. If subagents are unavailable or forbidden, do each step inline in the same order.\n\n## 1. Assess complexity\n\nIf the scope is ambiguous, state your interpretation and explore. The user can redirect.\n\n- **Simple** (a single module, a small utility, a narrow question such as \"how does function X work\"): no explorers. Spawn one explainer that explores and explains in one pass, built from `references\u002Fexplainer-prompt.md` without the explorer-findings section. Go to step 4.\n- **Complex** (a subsystem spanning multiple files or services, a cross-cutting feature, a full architectural overview): go to step 2.\n\nWhen in doubt, take the simple path.\n\n## 2. Explore (complex only)\n\nDecompose the question into 2 to 4 angles, each a distinct, non-overlapping slice of the subsystem. Start all explorers concurrently, each with `references\u002Fexplorer-prompt.md` and its angle filled in.\n\n## 3. Synthesize (complex only)\n\nOnce all explorers have returned, spawn one explainer with `references\u002Fexplainer-prompt.md` and every explorer's findings filled in.\n\n## 4. Present\n\nPresent the explainer's output. Light edits for clarity or context from the conversation are fine. Do not substantially rewrite it.\n\n## Output format\n\nThe explanation uses the sections defined in `references\u002Fexplainer-prompt.md`, dropping any that do not apply: Overview, Key Concepts, How It Works, Where Things Live, Gotchas.\n","# How\n\nExplore the codebase to answer \"how does X work?\" questions. Produce architectural explanations at the level of a senior engineer onboarding onto a subsystem, enough to build a working mental model, not so much that it reads like annotated source code. Use **why** when the user wants historical motivation.\n\nEvery spawn is a read-only subagent that inherits the parent model. When the host supports model selection, a fast model suits explorers and a judgment-focused model suits the explainer. Pick each subagent's reasoning level for the job, per the Subagents section of the **poteto-mode** skill. If subagents are unavailable or forbidden, do each step inline in the same order.\n\n## 1. Assess complexity\n\nIf the scope is ambiguous, state your interpretation and explore. The user can redirect.\n\n- **Simple** (a single module, a small utility, a narrow question such as \"how does function X work\"): no explorers. Spawn one explainer that explores and explains in one pass, built from `references\u002Fexplainer-prompt.md` without the explorer-findings section. Go to step 4.\n- **Complex** (a subsystem spanning multiple files or services, a cross-cutting feature, a full architectural overview): go to step 2.\n\nWhen in doubt, take the simple path.\n\n## 2. Explore (complex only)\n\nDecompose the question into 2 to 4 angles, each a distinct, non-overlapping slice of the subsystem. Start all explorers concurrently, each with `references\u002Fexplorer-prompt.md` and its angle filled in.\n\n## 3. Synthesize (complex only)\n\nOnce all explorers have returned, spawn one explainer with `references\u002Fexplainer-prompt.md` and every explorer's findings filled in.\n\n## 4. Present\n\nPresent the explainer's output. Light edits for clarity or context from the conversation are fine. Do not substantially rewrite it.\n\n## Output format\n\nThe explanation uses the sections defined in `references\u002Fexplainer-prompt.md`, dropping any that do not apply: Overview, Key Concepts, How It Works, Where Things Live, Gotchas.\n",{"name":5,"description":7},"master","7f2d936bba86c2c512c4ad83e759752f4f065b7c","skills\u002Fhow",4,"https:\u002F\u002Fgithub.com\u002Fpainhardcore\u002Fpstack","https:\u002F\u002Fgithub.com\u002Fpainhardcore","https:\u002F\u002Fiurchenkov.com","2026-11-14 06:02:01",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add painhardcore\u002Fpstack --skill how",{"tool":38,"command":39},"bunx","bunx skills add painhardcore\u002Fpstack --skill how",{"tool":41,"command":42},"pnpm","pnpm dlx skills add painhardcore\u002Fpstack --skill how","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpainhardcore\u002Fpstack\u002Fblob\u002Fmaster\u002Fskills\u002Fhow\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fexplainer-prompt.md","REFERENCE","参考文档",3085,"https:\u002F\u002Fgithub.com\u002Fpainhardcore\u002Fpstack\u002Fblob\u002Fmaster\u002Fskills\u002Fhow\u002Freferences\u002Fexplainer-prompt.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fexplorer-prompt.md",1135,"https:\u002F\u002Fgithub.com\u002Fpainhardcore\u002Fpstack\u002Fblob\u002Fmaster\u002Fskills\u002Fhow\u002Freferences\u002Fexplorer-prompt.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7B2Y4B9GZTVRQQEN6PQJJ8R","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\u002Fpainhardcore\u002Fpstack\u002Fblob\u002Fmaster\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7B2Y2G4D64TNX6JW7N87BKZ","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fpainhardcore\u002Fpstack\u002Fblob\u002Fmaster\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7B2Y0BESNNXSY4M7CEJVCJ3","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fpainhardcore\u002Fpstack\u002Fblob\u002Fmaster\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7B2XVPCP4X4B9ME462ZQGSP","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\u002Fpainhardcore\u002Fpstack\u002Fblob\u002Fmaster\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7B2XRE370P92ZQF9SJG3A5W","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\u002Fpainhardcore\u002Fpstack\u002Fblob\u002Fmaster\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7B2XN6VE4EZTQ84NWS7P0Q6","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\u002Fpainhardcore\u002Fpstack\u002Fblob\u002Fmaster\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]