Made by@slashcloneDev prod parity rule
@slashclone/dev-prod-parity-rule
A CLAUDE.md rule that keeps development and production behaving the same: prefer explicit environment flags over NODE_ENV checks, and write down every unavoidable difference in the deploy guide in the same change.
CLAUDE.mdDevOpsv0.1.0 (latest)
- Activity
- New: be the first to try it
- Installs
- 0 installs
- Likes
- 0 likes
- Clones
- 0 clones
- 1## Dev and production parity
- 3- Development and production behave the same. Bugs that only happen in production are the expensive kind.
- 4- Prefer an explicit environment flag (for example `FEATURE_X=off`) over checking `NODE_ENV`, so a behavior can be turned on or off the same way everywhere.
- 5- When a difference cannot be avoided (local file storage, a test mail sink, relaxed rate limits), document it in the deploy guide, in a "Dev and production differences" table: what differs, why, and how to run the production behavior locally. Do it in the same change that adds the difference.
- 6- Before finishing a task that touches configuration, search for new `NODE_ENV` checks and either replace them with a flag or add them to the table.