[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4FD5HNMGP3TK381DR89Z5":3,"skill-same:01M7F4FD5HNMGP3TK381DR89Z5":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M7F4FD5HNMGP3TK381DR89Z5","how",null,"Use for \"how does X work\", code walkthroughs before changing something, and placement \u002F ownership \u002F layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.","jiangkoumo\u002Fpi-pstack","jiangkoumo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F152110621?v=4","01M7D1MDN9G4YF0GDZ26A6QK4A","01M7F4E0SAT3WG6EMQGZ9YR7D8",35,"MIT","https:\u002F\u002Fgithub.com\u002Fjiangkoumo\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fhow\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: how\ndescription: \"Use for \\\"how does X work\\\", code walkthroughs before changing something, and placement \u002F ownership \u002F layering questions (\\\"where should this live\\\", \\\"which package owns this\\\", \\\"is this the right layer\\\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.\"\ndisable-model-invocation: true\nlicense: MIT\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.\n\nEvery spawn is a `subagent` call with a registered read-only pstack agent. Explorers use the `verification` role, and every explainer uses the `judgment` role. Set the role's model and thinking through `\u002Fsetup-pstack`, or leave it at the default if the role or the line is missing. Leave `model` unset when the value is `inherit`, so that seat runs on the parent model. If the host rejects a configured model, use the default and say so. If it rejects the default, use the closest valid configured model of the same family and reasoning tier, and report the substitution. Pick each subagent's thinking for the job, per the Subagents section of the **poteto-mode** skill.\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 [explainer-prompt.md](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 slice of the subsystem. Spawn all explorers in a single message, each with [explorer-prompt.md](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\n## Pi adaptation\n\nAdapted from Lauren Tan’s pstack v0.15.25, MIT, fixed revision f713f14203cd6420cec13cd7c55c32d598dbab68. Read the [Pi adapter](..\u002F..\u002Fadapters\u002Fpi\u002Fharness.md) for host mappings.\n\nDelegation requires current operator or applicable project authorization and a compatible pi-subagents integration. If unavailable or unauthorized, perform authorized stages locally, disclose self-review and missing independence, and report any required independent stage as open. Use only registered pstack.* agents. Models and thinking bind through \u002Fsetup-pstack roles and user agentOverrides; never put model in a task item or on the outer subagent call. Report unavailable or identical configured models; do not silently substitute. Await native completion notices and collect every required result before synthesis.\n\nUse read for file contents, grep\u002Ffind\u002Fls for search and directories, and ffgrep\u002Ffffind when available. Batch independent reads with codemode when available. Use edit\u002Fwrite only for authorized changes; bash executes programs and Git in an explicit working directory, never reads or searches files. Keep one writer per worktree and isolate candidate output paths. Read-only reviewers never receive bash, edit, write, or nested delegation. Loading this skill grants no new permission: push, PR creation, merge, external messages, and destructive operations require explicit authorization in the current session. Commit only when authorized.\n\nExplorers launch together through one parallel workflow, with the angle named only in each task:\n\n```js\nsubagent({ workflow: \"parallel\", args: { tasks: [\n  { agent: \"pstack.verifier\", task: \"\u003Creferences\u002Fexplorer-prompt.md with angle 1>\" },\n  { agent: \"pstack.verifier\", task: \"\u003Creferences\u002Fexplorer-prompt.md with angle 2>\" }\n] } })\n```\n\nNever put `model` in a task item or on the outer call.\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.\n\nEvery spawn is a `subagent` call with a registered read-only pstack agent. Explorers use the `verification` role, and every explainer uses the `judgment` role. Set the role's model and thinking through `\u002Fsetup-pstack`, or leave it at the default if the role or the line is missing. Leave `model` unset when the value is `inherit`, so that seat runs on the parent model. If the host rejects a configured model, use the default and say so. If it rejects the default, use the closest valid configured model of the same family and reasoning tier, and report the substitution. Pick each subagent's thinking for the job, per the Subagents section of the **poteto-mode** skill.\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 [explainer-prompt.md](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 slice of the subsystem. Spawn all explorers in a single message, each with [explorer-prompt.md](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\n## Pi adaptation\n\nAdapted from Lauren Tan’s pstack v0.15.25, MIT, fixed revision f713f14203cd6420cec13cd7c55c32d598dbab68. Read the [Pi adapter](..\u002F..\u002Fadapters\u002Fpi\u002Fharness.md) for host mappings.\n\nDelegation requires current operator or applicable project authorization and a compatible pi-subagents integration. If unavailable or unauthorized, perform authorized stages locally, disclose self-review and missing independence, and report any required independent stage as open. Use only registered pstack.* agents. Models and thinking bind through \u002Fsetup-pstack roles and user agentOverrides; never put model in a task item or on the outer subagent call. Report unavailable or identical configured models; do not silently substitute. Await native completion notices and collect every required result before synthesis.\n\nUse read for file contents, grep\u002Ffind\u002Fls for search and directories, and ffgrep\u002Ffffind when available. Batch independent reads with codemode when available. Use edit\u002Fwrite only for authorized changes; bash executes programs and Git in an explicit working directory, never reads or searches files. Keep one writer per worktree and isolate candidate output paths. Read-only reviewers never receive bash, edit, write, or nested delegation. Loading this skill grants no new permission: push, PR creation, merge, external messages, and destructive operations require explicit authorization in the current session. Commit only when authorized.\n\nExplorers launch together through one parallel workflow, with the angle named only in each task:\n\n```js\nsubagent({ workflow: \"parallel\", args: { tasks: [\n  { agent: \"pstack.verifier\", task: \"\u003Creferences\u002Fexplorer-prompt.md with angle 1>\" },\n  { agent: \"pstack.verifier\", task: \"\u003Creferences\u002Fexplorer-prompt.md with angle 2>\" }\n] } })\n```\n\nNever put `model` in a task item or on the outer call.\n",{"name":5,"license":14,"description":7,"disable-model-invocation":23},true,"main","e6c23993b765c64906a9cd8ecd55dcecfcec908a","skills\u002Fhow",0,"https:\u002F\u002Fgithub.com\u002Fjiangkoumo\u002Fpi-pstack","https:\u002F\u002Fgithub.com\u002Fjiangkoumo","2026-11-03 09:00:34",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":23},[33,36,39],{"tool":34,"command":35},"npx","npx skills add jiangkoumo\u002Fpi-pstack --skill how",{"tool":37,"command":38},"bunx","bunx skills add jiangkoumo\u002Fpi-pstack --skill how",{"tool":40,"command":41},"pnpm","pnpm dlx skills add jiangkoumo\u002Fpi-pstack --skill how","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiangkoumo\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fhow\u002FSKILL.md",[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fexplainer-prompt.md","REFERENCE","参考文档",3112,"https:\u002F\u002Fgithub.com\u002Fjiangkoumo\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fhow\u002Freferences\u002Fexplainer-prompt.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fexplorer-prompt.md",1135,"https:\u002F\u002Fgithub.com\u002Fjiangkoumo\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fhow\u002Freferences\u002Fexplorer-prompt.md",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7F4TX6VJQXXJ05M3BY9HBKM","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\u002Fjiangkoumo\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M7F4TVBX1JES1GGRWGBXVQJ4","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fjiangkoumo\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M7F4TRZC97AQYBKJGYY1WR6S","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fjiangkoumo\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7F4TMRTJSN9M773EPYC8AV3","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\u002Fjiangkoumo\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7F4THEK20TDMKHNZ3N173FE","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\u002Fjiangkoumo\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M7F4TDXQ77E813CVDVHWX35Q","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\u002Fjiangkoumo\u002Fpi-pstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]