From understand-anything
Generates markdown onboarding guide from project's knowledge graph for new team members: overview, architecture layers, guided tour, file map, complexity hotspots.
npx claudepluginhub lum1104/understand-anything --plugin understand-anythingThis skill uses the workspace's default tool permissions.
Generate a comprehensive onboarding guide from the project's knowledge graph.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Generate a comprehensive onboarding guide from the project's knowledge graph.
The knowledge graph JSON has this structure:
project — {name, description, languages, frameworks, analyzedAt, gitCommitHash}nodes[] — each has {id, type, name, filePath, summary, tags[], complexity, languageNotes?}
file:path, function:path:name, class:path:nameedges[] — each has {source, target, type, direction, weight}
layers[] — each has {id, name, description, nodeIds[]}tour[] — each has {order, title, description, nodeIds[]}Check that .understand-anything/knowledge-graph.json exists. If not, tell the user to run /understand first.
Read project metadata — use Grep or Read with a line limit to extract the "project" section (name, description, languages, frameworks).
Read layers — Grep for "layers" to get the full layers array. These define the architecture and will structure the guide.
Read the tour — Grep for "tour" to get the guided walkthrough steps. These provide the recommended learning path.
Read file-level nodes only — use Grep to find nodes with "type": "file" in the knowledge graph. Skip function-level and class-level nodes to keep the guide high-level. Extract each file node's name, filePath, summary, and complexity.
Identify complexity hotspots — from the file-level nodes, find those with the highest complexity values. These are areas new developers should approach carefully.
Generate the onboarding guide with these sections:
Format as clean markdown
Offer to save the guide to docs/ONBOARDING.md in the project
Suggest the user commit it to the repo for the team