[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M756NF79MR3DD69W7XJAT2PB":3,"skill-same:01M756NF79MR3DD69W7XJAT2PB":53},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M756NF79MR3DD69W7XJAT2PB","understand-domain",null,"Extract business domain knowledge from a codebase and generate an interactive domain flow graph. Works standalone (lightweight scan) or derives from an existing \u002Funderstand knowledge graph.","Ikeu-1030\u002FiRun","Ikeu-1030","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F229719040?v=4","01M756CMM1YGXYJFY5C8ABR8Y1","ikeu","01M756CMMSQXPZW8JGYCRGYEK9",5,"MIT","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-domain\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: understand-domain\ndescription: Extract business domain knowledge from a codebase and generate an interactive domain flow graph. Works standalone (lightweight scan) or derives from an existing \u002Funderstand knowledge graph.\nargument-hint: [--full]\n---\n\n# \u002Funderstand-domain\n\nExtracts business domain knowledge — domains, business flows, and process steps — from a codebase and produces an interactive horizontal flow graph in the dashboard.\n\n## How It Works\n\n- If a knowledge graph already exists (`.understand-anything\u002Fknowledge-graph.json`), derives domain knowledge from it (cheap, no file scanning)\n- If no knowledge graph exists, performs a lightweight scan: file tree + entry point detection + sampled files\n- Use `--full` flag to force a fresh scan even if a knowledge graph exists\n\n## Instructions\n\n### Phase 0: Resolve `PROJECT_ROOT`\n\nSet `PROJECT_ROOT` to the current working directory.\n\n**Worktree redirect.** If `PROJECT_ROOT` is inside a git worktree (not the main checkout), redirect output to the main repository root. Worktrees managed by Claude Code are ephemeral — `.understand-anything\u002F` written there is destroyed when the session ends, taking the domain graph with it (issue #133). Detect a worktree by comparing `git rev-parse --git-dir` against `git rev-parse --git-common-dir`; in a normal checkout or submodule they resolve to the same path, in a worktree they differ and the parent of `--git-common-dir` is the main repo root.\n\n```bash\nCOMMON_DIR=$(git -C \"$PROJECT_ROOT\" rev-parse --git-common-dir 2>\u002Fdev\u002Fnull)\nGIT_DIR=$(git -C \"$PROJECT_ROOT\" rev-parse --git-dir 2>\u002Fdev\u002Fnull)\nif [ -n \"$COMMON_DIR\" ] && [ -n \"$GIT_DIR\" ]; then\n  COMMON_ABS=$(cd \"$PROJECT_ROOT\" && cd \"$COMMON_DIR\" 2>\u002Fdev\u002Fnull && pwd -P)\n  GIT_ABS=$(cd \"$PROJECT_ROOT\" && cd \"$GIT_DIR\" 2>\u002Fdev\u002Fnull && pwd -P)\n  if [ -n \"$COMMON_ABS\" ] && [ \"$COMMON_ABS\" != \"$GIT_ABS\" ]; then\n    MAIN_ROOT=$(dirname \"$COMMON_ABS\")\n    if [ -d \"$MAIN_ROOT\" ] && [ \"${UNDERSTAND_NO_WORKTREE_REDIRECT:-0}\" != \"1\" ]; then\n      echo \"[understand-domain] Detected git worktree at $PROJECT_ROOT\"\n      echo \"[understand-domain] Redirecting output to main repo root: $MAIN_ROOT\"\n      echo \"[understand-domain] (Set UNDERSTAND_NO_WORKTREE_REDIRECT=1 to keep PROJECT_ROOT as the worktree.)\"\n      PROJECT_ROOT=\"$MAIN_ROOT\"\n    fi\n  fi\nfi\n```\n\nUse `$PROJECT_ROOT` (not the bare CWD) for every reference to \"the current project\" \u002F `\u003Cproject-root>` in subsequent phases.\n\n**Important:** do **not** assume the plugin root is simply two directories above the skill path string. In many installations `~\u002F.agents\u002Fskills\u002Funderstand-domain` is a symlink into the real plugin checkout. Prefer runtime-provided plugin roots first (for Claude), then fall back to universal symlinks, skill symlink resolution, and common clone-based install paths.\n\nResolve the plugin root like this:\n\n```bash\nSKILL_REAL=$(realpath ~\u002F.agents\u002Fskills\u002Funderstand-domain 2>\u002Fdev\u002Fnull || readlink -f ~\u002F.agents\u002Fskills\u002Funderstand-domain 2>\u002Fdev\u002Fnull || echo \"\")\nSELF_RELATIVE=$([ -n \"$SKILL_REAL\" ] && cd \"$SKILL_REAL\u002F..\u002F..\" 2>\u002Fdev\u002Fnull && pwd || echo \"\")\nCOPILOT_SKILL_REAL=$(realpath ~\u002F.copilot\u002Fskills\u002Funderstand-domain 2>\u002Fdev\u002Fnull || readlink -f ~\u002F.copilot\u002Fskills\u002Funderstand-domain 2>\u002Fdev\u002Fnull || echo \"\")\nCOPILOT_SELF_RELATIVE=$([ -n \"$COPILOT_SKILL_REAL\" ] && cd \"$COPILOT_SKILL_REAL\u002F..\u002F..\" 2>\u002Fdev\u002Fnull && pwd || echo \"\")\n\nPLUGIN_ROOT=\"\"\nfor candidate in \\\n  \"${CLAUDE_PLUGIN_ROOT}\" \\\n  \"$HOME\u002F.understand-anything-plugin\" \\\n  \"$SELF_RELATIVE\" \\\n  \"$COPILOT_SELF_RELATIVE\" \\\n  \"$HOME\u002F.codex\u002Funderstand-anything\u002Funderstand-anything-plugin\" \\\n  \"$HOME\u002F.opencode\u002Funderstand-anything\u002Funderstand-anything-plugin\" \\\n  \"$HOME\u002F.pi\u002Funderstand-anything\u002Funderstand-anything-plugin\" \\\n  \"$HOME\u002Funderstand-anything\u002Funderstand-anything-plugin\"; do\n  if [ -n \"$candidate\" ] && [ -f \"$candidate\u002Fpackage.json\" ] && [ -f \"$candidate\u002Fpnpm-workspace.yaml\" ]; then\n    PLUGIN_ROOT=\"$candidate\"\n    break\n  fi\ndone\n\nif [ -z \"$PLUGIN_ROOT\" ]; then\n  echo \"Error: Cannot find the understand-anything plugin root.\"\n  echo \"Checked:\"\n  echo \"  - ${CLAUDE_PLUGIN_ROOT:-\u003Cunset CLAUDE_PLUGIN_ROOT>}\"\n  echo \"  - $HOME\u002F.understand-anything-plugin\"\n  echo \"  - ${SELF_RELATIVE:-\u003Cunresolved path derived from ~\u002F.agents\u002Fskills\u002Funderstand-domain>}\"\n  echo \"  - ${COPILOT_SELF_RELATIVE:-\u003Cunresolved path derived from ~\u002F.copilot\u002Fskills\u002Funderstand-domain>}\"\n  echo \"  - $HOME\u002F.codex\u002Funderstand-anything\u002Funderstand-anything-plugin\"\n  echo \"  - $HOME\u002F.opencode\u002Funderstand-anything\u002Funderstand-anything-plugin\"\n  echo \"  - $HOME\u002F.pi\u002Funderstand-anything\u002Funderstand-anything-plugin\"\n  echo \"  - $HOME\u002Funderstand-anything\u002Funderstand-anything-plugin\"\n  echo \"Make sure the plugin is installed correctly.\"\n  exit 1\nfi\n```\n\nUse `$PLUGIN_ROOT` for every reference to agent definitions in subsequent phases.\n\n### Phase 1: Detect Existing Graph\n\n1. Check if `$PROJECT_ROOT\u002F.understand-anything\u002Fknowledge-graph.json` exists\n2. If it exists AND `--full` was NOT passed → proceed to Phase 3 (derive from graph)\n3. Otherwise → proceed to Phase 2 (lightweight scan)\n\n### Phase 2: Lightweight Scan (Path 1)\n\nThe preprocessing script does NOT produce a domain graph — it produces **raw material** (file tree, entry points, exports\u002Fimports) so the domain-analyzer agent can focus on the actual domain analysis instead of spending dozens of tool calls exploring the codebase. Think of it as a cheat sheet: cheap Python preprocessing → expensive LLM gets a clean, small input → better results for less cost.\n\n1. Run the preprocessing script bundled with this skill, passing `$PROJECT_ROOT` from Phase 0:\n   ```\n   python .\u002Fextract-domain-context.py \"$PROJECT_ROOT\"\n   ```\n   This outputs `$PROJECT_ROOT\u002F.understand-anything\u002Fintermediate\u002Fdomain-context.json` containing:\n   - File tree (respecting `.gitignore`)\n   - Detected entry points (HTTP routes, CLI commands, event handlers, cron jobs, exported handlers)\n   - File signatures (exports, imports per file)\n   - Code snippets for each entry point (signature + first few lines)\n   - Project metadata (package.json, README, etc.)\n2. Read the generated `domain-context.json` as context for Phase 4\n3. Proceed to Phase 4\n\n### Phase 3: Derive from Existing Graph (Path 2)\n\n1. Read `$PROJECT_ROOT\u002F.understand-anything\u002Fknowledge-graph.json`\n2. Format the graph data as structured context:\n   - All nodes with their types, names, summaries, and tags\n   - All edges with their types (especially `calls`, `imports`, `contains`)\n   - All layers with their descriptions\n   - Tour steps if available\n3. This is the context for the domain analyzer — no file reading needed\n4. Proceed to Phase 4\n\n### Phase 4: Domain Analysis\n\n1. Read the domain-analyzer agent prompt from `$PLUGIN_ROOT\u002Fagents\u002Fdomain-analyzer.md`\n2. Dispatch a subagent with the domain-analyzer prompt + the context from Phase 2 or 3\n3. The agent writes its output to `$PROJECT_ROOT\u002F.understand-anything\u002Fintermediate\u002Fdomain-analysis.json`\n\n### Phase 5: Validate and Save\n\n1. Read the domain analysis output\n2. Validate using the standard graph validation pipeline (the schema now supports domain\u002Fflow\u002Fstep types)\n3. If validation fails, log warnings but save what's valid (error tolerance)\n4. Save to `$PROJECT_ROOT\u002F.understand-anything\u002Fdomain-graph.json`\n5. Clean up `$PROJECT_ROOT\u002F.understand-anything\u002Fintermediate\u002Fdomain-analysis.json` and `$PROJECT_ROOT\u002F.understand-anything\u002Fintermediate\u002Fdomain-context.json`\n\n### Phase 6: Launch Dashboard\n\n1. Auto-trigger `\u002Funderstand-dashboard` to visualize the domain graph\n2. The dashboard will detect `domain-graph.json` and show the domain view by default\n","# \u002Funderstand-domain\n\nExtracts business domain knowledge — domains, business flows, and process steps — from a codebase and produces an interactive horizontal flow graph in the dashboard.\n\n## How It Works\n\n- If a knowledge graph already exists (`.understand-anything\u002Fknowledge-graph.json`), derives domain knowledge from it (cheap, no file scanning)\n- If no knowledge graph exists, performs a lightweight scan: file tree + entry point detection + sampled files\n- Use `--full` flag to force a fresh scan even if a knowledge graph exists\n\n## Instructions\n\n### Phase 0: Resolve `PROJECT_ROOT`\n\nSet `PROJECT_ROOT` to the current working directory.\n\n**Worktree redirect.** If `PROJECT_ROOT` is inside a git worktree (not the main checkout), redirect output to the main repository root. Worktrees managed by Claude Code are ephemeral — `.understand-anything\u002F` written there is destroyed when the session ends, taking the domain graph with it (issue #133). Detect a worktree by comparing `git rev-parse --git-dir` against `git rev-parse --git-common-dir`; in a normal checkout or submodule they resolve to the same path, in a worktree they differ and the parent of `--git-common-dir` is the main repo root.\n\n```bash\nCOMMON_DIR=$(git -C \"$PROJECT_ROOT\" rev-parse --git-common-dir 2>\u002Fdev\u002Fnull)\nGIT_DIR=$(git -C \"$PROJECT_ROOT\" rev-parse --git-dir 2>\u002Fdev\u002Fnull)\nif [ -n \"$COMMON_DIR\" ] && [ -n \"$GIT_DIR\" ]; then\n  COMMON_ABS=$(cd \"$PROJECT_ROOT\" && cd \"$COMMON_DIR\" 2>\u002Fdev\u002Fnull && pwd -P)\n  GIT_ABS=$(cd \"$PROJECT_ROOT\" && cd \"$GIT_DIR\" 2>\u002Fdev\u002Fnull && pwd -P)\n  if [ -n \"$COMMON_ABS\" ] && [ \"$COMMON_ABS\" != \"$GIT_ABS\" ]; then\n    MAIN_ROOT=$(dirname \"$COMMON_ABS\")\n    if [ -d \"$MAIN_ROOT\" ] && [ \"${UNDERSTAND_NO_WORKTREE_REDIRECT:-0}\" != \"1\" ]; then\n      echo \"[understand-domain] Detected git worktree at $PROJECT_ROOT\"\n      echo \"[understand-domain] Redirecting output to main repo root: $MAIN_ROOT\"\n      echo \"[understand-domain] (Set UNDERSTAND_NO_WORKTREE_REDIRECT=1 to keep PROJECT_ROOT as the worktree.)\"\n      PROJECT_ROOT=\"$MAIN_ROOT\"\n    fi\n  fi\nfi\n```\n\nUse `$PROJECT_ROOT` (not the bare CWD) for every reference to \"the current project\" \u002F `\u003Cproject-root>` in subsequent phases.\n\n**Important:** do **not** assume the plugin root is simply two directories above the skill path string. In many installations `~\u002F.agents\u002Fskills\u002Funderstand-domain` is a symlink into the real plugin checkout. Prefer runtime-provided plugin roots first (for Claude), then fall back to universal symlinks, skill symlink resolution, and common clone-based install paths.\n\nResolve the plugin root like this:\n\n```bash\nSKILL_REAL=$(realpath ~\u002F.agents\u002Fskills\u002Funderstand-domain 2>\u002Fdev\u002Fnull || readlink -f ~\u002F.agents\u002Fskills\u002Funderstand-domain 2>\u002Fdev\u002Fnull || echo \"\")\nSELF_RELATIVE=$([ -n \"$SKILL_REAL\" ] && cd \"$SKILL_REAL\u002F..\u002F..\" 2>\u002Fdev\u002Fnull && pwd || echo \"\")\nCOPILOT_SKILL_REAL=$(realpath ~\u002F.copilot\u002Fskills\u002Funderstand-domain 2>\u002Fdev\u002Fnull || readlink -f ~\u002F.copilot\u002Fskills\u002Funderstand-domain 2>\u002Fdev\u002Fnull || echo \"\")\nCOPILOT_SELF_RELATIVE=$([ -n \"$COPILOT_SKILL_REAL\" ] && cd \"$COPILOT_SKILL_REAL\u002F..\u002F..\" 2>\u002Fdev\u002Fnull && pwd || echo \"\")\n\nPLUGIN_ROOT=\"\"\nfor candidate in \\\n  \"${CLAUDE_PLUGIN_ROOT}\" \\\n  \"$HOME\u002F.understand-anything-plugin\" \\\n  \"$SELF_RELATIVE\" \\\n  \"$COPILOT_SELF_RELATIVE\" \\\n  \"$HOME\u002F.codex\u002Funderstand-anything\u002Funderstand-anything-plugin\" \\\n  \"$HOME\u002F.opencode\u002Funderstand-anything\u002Funderstand-anything-plugin\" \\\n  \"$HOME\u002F.pi\u002Funderstand-anything\u002Funderstand-anything-plugin\" \\\n  \"$HOME\u002Funderstand-anything\u002Funderstand-anything-plugin\"; do\n  if [ -n \"$candidate\" ] && [ -f \"$candidate\u002Fpackage.json\" ] && [ -f \"$candidate\u002Fpnpm-workspace.yaml\" ]; then\n    PLUGIN_ROOT=\"$candidate\"\n    break\n  fi\ndone\n\nif [ -z \"$PLUGIN_ROOT\" ]; then\n  echo \"Error: Cannot find the understand-anything plugin root.\"\n  echo \"Checked:\"\n  echo \"  - ${CLAUDE_PLUGIN_ROOT:-\u003Cunset CLAUDE_PLUGIN_ROOT>}\"\n  echo \"  - $HOME\u002F.understand-anything-plugin\"\n  echo \"  - ${SELF_RELATIVE:-\u003Cunresolved path derived from ~\u002F.agents\u002Fskills\u002Funderstand-domain>}\"\n  echo \"  - ${COPILOT_SELF_RELATIVE:-\u003Cunresolved path derived from ~\u002F.copilot\u002Fskills\u002Funderstand-domain>}\"\n  echo \"  - $HOME\u002F.codex\u002Funderstand-anything\u002Funderstand-anything-plugin\"\n  echo \"  - $HOME\u002F.opencode\u002Funderstand-anything\u002Funderstand-anything-plugin\"\n  echo \"  - $HOME\u002F.pi\u002Funderstand-anything\u002Funderstand-anything-plugin\"\n  echo \"  - $HOME\u002Funderstand-anything\u002Funderstand-anything-plugin\"\n  echo \"Make sure the plugin is installed correctly.\"\n  exit 1\nfi\n```\n\nUse `$PLUGIN_ROOT` for every reference to agent definitions in subsequent phases.\n\n### Phase 1: Detect Existing Graph\n\n1. Check if `$PROJECT_ROOT\u002F.understand-anything\u002Fknowledge-graph.json` exists\n2. If it exists AND `--full` was NOT passed → proceed to Phase 3 (derive from graph)\n3. Otherwise → proceed to Phase 2 (lightweight scan)\n\n### Phase 2: Lightweight Scan (Path 1)\n\nThe preprocessing script does NOT produce a domain graph — it produces **raw material** (file tree, entry points, exports\u002Fimports) so the domain-analyzer agent can focus on the actual domain analysis instead of spending dozens of tool calls exploring the codebase. Think of it as a cheat sheet: cheap Python preprocessing → expensive LLM gets a clean, small input → better results for less cost.\n\n1. Run the preprocessing script bundled with this skill, passing `$PROJECT_ROOT` from Phase 0:\n   ```\n   python .\u002Fextract-domain-context.py \"$PROJECT_ROOT\"\n   ```\n   This outputs `$PROJECT_ROOT\u002F.understand-anything\u002Fintermediate\u002Fdomain-context.json` containing:\n   - File tree (respecting `.gitignore`)\n   - Detected entry points (HTTP routes, CLI commands, event handlers, cron jobs, exported handlers)\n   - File signatures (exports, imports per file)\n   - Code snippets for each entry point (signature + first few lines)\n   - Project metadata (package.json, README, etc.)\n2. Read the generated `domain-context.json` as context for Phase 4\n3. Proceed to Phase 4\n\n### Phase 3: Derive from Existing Graph (Path 2)\n\n1. Read `$PROJECT_ROOT\u002F.understand-anything\u002Fknowledge-graph.json`\n2. Format the graph data as structured context:\n   - All nodes with their types, names, summaries, and tags\n   - All edges with their types (especially `calls`, `imports`, `contains`)\n   - All layers with their descriptions\n   - Tour steps if available\n3. This is the context for the domain analyzer — no file reading needed\n4. Proceed to Phase 4\n\n### Phase 4: Domain Analysis\n\n1. Read the domain-analyzer agent prompt from `$PLUGIN_ROOT\u002Fagents\u002Fdomain-analyzer.md`\n2. Dispatch a subagent with the domain-analyzer prompt + the context from Phase 2 or 3\n3. The agent writes its output to `$PROJECT_ROOT\u002F.understand-anything\u002Fintermediate\u002Fdomain-analysis.json`\n\n### Phase 5: Validate and Save\n\n1. Read the domain analysis output\n2. Validate using the standard graph validation pipeline (the schema now supports domain\u002Fflow\u002Fstep types)\n3. If validation fails, log warnings but save what's valid (error tolerance)\n4. Save to `$PROJECT_ROOT\u002F.understand-anything\u002Fdomain-graph.json`\n5. Clean up `$PROJECT_ROOT\u002F.understand-anything\u002Fintermediate\u002Fdomain-analysis.json` and `$PROJECT_ROOT\u002F.understand-anything\u002Fintermediate\u002Fdomain-context.json`\n\n### Phase 6: Launch Dashboard\n\n1. Auto-trigger `\u002Funderstand-dashboard` to visualize the domain graph\n2. The dashboard will detect `domain-graph.json` and show the domain view by default\n",{"name":5,"description":7,"argument-hint":24},[25],"--full","main","14d19341a5ae6e5a3c751328fcc273395da5bd21",".claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-domain","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun","https:\u002F\u002Fgithub.com\u002FIkeu-1030","Action shatters illusion\u002F","2026-07-02 15:19:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Ikeu-1030\u002FiRun --skill understand-domain",{"tool":39,"command":40},"bunx","bunx skills add Ikeu-1030\u002FiRun --skill understand-domain",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Ikeu-1030\u002FiRun --skill understand-domain","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-domain\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"extract-domain-context.py","SCRIPT","脚本",15888,"https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-domain\u002Fextract-domain-context.py",[54,61,68,75,82,89],{"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},"01M756NR65N494G30JZP84MS7R","understand","Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand\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},"01M756NPH7BMV8655NPXER0ZAS","understand-onboard","Use when you need to generate an onboarding guide for new team members joining a project","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-onboard\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},"01M756NM7K2DP7KD475N4S3ZXD","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\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-knowledge\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},"01M756NJPJADZ13YRP1D9PEVEF","understand-explain","Use when you need a deep-dive explanation of a specific file, function, or module in the codebase","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-explain\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},"01M756NCF0HHCSJTMDV85G7KR2","understand-diff","Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-diff\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M756NA0ZYHV493C2DHEGG1TF","understand-dashboard","Launch the interactive web dashboard to visualize a codebase's knowledge graph","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-dashboard\u002FSKILL.md",[],[]]