[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79R7YC44AVQNBY930V32VBB":3,"skill-same:01M79R7YC44AVQNBY930V32VBB":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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M79R7YC44AVQNBY930V32VBB","explain-codebase-concept",null,"Onboard to how one Ahentic concept, feature, or subsystem is wired — chat summary plus visual HTML walkthrough (optional durable copy under docs\u002Fwalkthroughs\u002F).","gambitph\u002FAhentic","gambitph","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3227089?v=4","01M6C1ZD8129MTRC23K53VJ45E","Gambit Technologies","01M79R7A85NS2N9JAK7AC0NE1X",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fexplain-codebase-concept\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: explain-codebase-concept\ndescription: Onboard to how one Ahentic concept, feature, or subsystem is wired — chat summary plus visual HTML walkthrough (optional durable copy under docs\u002Fwalkthroughs\u002F).\ndisable-model-invocation: true\n---\n\n# Explain Codebase Concept\n\nOnboard a **repo \u002F Ahentic beginner** (stack-literate: WP\u002FJS assumed) to **one** concept, feature, or subsystem so they can contribute — extend, fix bugs, or add related behavior — without inventing a second architecture doc.\n\n**Deliverables (every run):** chat summary **and** a self-contained HTML walkthrough (Tailwind + Mermaid).  \n**Authority:** compose and cite the doc ladder + live code. PRD \u002F CONTRACT win on disagreement. Flag drift; **offer** doc fixes — do not auto-write product law.  \n**Not this skill:** deepening\u002Frefactor candidates (`improve-codebase-architecture`), bug hunts (`diagnosing-bugs`), or a whole-product tour (point at `docs\u002Farchitecture.md` and offer a menu of slices).\n\nSee [HTML-REPORT.md](HTML-REPORT.md) for the report scaffold and section rules. Human index: [`docs\u002Fagents\u002Fexplain-concept.md`](..\u002F..\u002F..\u002Fdocs\u002Fagents\u002Fexplain-concept.md).\n\n## Process\n\n### 1. Scope\n\n**Done when:** one coherent slice is named in a single sentence (concept \u002F flow \u002F subsystem), or the user picked from a short menu.\n\n- If the ask maps cleanly to `CONTEXT.md`, `docs\u002Farchitecture.md`, or a `CONTRACT.md` → state the assumed scope and proceed.\n- If several slices fit → offer a **short menu** (A \u002F B \u002F C), not a full grill.\n- If they ask to “explain all of Ahentic” → point at [`docs\u002Farchitecture.md`](..\u002F..\u002F..\u002Fdocs\u002Farchitecture.md); offer 3–5 high-value follow-on concepts. Do not generate a mega-walkthrough.\n\nNormalize subsystem \u002F filename asks into the **runtime path that makes the concept real** (sidebar → REST → orchestrator → …), not a folder dump.\n\n### 2. Explore\n\n**Done when:** glossary terms for the slice are loaded, the relevant CONTRACT + how-it-works are read, the live path is traced, and any doc↔code drift is noted.\n\n1. **Docs-first ladder** (skip missing files silently): `CONTEXT.md` → `docs\u002Farchitecture.md` → relevant `src\u002F**\u002FCONTRACT.md` + colocated how-it-works → PRD\u002FADR only if the slice is about intended behavior or a recorded trade-off.\n2. **Code trace** — use the Agent tool with `subagent_type=Explore` to follow the runtime path end-to-end. Neighbors that are not load-bearing stay **black boxes** with pointers to their CONTRACT \u002F how-it-works.\n3. Collect primary files and key symbols for the Cast and Step-through (prefer a tight set over exhaustiveness).\n4. Note contribution hooks: usual touch path, ability-checklist \u002F tests \u002F catalogues that must stay in sync when this slice changes.\n\nUse **CONTEXT.md** vocabulary for domain names. Use codebase-design terms (`module`, `seam`, `interface`, …) **only** in Neighbors \u002F Change map when they help a contributor locate a change. Keep ELI5 in plain English.\n\n### 3. Write the HTML walkthrough\n\n**Done when:** the file exists, opens in the browser, and contains all nine mandatory sections in order (see [HTML-REPORT.md](HTML-REPORT.md)).\n\n1. Resolve temp dir from `$TMPDIR`, else `\u002Ftmp` (or `%TEMP%` on Windows).\n2. Write `$TMPDIR\u002Fconcept-walkthrough-\u003Cslug>-\u003Ctimestamp>.html` (slug from the concept name; kebab-case).\n3. Open it: `open \u003Cpath>` (macOS), `xdg-open \u003Cpath>` (Linux), `start \u003Cpath>` (Windows).\n4. Tell the user the absolute path.\n\nEmpty sections still appear as a one-liner (e.g. “No doc drift found”) so the shape stays recognizable.\n\n### 4. Chat handoff\n\n**Done when:** the user has a short summary in-thread and clear next offers.\n\nIn chat (≈5–8 lines):\n\n- What the concept is (one sentence)\n- The runtime path in plain words\n- Where to look first (2–4 primary files)\n- How you’d usually change it (one sentence)\n- Absolute path to the HTML file\n\nThen **offer**:\n\n- (a) zoom a black-boxed neighbor into its own walkthrough  \n- (b) walk a related concept  \n- (c) fix doc drift (if any were listed)  \n- (d) **save a durable copy** under `docs\u002Fwalkthroughs\u002F` for humans (see below)\n\n### 5. Durable docs (optional)\n\n**Done when:** either the user declined, or `docs\u002Fwalkthroughs\u002F\u003Cslug>.html` is written, the folder README index lists it, and the HTML banner states it is pedagogical — not product law.\n\nDefault output stays in temp. When the user asks to keep \u002F commit \u002F add as docs:\n\n1. Write (or refresh) `docs\u002Fwalkthroughs\u002F\u003Cslug>.html` with the **same** mandatory outline and a visible banner: pedagogical walkthrough; PRD \u002F CONTRACT \u002F how-it-works win; regenerate when the slice drifts.\n2. Update `docs\u002Fwalkthroughs\u002FREADME.md` index (slug, title, one-line summary, date).\n3. Do **not** `git commit` unless the user explicitly asks. Do **not** invent product “should” in the walkthrough — cite PRDs; absorb real product gaps via domain-modeling \u002F PRD edits only when the user accepts that offer.\n4. Do **not** replace or duplicate `CONTRACT.md` \u002F colocated how-it-works as the source of truth; the walkthrough **points at** them.\n\nWalkthroughs are supporting orientation maps (cross-stack, beginner-shaped). They are not a fourth product-law surface (see ADR-0001 \u002F PRD index).\n\n## Collision guard\n\n| Ask | Skill |\n| --- | --- |\n| How does X work \u002F onboard me on X | **This skill** |\n| Deepen \u002F shallow modules \u002F architecture review | `improve-codebase-architecture` |\n| Something’s broken \u002F failing | `diagnosing-bugs` |\n| Whole-system map only | `docs\u002Farchitecture.md` (no mega-HTML) |\n","# Explain Codebase Concept\n\nOnboard a **repo \u002F Ahentic beginner** (stack-literate: WP\u002FJS assumed) to **one** concept, feature, or subsystem so they can contribute — extend, fix bugs, or add related behavior — without inventing a second architecture doc.\n\n**Deliverables (every run):** chat summary **and** a self-contained HTML walkthrough (Tailwind + Mermaid).  \n**Authority:** compose and cite the doc ladder + live code. PRD \u002F CONTRACT win on disagreement. Flag drift; **offer** doc fixes — do not auto-write product law.  \n**Not this skill:** deepening\u002Frefactor candidates (`improve-codebase-architecture`), bug hunts (`diagnosing-bugs`), or a whole-product tour (point at `docs\u002Farchitecture.md` and offer a menu of slices).\n\nSee [HTML-REPORT.md](HTML-REPORT.md) for the report scaffold and section rules. Human index: [`docs\u002Fagents\u002Fexplain-concept.md`](..\u002F..\u002F..\u002Fdocs\u002Fagents\u002Fexplain-concept.md).\n\n## Process\n\n### 1. Scope\n\n**Done when:** one coherent slice is named in a single sentence (concept \u002F flow \u002F subsystem), or the user picked from a short menu.\n\n- If the ask maps cleanly to `CONTEXT.md`, `docs\u002Farchitecture.md`, or a `CONTRACT.md` → state the assumed scope and proceed.\n- If several slices fit → offer a **short menu** (A \u002F B \u002F C), not a full grill.\n- If they ask to “explain all of Ahentic” → point at [`docs\u002Farchitecture.md`](..\u002F..\u002F..\u002Fdocs\u002Farchitecture.md); offer 3–5 high-value follow-on concepts. Do not generate a mega-walkthrough.\n\nNormalize subsystem \u002F filename asks into the **runtime path that makes the concept real** (sidebar → REST → orchestrator → …), not a folder dump.\n\n### 2. Explore\n\n**Done when:** glossary terms for the slice are loaded, the relevant CONTRACT + how-it-works are read, the live path is traced, and any doc↔code drift is noted.\n\n1. **Docs-first ladder** (skip missing files silently): `CONTEXT.md` → `docs\u002Farchitecture.md` → relevant `src\u002F**\u002FCONTRACT.md` + colocated how-it-works → PRD\u002FADR only if the slice is about intended behavior or a recorded trade-off.\n2. **Code trace** — use the Agent tool with `subagent_type=Explore` to follow the runtime path end-to-end. Neighbors that are not load-bearing stay **black boxes** with pointers to their CONTRACT \u002F how-it-works.\n3. Collect primary files and key symbols for the Cast and Step-through (prefer a tight set over exhaustiveness).\n4. Note contribution hooks: usual touch path, ability-checklist \u002F tests \u002F catalogues that must stay in sync when this slice changes.\n\nUse **CONTEXT.md** vocabulary for domain names. Use codebase-design terms (`module`, `seam`, `interface`, …) **only** in Neighbors \u002F Change map when they help a contributor locate a change. Keep ELI5 in plain English.\n\n### 3. Write the HTML walkthrough\n\n**Done when:** the file exists, opens in the browser, and contains all nine mandatory sections in order (see [HTML-REPORT.md](HTML-REPORT.md)).\n\n1. Resolve temp dir from `$TMPDIR`, else `\u002Ftmp` (or `%TEMP%` on Windows).\n2. Write `$TMPDIR\u002Fconcept-walkthrough-\u003Cslug>-\u003Ctimestamp>.html` (slug from the concept name; kebab-case).\n3. Open it: `open \u003Cpath>` (macOS), `xdg-open \u003Cpath>` (Linux), `start \u003Cpath>` (Windows).\n4. Tell the user the absolute path.\n\nEmpty sections still appear as a one-liner (e.g. “No doc drift found”) so the shape stays recognizable.\n\n### 4. Chat handoff\n\n**Done when:** the user has a short summary in-thread and clear next offers.\n\nIn chat (≈5–8 lines):\n\n- What the concept is (one sentence)\n- The runtime path in plain words\n- Where to look first (2–4 primary files)\n- How you’d usually change it (one sentence)\n- Absolute path to the HTML file\n\nThen **offer**:\n\n- (a) zoom a black-boxed neighbor into its own walkthrough  \n- (b) walk a related concept  \n- (c) fix doc drift (if any were listed)  \n- (d) **save a durable copy** under `docs\u002Fwalkthroughs\u002F` for humans (see below)\n\n### 5. Durable docs (optional)\n\n**Done when:** either the user declined, or `docs\u002Fwalkthroughs\u002F\u003Cslug>.html` is written, the folder README index lists it, and the HTML banner states it is pedagogical — not product law.\n\nDefault output stays in temp. When the user asks to keep \u002F commit \u002F add as docs:\n\n1. Write (or refresh) `docs\u002Fwalkthroughs\u002F\u003Cslug>.html` with the **same** mandatory outline and a visible banner: pedagogical walkthrough; PRD \u002F CONTRACT \u002F how-it-works win; regenerate when the slice drifts.\n2. Update `docs\u002Fwalkthroughs\u002FREADME.md` index (slug, title, one-line summary, date).\n3. Do **not** `git commit` unless the user explicitly asks. Do **not** invent product “should” in the walkthrough — cite PRDs; absorb real product gaps via domain-modeling \u002F PRD edits only when the user accepts that offer.\n4. Do **not** replace or duplicate `CONTRACT.md` \u002F colocated how-it-works as the source of truth; the walkthrough **points at** them.\n\nWalkthroughs are supporting orientation maps (cross-stack, beginner-shaped). They are not a fourth product-law surface (see ADR-0001 \u002F PRD index).\n\n## Collision guard\n\n| Ask | Skill |\n| --- | --- |\n| How does X work \u002F onboard me on X | **This skill** |\n| Deepen \u002F shallow modules \u002F architecture review | `improve-codebase-architecture` |\n| Something’s broken \u002F failing | `diagnosing-bugs` |\n| Whole-system map only | `docs\u002Farchitecture.md` (no mega-HTML) |\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","c4de8c3c2dcdca2892337cdc47c05dcb1cea8562",".cursor\u002Fskills\u002Fexplain-codebase-concept","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic","https:\u002F\u002Fgithub.com\u002Fgambitph","https:\u002F\u002Fwpstackable.com","2026-08-15 14:40:10",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add gambitph\u002FAhentic --skill explain-codebase-concept",{"tool":38,"command":39},"bunx","bunx skills add gambitph\u002FAhentic --skill explain-codebase-concept",{"tool":41,"command":42},"pnpm","pnpm dlx skills add gambitph\u002FAhentic --skill explain-codebase-concept","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fexplain-codebase-concept\u002FSKILL.md",[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",164,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fexplain-codebase-concept\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"HTML-REPORT.md",4938,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fexplain-codebase-concept\u002FHTML-REPORT.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},"01M79RB5GMQX62XBSR4XMJ3758","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwriting-for-agents\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},"01M79RB0ET331AVRW6W4JAW30C","wp-rest-api","Use when building, extending, or debugging WordPress REST API endpoints\u002Froutes: register_rest_route, WP_REST_Controller\u002Fcontroller classes, schema\u002Fargument validation, permission_callback\u002Fauthentication, response shaping, register_rest_field\u002Fregister_meta, or exposing CPTs\u002Ftaxonomies via show_in_rest.","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-rest-api\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},"01M79RAX0CGSMDWJ7F5DATG4WF","wp-project-triage","Use when you need a deterministic inspection of a WordPress repository (plugin\u002Ftheme\u002Fblock theme\u002FWP core\u002FGutenberg\u002Ffull site) including tooling\u002Ftests\u002Fversion hints, and a structured JSON report to guide workflows and guardrails.","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-project-triage\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},"01M79RAQ5Q24QC2W4M3XDM2195","wp-plugin-directory-guidelines","Use when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell\u002Ffreemium\u002Ftrialware patterns, validating plugin naming or trademark rules, checking plugin slugs, understanding why a plugin was rejected from WordPress.org, or answering any question about the 18 WordPress.org Plugin Directory guidelines — even if the user doesn't mention 'guidelines' explicitly.","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-plugin-directory-guidelines\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},"01M79RAJ56J66CKG54B0SBK8PX","wp-plugin-development","Use when developing WordPress plugins: architecture and hooks, activation\u002Fdeactivation\u002Funinstall, admin UI and Settings API, data storage, cron\u002Ftasks, security (nonces\u002Fcapabilities\u002Fsanitization\u002Fescaping), and release packaging.","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-plugin-development\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},"01M79RACN5F4BJYC0QX4MBFV0P","wp-performance","Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile\u002Fdoctor, Server-Timing, Query Monitor via REST headers), database\u002Fquery optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002FSKILL.md",[],[]]