[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E6V8K2MDRCFRDNF6AXF76F":3,"skill-same:01M7E6V8K2MDRCFRDNF6AXF76F":57},{"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":31,"updatedAt":32,"install":33,"resources":46},"01M7E6V8K2MDRCFRDNF6AXF76F","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.","paramcodes\u002Fostack","paramcodes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F190682747?v=4","01M7E6SGQX3X1GN8QHH9TPRN6Y","Paramveer Singh","01M7E6SGRXBACX52S3T6J2RGCX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fhow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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.\"\n---\n\nThis skill is invoked only via `\u002Fhow` or an explicit user request. Do not auto-trigger from the description alone.\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\nEach spawn below names a role line in the `~\u002F.config\u002Fopencode\u002Fpstack-models.json` file and a default. Set `model` to that line's value, or to the default if the rule or the line is missing. Leave `model` unset when the value is `auto` or `inherit-parent`. If the subagent tool rejects a slug, use the default and say so. If it rejects the default, use the closest valid slug of the same family from its error message.\n\n## Step 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. One explainer explores and explains in a single pass. Go to Step 2b.\n- **Complex** (a subsystem spanning multiple files or services, a cross-cutting feature, a full architectural overview): spawn parallel explorers first, then hand off to the explainer. Go to Step 2a.\n\nWhen in doubt, take the simple path.\n\n## Step 2a. Explore (complex questions only)\n\nDecompose the question into 2 to 4 exploration angles, each a distinct slice of the subsystem. Spawn all explorers in a single message:\n\n- `agent`: `general`\n- `model`: the `how explorer` line, default `grok-4.7-xhigh-fast`\n- `readonly`: `true`\n\nEach explorer gets the prompt in `references\u002Fexplorer-prompt.md` with its angle filled in. Then go to Step 3.\n\n## Step 2b. Direct Explain (simple questions)\n\nSpawn one subagent that explores and explains in one pass:\n\n- `agent`: `general`\n- `model`: the `how explainer` line, default `claude-opus-5-5-max`\n- `readonly`: `true`\n\nBuild its prompt from `references\u002Fexplainer-prompt.md` without the explorer-findings section. Go to Step 4.\n\n## Step 3. Synthesize (complex questions only)\n\nOnce all explorers have returned, spawn one subagent to synthesize their findings into one explanation:\n\n- `agent`: `general`\n- `model`: the `how explainer` line, default `claude-opus-5-5-max`\n- `readonly`: `true`\n\nBuild its prompt from `references\u002Fexplainer-prompt.md` with every explorer's findings filled in.\n\n## Step 4. Present\n\nPresent the explainer's output to the user. 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","This skill is invoked only via `\u002Fhow` or an explicit user request. Do not auto-trigger from the description alone.\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\nEach spawn below names a role line in the `~\u002F.config\u002Fopencode\u002Fpstack-models.json` file and a default. Set `model` to that line's value, or to the default if the rule or the line is missing. Leave `model` unset when the value is `auto` or `inherit-parent`. If the subagent tool rejects a slug, use the default and say so. If it rejects the default, use the closest valid slug of the same family from its error message.\n\n## Step 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. One explainer explores and explains in a single pass. Go to Step 2b.\n- **Complex** (a subsystem spanning multiple files or services, a cross-cutting feature, a full architectural overview): spawn parallel explorers first, then hand off to the explainer. Go to Step 2a.\n\nWhen in doubt, take the simple path.\n\n## Step 2a. Explore (complex questions only)\n\nDecompose the question into 2 to 4 exploration angles, each a distinct slice of the subsystem. Spawn all explorers in a single message:\n\n- `agent`: `general`\n- `model`: the `how explorer` line, default `grok-4.7-xhigh-fast`\n- `readonly`: `true`\n\nEach explorer gets the prompt in `references\u002Fexplorer-prompt.md` with its angle filled in. Then go to Step 3.\n\n## Step 2b. Direct Explain (simple questions)\n\nSpawn one subagent that explores and explains in one pass:\n\n- `agent`: `general`\n- `model`: the `how explainer` line, default `claude-opus-5-5-max`\n- `readonly`: `true`\n\nBuild its prompt from `references\u002Fexplainer-prompt.md` without the explorer-findings section. Go to Step 4.\n\n## Step 3. Synthesize (complex questions only)\n\nOnce all explorers have returned, spawn one subagent to synthesize their findings into one explanation:\n\n- `agent`: `general`\n- `model`: the `how explainer` line, default `claude-opus-5-5-max`\n- `readonly`: `true`\n\nBuild its prompt from `references\u002Fexplainer-prompt.md` with every explorer's findings filled in.\n\n## Step 4. Present\n\nPresent the explainer's output to the user. 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},"main","6bfc4d0a61ace77dcf2857f34c360cd50ec78604","content\u002Fskills\u002Fhow",0,"https:\u002F\u002Fgithub.com\u002Fparamcodes\u002Fostack","https:\u002F\u002Fgithub.com\u002Fparamcodes","paramveer.me","on my way to become 1000x engineer","2026-10-06 19:51:22",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add paramcodes\u002Fostack --skill how",{"tool":39,"command":40},"bunx","bunx skills add paramcodes\u002Fostack --skill how",{"tool":42,"command":43},"pnpm","pnpm dlx skills add paramcodes\u002Fostack --skill how","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fhow\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fexplainer-prompt.md","REFERENCE","参考文档",3085,"https:\u002F\u002Fgithub.com\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fhow\u002Freferences\u002Fexplainer-prompt.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fexplorer-prompt.md",2684,"https:\u002F\u002Fgithub.com\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fhow\u002Freferences\u002Fexplorer-prompt.md",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7E70AA1SXNZ7MYB8Y5PJ1W0","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\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7E708BD5REN09DTH0AR2M8K","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7E706HRA328SZJPQBX333W5","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7E701YECJYA8SNV5VX35Z8F","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\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7E6ZYXGM639ZFDP9Q5CEQW2","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\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7E6ZTGNBWCX5CZXASPN2GDG","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\u002Fparamcodes\u002Fostack\u002Fblob\u002Fmain\u002Fcontent\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]