[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7535K5DN1RA2SJM6KVM9SW6":3,"skill-same:01M7535K5DN1RA2SJM6KVM9SW6":46},{"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":45},"01M7535K5DN1RA2SJM6KVM9SW6","understand-explain",null,"Use when you need a deep-dive explanation of a specific file, function, or module in the codebase","longhang2004\u002FTenvyr","longhang2004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F149140492?v=4","01M752YHWXV1V7TNHCK1P2SNK3","Hàng Nhựt Long","01M752YHYMBBTCMQ391XSES647",0,"MIT","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Funderstand-explain\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: understand-explain\ndescription: Use when you need a deep-dive explanation of a specific file, function, or module in the codebase\nargument-hint: \"[file-path]\"\n---\n\n# \u002Funderstand-explain\n\nProvide a thorough, in-depth explanation of a specific code component.\n\n## Graph Structure Reference\n\nThe knowledge graph JSON has this structure:\n- `project` — {name, description, languages, frameworks, analyzedAt, gitCommitHash}\n- `nodes[]` — each has {id, type, name, filePath?, summary, tags[], complexity, languageNotes?}\n  - Code node types: file, function, class, module, concept\n  - Non-code node types: config, document, service, table, endpoint, pipeline, schema, resource\n  - Domain\u002Fknowledge node types: domain, flow, step, article, entity, topic, claim, source\n  - IDs use the node type as prefix, e.g. `file:path`, `function:path:name`, `config:path`, `article:path`\n- `edges[]` — each has {source, target, type, direction, weight}\n  - Key types: imports, contains, calls, depends_on, configures, documents, deploys, triggers, contains_flow, flow_step, related, cites\n- `layers[]` — each has {id, name, description, nodeIds[]}\n- `tour[]` — each has {order, title, description, nodeIds[]}\n\n## How to Read Efficiently\n\n1. Use Grep to search within the JSON for relevant entries BEFORE reading the full file\n2. Only read sections you need — don't dump the entire graph into context\n3. Node names and summaries are the most useful fields for understanding\n4. Edges tell you how components connect — follow imports and calls for dependency chains\n\n## Instructions\n\n1. **Resolve the data directory `$UA_DIR`.** Run `UA_DIR=$([ -d .understand-anything ] && echo .understand-anything || echo .ua)` — this is the legacy `.understand-anything\u002F` when it already exists, otherwise the new `.ua\u002F`. Check that `$UA_DIR\u002Fknowledge-graph.json` exists. If not, tell the user to run `\u002Funderstand` first.\n\n2. **Check graph freshness before using graph-derived context**:\n   - Read `project.gitCommitHash` from the graph metadata as `GRAPH_COMMIT_RAW`. Resolve it as a commit before using it in any Git diff, then compare it with `git rev-parse HEAD` and inspect project-scoped committed and working-tree changes from the project root:\n     ```bash\n     GRAPH_COMMIT=$(git rev-parse --verify --end-of-options \"${GRAPH_COMMIT_RAW}^{commit}\" 2>\u002Fdev\u002Fnull)\n     git rev-parse HEAD\n     git diff --name-only \"$GRAPH_COMMIT\" HEAD -- .\n     git diff --cached --name-only -- .\n     git diff --name-only -- .\n     git ls-files --others --exclude-standard -- .\n     ```\n   - The `-- .` pathspec is required: commits that only touch a sibling monorepo project must not make this graph stale. A hash mismatch alone is not stale when the project diff is empty.\n   - Ignore the selected data directory (`.ua\u002F` or legacy `.understand-anything\u002F`) in every command's output because it contains generated graph artifacts, not project source drift.\n   - If the committed diff or any working-tree command reports project files, warn before explaining that graph-derived context may omit those changes. Suggest: Run `\u002Funderstand` to refresh the graph.\n   - Run the commit diff only when `GRAPH_COMMIT_RAW` resolves successfully. If the graph commit or Git metadata is missing, invalid, or unavailable, give a brief best-effort warning and continue instead of blocking.\n\n3. **Find the target node** — use Grep to search the knowledge graph for the component: \"$ARGUMENTS\"\n   - For file paths (e.g., `src\u002Fauth\u002Flogin.ts`): search for `\"filePath\"` matches\n   - For function notation (e.g., `src\u002Fauth\u002Flogin.ts:verifyToken`): search for the function name in `\"name\"` fields filtered by the file path\n   - Note the exact node `id`, `type`, `summary`, `tags`, and `complexity`\n\n4. **Find all connected edges** — Grep for the target node's ID in the edges section:\n   - `\"source\"` matches → things this node calls\u002Fimports\u002Fdepends on (outgoing)\n   - `\"target\"` matches → things that call\u002Fimport\u002Fdepend on this node (incoming)\n   - Note the connected node IDs and edge types\n\n5. **Read connected nodes** — for each connected node ID from step 4, Grep for those IDs in the nodes section to get their `name`, `summary`, and `type`. This builds the component's neighborhood.\n\n6. **Identify the layer** — Grep for the target node's ID in the `\"layers\"` section to find which architectural layer it belongs to and that layer's description.\n\n7. **Read the actual source file** — Read the source file at the node's `filePath` for the deep-dive analysis.\n\n8. **Explain the component in context**:\n   - Its role in the architecture (which layer, why it exists)\n   - Internal structure (functions, classes it contains — from `contains` edges)\n   - External connections (what it imports, what calls it, what it depends on — from edges)\n   - Data flow (inputs → processing → outputs — from source code)\n   - Explain clearly, assuming the reader may not know the programming language\n   - Highlight any patterns, idioms, or complexity worth understanding\n","# \u002Funderstand-explain\n\nProvide a thorough, in-depth explanation of a specific code component.\n\n## Graph Structure Reference\n\nThe knowledge graph JSON has this structure:\n- `project` — {name, description, languages, frameworks, analyzedAt, gitCommitHash}\n- `nodes[]` — each has {id, type, name, filePath?, summary, tags[], complexity, languageNotes?}\n  - Code node types: file, function, class, module, concept\n  - Non-code node types: config, document, service, table, endpoint, pipeline, schema, resource\n  - Domain\u002Fknowledge node types: domain, flow, step, article, entity, topic, claim, source\n  - IDs use the node type as prefix, e.g. `file:path`, `function:path:name`, `config:path`, `article:path`\n- `edges[]` — each has {source, target, type, direction, weight}\n  - Key types: imports, contains, calls, depends_on, configures, documents, deploys, triggers, contains_flow, flow_step, related, cites\n- `layers[]` — each has {id, name, description, nodeIds[]}\n- `tour[]` — each has {order, title, description, nodeIds[]}\n\n## How to Read Efficiently\n\n1. Use Grep to search within the JSON for relevant entries BEFORE reading the full file\n2. Only read sections you need — don't dump the entire graph into context\n3. Node names and summaries are the most useful fields for understanding\n4. Edges tell you how components connect — follow imports and calls for dependency chains\n\n## Instructions\n\n1. **Resolve the data directory `$UA_DIR`.** Run `UA_DIR=$([ -d .understand-anything ] && echo .understand-anything || echo .ua)` — this is the legacy `.understand-anything\u002F` when it already exists, otherwise the new `.ua\u002F`. Check that `$UA_DIR\u002Fknowledge-graph.json` exists. If not, tell the user to run `\u002Funderstand` first.\n\n2. **Check graph freshness before using graph-derived context**:\n   - Read `project.gitCommitHash` from the graph metadata as `GRAPH_COMMIT_RAW`. Resolve it as a commit before using it in any Git diff, then compare it with `git rev-parse HEAD` and inspect project-scoped committed and working-tree changes from the project root:\n     ```bash\n     GRAPH_COMMIT=$(git rev-parse --verify --end-of-options \"${GRAPH_COMMIT_RAW}^{commit}\" 2>\u002Fdev\u002Fnull)\n     git rev-parse HEAD\n     git diff --name-only \"$GRAPH_COMMIT\" HEAD -- .\n     git diff --cached --name-only -- .\n     git diff --name-only -- .\n     git ls-files --others --exclude-standard -- .\n     ```\n   - The `-- .` pathspec is required: commits that only touch a sibling monorepo project must not make this graph stale. A hash mismatch alone is not stale when the project diff is empty.\n   - Ignore the selected data directory (`.ua\u002F` or legacy `.understand-anything\u002F`) in every command's output because it contains generated graph artifacts, not project source drift.\n   - If the committed diff or any working-tree command reports project files, warn before explaining that graph-derived context may omit those changes. Suggest: Run `\u002Funderstand` to refresh the graph.\n   - Run the commit diff only when `GRAPH_COMMIT_RAW` resolves successfully. If the graph commit or Git metadata is missing, invalid, or unavailable, give a brief best-effort warning and continue instead of blocking.\n\n3. **Find the target node** — use Grep to search the knowledge graph for the component: \"$ARGUMENTS\"\n   - For file paths (e.g., `src\u002Fauth\u002Flogin.ts`): search for `\"filePath\"` matches\n   - For function notation (e.g., `src\u002Fauth\u002Flogin.ts:verifyToken`): search for the function name in `\"name\"` fields filtered by the file path\n   - Note the exact node `id`, `type`, `summary`, `tags`, and `complexity`\n\n4. **Find all connected edges** — Grep for the target node's ID in the edges section:\n   - `\"source\"` matches → things this node calls\u002Fimports\u002Fdepends on (outgoing)\n   - `\"target\"` matches → things that call\u002Fimport\u002Fdepend on this node (incoming)\n   - Note the connected node IDs and edge types\n\n5. **Read connected nodes** — for each connected node ID from step 4, Grep for those IDs in the nodes section to get their `name`, `summary`, and `type`. This builds the component's neighborhood.\n\n6. **Identify the layer** — Grep for the target node's ID in the `\"layers\"` section to find which architectural layer it belongs to and that layer's description.\n\n7. **Read the actual source file** — Read the source file at the node's `filePath` for the deep-dive analysis.\n\n8. **Explain the component in context**:\n   - Its role in the architecture (which layer, why it exists)\n   - Internal structure (functions, classes it contains — from `contains` edges)\n   - External connections (what it imports, what calls it, what it depends on — from edges)\n   - Data flow (inputs → processing → outputs — from source code)\n   - Explain clearly, assuming the reader may not know the programming language\n   - Highlight any patterns, idioms, or complexity worth understanding\n",{"name":5,"description":7,"argument-hint":24},"[file-path]","main","fa33bab5e066f61f678d15d8654b7f16fcb5aef0","skills\u002Funderstand-explain","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr","https:\u002F\u002Fgithub.com\u002Flonghang2004","https:\u002F\u002Flonghang2004.github.io\u002Fportfolio-website\u002F","2026-10-17 00:52:25",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add longhang2004\u002FTenvyr --skill understand-explain",{"tool":38,"command":39},"bunx","bunx skills add longhang2004\u002FTenvyr --skill understand-explain",{"tool":41,"command":42},"pnpm","pnpm dlx skills add longhang2004\u002FTenvyr --skill understand-explain","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Funderstand-explain\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M75368XG3WHG7S884RH1FQEG","wowerpoint","Turn one document into a kawaii NotebookLM slide-deck PDF. Use for \"wowerpoint this\", \"make a deck about \u003Cfile>\", \"turn this report into slides\", or any request to render a single document as shareable narrative slides.","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Fwowerpoint\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7536783K0EKKQ66A56RJ262","what-the","What the? Use when the user wants a plain-English breakdown of something technical — the who, what, where, why, and when.","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Fwhat-the\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M75362M917THP79D9APYRKTE","weekly-digests","Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for \"weekly digests\", \"week-by-week story\", \"serial timeline\", or \"narrative chapters\" of a project's history.","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Fweekly-digests\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7535ZRATN41PZHPPWZEBM8E","version-bump","Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing (so `npx claude-mem@X.Y.Z` resolves) is handed off to the human maintainer, who raised npm security.","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Fversion-bump\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7535VQDD9MXAYXH6N2E8FFJ","understand","Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Funderstand\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7535T2XNDGZP1GD2AD8VHEW","understand-onboard","Use when you need to generate an onboarding guide for new team members joining a project","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Funderstand-onboard\u002FSKILL.md",[],[]]