.cursor/skills/ui-web-explorer/SKILL.md
Vite/React UI for LaightDB: dashboard, search, and the 3D Explorer (/explorer) for context graphs and storage engine layout. Use when editing ui/src, Vite config, or REST client calls for graph overview / storage diagnostics.
npx skillsauth add gtrig/LaightDB ui-web-explorerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
ui/src/main.tsx, routes in ui/src/App.tsx.ui/src/api.ts — includes getGraphOverview(), getStorageDiagnostics().ui/src/types.ts — GraphOverview, StorageDiagnostics, etc.ui/src/components/StorageExplorer3D.tsx — tabs for Context Graph (force layout) and Engine Layout (WAL / memtable / SST blocks).| Purpose | Method | Path |
|---------|--------|------|
| Bulk graph for 3D mindmap | GET | /v1/graph/overview?collection=&limit= |
| WAL / SST sizes | GET | /v1/storage/diagnostics |
:8080).cd ui && npm run dev — requests to /v1 proxy to the API.Do not add Go dependencies for UI work; npm deps belong in ui/package.json with project approval.
tools
Proactively loads relevant LaightDB context at the start of substantive work and persists concise rolling notes before wrapping up, using LaightDB MCP tools without waiting for the user to say "store" or "search". Use whenever this workspace has the LaightDB MCP server enabled and the user is doing multi-step implementation, debugging, or design that should survive across sessions.
tools
Build MCP servers using the official Go SDK (github.com/modelcontextprotocol/go-sdk/mcp). Use when implementing MCP tools, resources, server setup, transport configuration, or anything in internal/mcp/.
development
Build an LSM-tree storage engine in Go with WAL, MemTable, SSTables, bloom filters, and compaction. Use when implementing or modifying internal/storage/ components, writing the WAL, MemTable, SSTable, compaction, or the storage engine orchestrator.
tools
Proactively loads relevant LaightDB context at the start of substantive work and persists concise rolling notes before wrapping up, using LaightDB MCP tools without waiting for the user to say "store" or "search". Use whenever this workspace has the LaightDB MCP server enabled and the user is doing multi-step implementation, debugging, or design that should survive across sessions.