Run an author agent and a reviewer agent in a loop with a strict finding format, a mandatory verification pass, and a convergence rule that ends it.
Choose between processes, threads, and asynchronous concurrency based on isolation, memory sharing, and failure behaviour. Use when deciding how to run work concurrently.
Have agents argue opposing positions from the same evidence, then synthesize, so the strongest case for each option is heard before deciding.
Operate as a mobile engineer who plans around release trains, a real device matrix, and app-store rules that a web engineer never faces.
Model UI as explicit finite states so impossible combinations cannot render. Use when a component juggles interacting booleans, shows contradictory states, or a flow has grown too…
Predict when current capacity will be exhausted and plan the increase before it becomes an incident. Use when growth is steady enough to plan for or when scaling events surprise…
Build self-serve documentation that answers questions before they become tickets, organised by what people search for. Use when the same questions arrive repeatedly.
Read code metrics as smoke that points at where to look, not as verdicts that rank code good or bad. Use when triaging a large codebase for refactoring targets or reviewing…
Operate as a principal architect who owns the boundaries between systems, curates the technology set, and spends veto power sparingly.
Cut startup latency by deferring heavy imports, precompiling ahead of time, and pruning the dependency tree that loads before first useful work.
Read a profit and loss, balance sheet, and cash flow statement well enough to see what a business is actually doing.
Test an MCP server for protocol conformance, tool selection accuracy, and behaviour under real model calls rather than only unit tests.
Manage specificity with layers, :where, and low-specificity selectors so overrides stay predictable. Use when styles fight each other, !important spreads, or you are setting…