> understand-dashboard
Launch the interactive web dashboard to visualize a codebase's knowledge graph
curl "https://skillshub.wtf/Lum1104/Understand-Anything/understand-dashboard?format=md"/understand-dashboard
Start the Understand Anything dashboard to visualize the knowledge graph for the current project.
Instructions
-
Determine the project directory:
- If
$ARGUMENTScontains a path, use that as the project directory - Otherwise, use the current working directory
- If
-
Check that
.understand-anything/knowledge-graph.jsonexists in the project directory. If not, tell the user:No knowledge graph found. Run /understand first to analyze this project. -
Find the dashboard code. The dashboard is at
packages/dashboard/relative to this plugin's root directory. Use the Bash tool to resolve the path:PLUGIN_ROOT="$(cd "$(dirname "$0")/../.." && pwd)"Or locate it by checking these paths in order:
${CLAUDE_PLUGIN_ROOT}/packages/dashboard/- The parent directory of this skill file, then
../../packages/dashboard/
-
Install dependencies if needed:
cd <dashboard-dir> && pnpm install --frozen-lockfile 2>/dev/null || pnpm install -
Start the Vite dev server pointing at the project's knowledge graph:
cd <dashboard-dir> && GRAPH_DIR=<project-dir> npx vite --openRun this in the background so the user can continue working.
-
Report to the user:
Dashboard started at http://localhost:5173 Viewing: <project-dir>/.understand-anything/knowledge-graph.json The dashboard is running in the background. Press Ctrl+C in the terminal to stop it.
Notes
- The dashboard auto-opens in the default browser via
--open - If port 5173 is already in use, Vite will pick the next available port
- The
GRAPH_DIRenvironment variable tells the dashboard where to find the knowledge graph
> related_skills --same-repo
> understand
Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships
> understand-onboard
Use when you need to generate an onboarding guide for new team members joining a project
> understand-explain
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase
> understand-diff
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks