[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSY14G1C3VPX25GF5FNSG7":3,"skill-same:01M7CSY14G1C3VPX25GF5FNSG7":55},{"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":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7CSY14G1C3VPX25GF5FNSG7","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.","cameronjlarsen\u002Fengineering-toolkit","cameronjlarsen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F44081018?v=4","01M7CSW9ZZAK2D9T98W54VH45D","Cameron Larsen","01M7CSWA0JXH6RTFHGH204RA7F",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\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\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\n**Dispatch contract.** Resolve every configured role through [`provider-dispatch.md`](..\u002Fengineering-mode\u002Freferences\u002Fprovider-dispatch.md). Values are Routes written as `[provider:]model@effort`. On Codex, resolve remaining Claude tool names via [`codex-tools.md`](..\u002Fengineering-mode\u002Freferences\u002Fcodex-tools.md).\n\nEach spawn below names a role line in the active model sheet (see [`t3-tools.md`](..\u002Fengineering-mode\u002Freferences\u002Ft3-tools.md)) and a default. Use that line's value, or the default if the sheet or the line is missing. Leave the Route unset when the value is `auto` or `inherit-parent`.\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. Start all explorers in one fan-out phase through provider dispatch. Use the `how explorer` line (default `inherit-parent`) in `read-only` mode.\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\nDispatch one read-only lane that explores and explains in one pass using the `how explainer` line (default `inherit-parent`).\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, dispatch one read-only lane to synthesize their findings into one explanation using the `how explainer` line (default `inherit-parent`).\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","# 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\n**Dispatch contract.** Resolve every configured role through [`provider-dispatch.md`](..\u002Fengineering-mode\u002Freferences\u002Fprovider-dispatch.md). Values are Routes written as `[provider:]model@effort`. On Codex, resolve remaining Claude tool names via [`codex-tools.md`](..\u002Fengineering-mode\u002Freferences\u002Fcodex-tools.md).\n\nEach spawn below names a role line in the active model sheet (see [`t3-tools.md`](..\u002Fengineering-mode\u002Freferences\u002Ft3-tools.md)) and a default. Use that line's value, or the default if the sheet or the line is missing. Leave the Route unset when the value is `auto` or `inherit-parent`.\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. Start all explorers in one fan-out phase through provider dispatch. Use the `how explorer` line (default `inherit-parent`) in `read-only` mode.\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\nDispatch one read-only lane that explores and explains in one pass using the `how explainer` line (default `inherit-parent`).\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, dispatch one read-only lane to synthesize their findings into one explanation using the `how explainer` line (default `inherit-parent`).\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","e14e605d32e02d75d3bef1e20c21ccaa8ac05310","plugins\u002Fengineering-toolkit\u002Fskills\u002Fhow","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen","Software Engineer @TheMortgageOffice ","2026-11-04 08:21:41",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add cameronjlarsen\u002Fengineering-toolkit --skill how",{"tool":37,"command":38},"bunx","bunx skills add cameronjlarsen\u002Fengineering-toolkit --skill how",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cameronjlarsen\u002Fengineering-toolkit --skill how","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Fhow\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fexplainer-prompt.md","REFERENCE","参考文档",3085,"https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Fhow\u002Freferences\u002Fexplainer-prompt.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fexplorer-prompt.md",1135,"https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Fhow\u002Freferences\u002Fexplorer-prompt.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CT26RDV1NYPCSKMF6J22D6","work-unit-commits","Plan commits as reviewable work units. Trigger: implementation, commit splitting, stacked PRs, or keeping tests and docs with code.","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Fwork-unit-commits\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CT229DK7GNGZAC9EK10HKQ","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\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CT20NV7VM98JYJ8ZGPJRDS","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CT1ZDKYE78ZM563M21Y5YW","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CT1XX1VGTG1PA3P90ZRCDZ","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7CT1T7J6555NF1ZY5YCKX7W","thermo-nuclear-code-quality-review","Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Fthermo-nuclear-code-quality-review\u002FSKILL.md",[],[]]