Cross-project research workflow for cix workspaces in Claude Cowork. Use when a request spans multiple repositories — "wire feature X through the platform", "add Y across the services", "change Z in production/staging", "how does this work end-to-end across repos". Uses cixworkspacesearch to find which repos are in…
Semantic code search and navigation across repositories indexed by a cix server, via the cix MCP tools. Use when finding code by meaning rather than exact strings — "find the authentication middleware", "where is X defined?", "what calls this function?", "how does Y work in this codebase?", "search the codebase for…
Execute written implementation plan whose Tasks edit code, per-Task SAFE/CAUTION/UNSAFE git-signal verdict before edit AND code-style cascade for code-generation Tasks (style from silo authors, strategy+template from proven neighbors). Triggers on "execute the plan", "start Task N", "выполни план", "начни задачу"…
Assess project/domain health — scan risk zones across dimensions (bugs, hotspots, tech debt). Use when asked evaluate risks, find problematic areas, assess code health, identify zones needing attention — NOT for specific bug symptoms (use bug-hunt instead).
Audit a PR's structural choices against architecture-priming, the repo's own architecture.md, and any nested boundary configs. Use when the user says "audit this PR's architecture", "check the boundaries", "is this PR clean structurally", "post-merge review of.
Voice, tone, and format for the public Codemap docs (apps/docs, built with Blume). Use when authoring or editing apps/docs prose — landing, guides, concepts, recipes, reference, generated API — or deciding headline grammar, benefit framing, peer framing, or anti-pitch wording.
Find deepening opportunities in the codebase, informed by the domain language in docs/glossary.md and the architecture in docs/architecture.md. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Generate a complete project index with per-module README files for efficient code navigation. Use when starting work on a new project or after major restructuring. Run once per project.
Use when reviewing a diff, PR, or set of changes — your own or someone else's. Applies a severe-senior-engineer review checklist (root cause vs. symptom, unrequested abstractions, missing tests/checks, unverified claims) instead of a superficial pass.
Use when Jambavan MCP tools (jambavanindex, jambavancontext, jambavanmemory) are available in the current session, or when you see .jambavan/ in the project root.
Activate Vibhishana Niti — a severe senior-engineer discipline for shipping the minimum correct change. Use when the user asks for the smallest/simplest fix, a minimal diff, root-cause (not symptom) fixes, when a request seems larger than needed, or when they say "vibhishana niti". Deactivate when they say "normal…