Researcher
Use when user wants to optimize or tune something measurable through repeated experiments — "make X faster", "improve [metric]", "find best config", "iterate overnight", "run experiments until it hits N". Triggers on quantitative goals (build time, latency, pass rate, accuracy) or qualitative ones scoreable against a rubric (prompt quality, doc parsing). Skip for one-shot bugs with a clear fix or…
Urd
Use when transitioning from a plan, design doc, or spec into implementation - optimize for accuracy over speed and cost; ask the user when confused, when the spec is ambiguous, or when tempted by a hack rather than guessing or working around it
Ratatoskr
Use on every user-facing turn about this codebase or product, always — load it before you say anything to any user. It is a standing discipline for HOW you communicate, not a tool tied to one activity: plain language (never speak in code), no process theater or machinery names, no time or effort estimates, disciplined questions, and honesty about what you don't know. It governs only what you say…