mastersrunners

Use when reviewing API or database changes for contracts, auth/authz, validation, integrity, and failure handling.

Use when reviewing documentation changes for clarity, structure, source-of-truth alignment, and cross-reference quality.

Use when reviewing web changes for routing, auth gating, state ownership, loading/error handling, and accessibility basics.

Use when reviewing task, CI, script, or repository workflow changes for invariant safety and maintainability.

Use when performing the final product review for user value, acceptance criteria, scope fit, and rollout risk.

Use when writing specialist or PO review results so the output follows the repository review artifact contract.

Use when reviewing user-facing changes for interaction flow, copy, hierarchy, and product tone.

Use when reviewing API or database changes for contracts, auth/authz, validation, integrity, and failure handling.

Use when reviewing documentation changes for clarity, structure, source-of-truth alignment, and cross-reference quality.

Use when reviewing web changes for routing, auth gating, state ownership, loading/error handling, and accessibility basics.

Use when reviewing task, CI, script, or repository workflow changes for invariant safety and maintainability.

Use when performing the final product review for user value, acceptance criteria, scope fit, and rollout risk.

Use when writing specialist or PO review results so the output follows the repository review artifact contract.

Use when reviewing user-facing changes for interaction flow, copy, hierarchy, and product tone.