How and when to delegate work to subagents via the `subagent` tool (Explore, Plan, General). Use when a task involves codebase recon, implementation planning, or actual code changes that would benefit from an isolated context window instead of doing it all inline.
Manage MCP servers in Nuxt with @nuxtjs/mcp-toolkit — setup, create tools/resources/prompts, organize with handlers, build interactive MCP Apps, add elicitation/logging/sessions, review, and troubleshoot.
Use when creating, editing, validating, or running agent-qa tests, suites, or hooks. Prefer agent-qa MCP tools, enforce canonical agent-qa IDs, and use the bundled schema reference to avoid hallucinated config keys or YAML fields.
Build 5-level compaction tree (daily/weekly/monthly/root) with smart thresholds and fixed/tentative lifecycle. Run at session start when triggers are met, or via external scheduler.
3-tier agent memory system with 5-level compaction tree. Codex CLI version. Defines session start protocol, end-of-task checkpoints, and memory file management. MUST be followed every session.
Manual memory flush: dump current session context to daily raw log via subagent. Invoke with /hipocampus:flush. Run hipocampus:compaction afterwards for tree propagation and qmd reindex.
Orchestrator playbook and routing rules for Ringer, the verified-swarm delegation tool (ringer.py). TRIGGER — load BEFORE acting, not after — whenever: you are about to run ANY script or command that calls a model or drives a conversational/eval harness (probe, smoke test, simulation, grader, persona conversation) outside a live Ringer run; you are about to start an edit→test→edit loop or a batch of similar edits across files; you are about to do a "quick check" that spawns a model or a CLI agent; you are reviewing or diagnosing failed worker or model output; you catch yourself thinking a task is "small enough to just do myself" — that thought IS the trigger (a single task is a one-task manifest); or you are writing or reviewing a manifest, choosing a swarm pattern (review swarm, fix swarm, focus group, bakeoff, research-with-proof), picking a worker engine, or debugging a failed run. SKIP only for: reading or searching files, git operations, a one-file few-line ONE-SHOT edit (once — if you are back for a second pass, that is a loop: TRIGGER), authoring prose/specs/docs straight from your own context, or pure conversation.