Use when writing or reviewing Python 3.14+ with strict type-safety enforced: generics with PEP 695 syntax, annotationlib / deferred annotations, Protocol vs ABC, ParamSpec decorators, TypeIs / TypeGuard narrowing, TypedDict / ReadOnly, magic strings / numbers vs Literal / StrEnum / Final, NewType vs aliases, or any time mypy / pyright / pyrefly / ty is configured, run, or failing.
Use when writing or reviewing TypeScript 6.0+ with strict type-safety: tsconfig defaults and deprecations, explicit global types, rootDir / paths / moduleResolution, import attributes, generics with T-prefix names, branded types, discriminated unions with `never` exhaustiveness, Result types, magic strings / numbers vs literal unions and named constants, Zod boundaries, `satisfies`, assertion functions, inferred type predicates, `using`, standard decorators, `unknown` vs `any`, or `// @ts-expect-error`.
Use when reviewing code for maintainability issues such as coupling, cohesion, abstraction leaks, boundary drift, code smells, naming problems, duplicated logic, premature generalization, or design-pattern misuse.
Use when producing or consuming structured code review findings. Defines the shared output contract, severity rubric, finding schema, per-specialist report shape, and final aggregated report shape that all reviewer specialist agents must follow and the verifier agent enforces.
Always use when user asks to create, generate, draw, or design a diagram, flowchart, architecture diagram, ER diagram, sequence diagram, class diagram, network diagram, mockup, wireframe, or UI sketch, or mentions draw.io, drawio, drawoi, .drawio files, or diagram export to PNG/SVG/PDF.
Use when the user is entering unfamiliar territory — a new area of the codebase, a new domain, tool, or problem space — or is about to scope substantial work in one, and the gap between what they asked for and what the territory actually demands is likely to be large. Also use when the user asks what they are missing, says they don't know what good looks like, or wants help prompting better before delegating work.
Generate standalone HTML + inline-SVG technical diagrams that come out format-clean every time — text that always fits its box, arrows that actually connect, no overlaps, no drift. Works by planning a coordinate grid first and sizing every box with monospace arithmetic instead of guessing pixels, then self-checking the geometry before delivery. Output is a single self-contained .html file (no build step, no dependencies) that opens in any browser.
Use when reviewing code for logic errors, type-safety violations, null/undefined handling, off-by-one, race conditions, incorrect API usage, broken contracts, missing error handling, edge-case gaps, or state-management bugs.