| name | production-hardening |
| description | Prepare a selected implementation for production by auditing risk, accessibility, failure handling, security, performance, observability, cleanup, and verification. Use only when explicitly invoked after exploration or implementation; do not trigger during lightweight design iteration. |
Production Hardening
Instructions
- Establish the selected behavior and inspect the current diff before changing it.
- Remove dead variants, debug affordances, temporary data, and experiment-only code.
- Review accessibility, loading and empty states, failures, cancellation, concurrency, platform behavior, and localization where relevant.
- Review data exposure, authorization, secrets, production mutations, and observability where relevant.
- Add or improve tests according to regression impact; do not force a test-first rewrite of completed code.
- Run focused checks, then the repository's broader release-relevant checks.
- Report what is production-ready, what remains risky, and any release action still requiring approval.
Do not deploy, push, open a PR, or mutate production systems without explicit authorization.
