Universo-specific complement to the OntoIndex code-intelligence tool. Use alongside the generated `.claude/skills/ontoindex/*` skills when querying the code graph in this monorepo. Adds the three things those generated skills do NOT cover — the namespace-collision caveat (this is code intelligence over source, NOT OWL/RDF/SPARQL), this repo's pnpm wrapper and golden queries, and the SQL-first edge-quality limitation.
Use when the user needs to run OntoIndex CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
Use when the user asks about OntoIndex itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What OntoIndex tools are available?", "How do I use OntoIndex?"
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"
Use when working with the PlayCanvas Editor API, realtime sync protocols, WebSocket endpoints, ShareDB, Operational Transformation (OT), or document collections.