[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7535T2XNDGZP1GD2AD8VHEW":3,"skill-same:01M7535T2XNDGZP1GD2AD8VHEW":45},{"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":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7535T2XNDGZP1GD2AD8VHEW","understand-onboard",null,"Use when you need to generate an onboarding guide for new team members joining a project","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-onboard\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: understand-onboard\ndescription: Use when you need to generate an onboarding guide for new team members joining a project\n---\n\n# \u002Funderstand-onboard\n\nGenerate a comprehensive onboarding guide from the project's knowledge graph.\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 generating the guide that onboarding content 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. **Read project metadata** — use Grep or Read with a line limit to extract the `\"project\"` section (name, description, languages, frameworks).\n\n4. **Read layers** — Grep for `\"layers\"` to get the full layers array. These define the architecture and will structure the guide.\n\n5. **Read the tour** — Grep for `\"tour\"` to get the guided walkthrough steps. These provide the recommended learning path.\n\n6. **Read file-level structural nodes only** — use Grep to find nodes with file-level types (`file`, `config`, `document`, `service`, `pipeline`, `table`, `schema`, `resource`, `endpoint`) in the knowledge graph. Skip function-level and class-level nodes to keep the guide high-level. Extract each node's `name`, `filePath`, `summary`, and `complexity`.\n\n7. **Identify complexity hotspots** — from the file-level nodes, find those with the highest `complexity` values. These are areas new developers should approach carefully.\n\n8. **Generate the onboarding guide** with these sections:\n   - **Project Overview**: name, languages, frameworks, description (from project metadata)\n   - **Architecture Layers**: each layer's name, description, and key files (from layers + file nodes)\n   - **Key Concepts**: important patterns and design decisions (from node summaries and tags)\n   - **Guided Tour**: step-by-step walkthrough (from the tour section)\n   - **File Map**: what each key file does (from file-level nodes, organized by layer)\n   - **Complexity Hotspots**: areas to approach carefully (from complexity values)\n\n9. Format as clean markdown\n10. Offer to save the guide to `docs\u002FONBOARDING.md` in the project\n11. Suggest the user commit it to the repo for the team\n","# \u002Funderstand-onboard\n\nGenerate a comprehensive onboarding guide from the project's knowledge graph.\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 generating the guide that onboarding content 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. **Read project metadata** — use Grep or Read with a line limit to extract the `\"project\"` section (name, description, languages, frameworks).\n\n4. **Read layers** — Grep for `\"layers\"` to get the full layers array. These define the architecture and will structure the guide.\n\n5. **Read the tour** — Grep for `\"tour\"` to get the guided walkthrough steps. These provide the recommended learning path.\n\n6. **Read file-level structural nodes only** — use Grep to find nodes with file-level types (`file`, `config`, `document`, `service`, `pipeline`, `table`, `schema`, `resource`, `endpoint`) in the knowledge graph. Skip function-level and class-level nodes to keep the guide high-level. Extract each node's `name`, `filePath`, `summary`, and `complexity`.\n\n7. **Identify complexity hotspots** — from the file-level nodes, find those with the highest `complexity` values. These are areas new developers should approach carefully.\n\n8. **Generate the onboarding guide** with these sections:\n   - **Project Overview**: name, languages, frameworks, description (from project metadata)\n   - **Architecture Layers**: each layer's name, description, and key files (from layers + file nodes)\n   - **Key Concepts**: important patterns and design decisions (from node summaries and tags)\n   - **Guided Tour**: step-by-step walkthrough (from the tour section)\n   - **File Map**: what each key file does (from file-level nodes, organized by layer)\n   - **Complexity Hotspots**: areas to approach carefully (from complexity values)\n\n9. Format as clean markdown\n10. Offer to save the guide to `docs\u002FONBOARDING.md` in the project\n11. Suggest the user commit it to the repo for the team\n",{"name":5,"description":7},"main","fa33bab5e066f61f678d15d8654b7f16fcb5aef0","skills\u002Funderstand-onboard","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":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add longhang2004\u002FTenvyr --skill understand-onboard",{"tool":37,"command":38},"bunx","bunx skills add longhang2004\u002FTenvyr --skill understand-onboard",{"tool":40,"command":41},"pnpm","pnpm dlx skills add longhang2004\u002FTenvyr --skill understand-onboard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Funderstand-onboard\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"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":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7535QQM4BVPW9S85GDJP944","understand-knowledge","Analyze a Karpathy-pattern LLM wiki knowledge base and generate an interactive knowledge graph with entity extraction, implicit relationships, and topic clustering.","https:\u002F\u002Fgithub.com\u002Flonghang2004\u002FTenvyr\u002Fblob\u002Fmain\u002Fskills\u002Funderstand-knowledge\u002FSKILL.md",[],[]]