Use when starting any conversation in Trae - establishes mandatory skill activation, Trae tool mapping, and workflow priority before any response or action
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when executing implementation plans with independent tasks in the current session
Use when you have a spec or requirements for a multi-step task, before touching code
Use when tests have arbitrary sleeps/timeouts, race conditions, flaky async behavior, or timing-dependent failures
Use after finding a root cause when adding validation at multiple layers would make the bug impossible or obvious
Use when a bug manifests deep in a stack and you need to trace backward to the original trigger
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code