[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FDCF286PSFJTZKEEWNP523":3,"skill-same:01M7FDCF286PSFJTZKEEWNP523":48},{"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":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7FDCF286PSFJTZKEEWNP523","understand-explain",null,"Use when you need a deep-dive explanation of a specific file, function, or module in the codebase","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fresearch-docs\u002Fskills\u002Funderstand-explain\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fresearch-docs\u002Fskills\u002Funderstand-explain",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add siddu1004\u002FSFP --skill understand-explain",{"tool":40,"command":41},"bunx","bunx skills add siddu1004\u002FSFP --skill understand-explain",{"tool":43,"command":44},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill understand-explain","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fresearch-docs\u002Fskills\u002Funderstand-explain\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"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},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\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},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\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},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\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},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\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},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]