Audit and harden this Rust repo (code-graph-mcp) for Windows correctness: path-spelling drift between producers, the 32,767-char command-line cap, index-key mismatches, and path predicates that assume one ecosystem's layout. Use whenever touching code that builds, compares, prints, or stores a filesystem path; that…
Build, view, update, and navigate a project's call graph as GEML codemap documents. Use when asked to see/update/build a project's code graph or codemap (看下/更新下 code-graph), when asked "who calls X" / "what does X call" / to trace a call chain or impact path, or whenever a .geml-code-graph/ directory with index.geml…
Address a document by its BLOCKS instead of reading it whole. Use for any long Markdown or documentation file — README, spec, guide, design doc, changelog — when the job is to find where something is documented, read one section, or change one section: geml list, geml find and geml get read Markdown directly and hand…
Address a document by its BLOCKS instead of reading it whole. Use for any long Markdown or documentation file — README, spec, guide, design doc, changelog — when the job is to find where something is documented, read one section, or change one section: geml list, geml find and geml get read Markdown directly and hand…
Use bonsai-ninja as compiler-backed structural evidence when mapping a codebase, finding symbols, tracing behavior, inspecting dataflow, debugging across files, reviewing change impact, exporting graph facts, or running SAST.
Use to enable and operate rag-rat's optional AI memory-maintenance passes — the dream --verify / --compact model turns that verify repo memories (flag claims that no longer hold) and compact them (shorter summaries). Off by default. This configures [llm.dream] / [llm.dream.remote] (a chat model, over a Connect…
Apply rag-rat's Rust style when writing or reviewing Rust: current stable idioms, module-qualified free functions and constants, explicit persistence contracts, and narrow APIs.
Use when working in a repository indexed by rag-rat (a rag-rat.toml at the root and a rag-rat MCP server available). Establishes the working rule: reach for the rag-rat MCP tools (semanticsearch, symbollookup, impactsurface, findcallers/tracecallees, repobrief, importantsymbols) to FIND and UNDERSTAND code before…
Use before searching, reading, or editing files in this repo (or any repo with a "calm" MCP server), or whenever unsure which CALM tool fits — a self-triggerable orientation to the CALM Stage 1-8 tool workflow (repooverview → locate → source → callers → editcontext → editsymbol/editlines → diffimpact →…
Test codeweave-mcp tools against any project using TestHarness. Use this whenever verifying tool behavior, testing a code change, or running custom assertions — e.g. "test the harness", "run tests against X project", "does semanticsearch work correctly".
Start dekko's background daemon before a session that will run many bare dekko CLI commands via Bash (not the MCP tools) against a large or medium repo. Trigger when you're about to run several dekko CLI invocations in a row on the same repo — a long refactor loop, a batch of query/search/outline calls, or a…
Read and write dekko's symbol-anchored notes in any repo with a .dekko/ directory. Trigger every time you pull a symbol's context (querysymbol, getcontextpack, dekko query/context), right after a non-obvious change, and right after any rename/move/signature edit (to sweep orphaned notes). Notes are durable, committed…
Use dekko's tools instead of grep/Read whenever a repo has a .dekko/ directory — not just at session start. Trigger on any "find/locate/understand this symbol," "what does this file/dir contain," "what will this change break," or "read this file" impulse. dekko has already parsed and indexed the repo; grepping or…
Use when the user asks "what breaks if I change X", "blast radius of modifying method Y", "what tests do I need to run if I change class Z", "impact analysis for refactoring X", or wants to understand the downstream consequences of a code change before making it. Uses Orihime MCP tools only — no source file reads…
Use when the user asks for a code review focused on class structure, design patterns, OOP principles, or architecture quality. Reviews whether GoF/SOLID design patterns are properly applied, flags misapplications and missing patterns, suggests splitting bloated classes/methods, and recommends fortifying weak…
Use when the user asks "run a security audit on X", "find SQL injection risks", "check taint paths", "any OWASP issues in repo X", "find injection vulnerabilities", "check license compliance", or wants to understand what untrusted input can reach dangerous sinks in a codebase. Uses Orihime MCP tools only — no source…
Cut and publish a codeweb release end-to-end — prep the version/changelog file ecosystem, land it on main, push the vX.Y.Z tag, and let the tag-triggered workflow publish the GitHub Release. Use when asked to "cut a release", "tag a release", "publish vX.Y.Z", "do the release", or "ship version X".