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---
- 2name: dev-prod-parity-rule
- 3description: Add a rule to the project's CLAUDE.md that keeps development and production behaving the same, and records every unavoidable difference. Use when setting up a project or after a bug that only happened in production.
- 4---
- 6# Dev and production parity rule
- 81. Read the project's `CLAUDE.md` (create it at the repo root if there is none).
- 92. Add the "Dev and production parity" section from this kit's `CLAUDE.md`, unless an equivalent rule is already there.
- 103. If the project has a deploy guide, add an empty "Dev and production differences" table to it (what differs, why, how to run the production behavior locally), and fill in any differences you can see today, such as `NODE_ENV` checks.
- 114. Show the person the change before saving it.