arena

Design types, signatures, and module boundaries before code.

Use when saving unfinished work for a new session or approaching a context limit.

Review design, contract fidelity, and adversarial risks without repeating verified mechanical checks.

Resolve decisions through evidence, investigation, and a structured design tree.

Investigate an observable question with evidence before proposing changes.

Route development work through principles, capabilities, and verified delivery.

Apply when running a benchmark or reporting a measured speedup or regression, including performance comparisons between libraries or configurations.

Use when reading or changing GitHub resources.

Configure portable project context, tracking, delivery, and domain documentation for dev-cycle.

Choose project coding policy, dependencies, or external APIs when a decision is unresolved.

Test a skill change blind with organic tasks, parallel candidates, and one judge.

Improve one metric through measured keep-or-revert iterations.