Stop bugs that only happen in production
A CLAUDE.md rule that stops bugs that only show up in production by keeping development and production behaving the same. Your agent prefers explicit env flags over NODE_ENV checks and records every unavoidable difference in your deploy guide, in the same change that adds it. Shows you the edit before saving.
CLAUDE.mdDeploy and hostingVersion: A saved state of a kit. When the author changes it, they share a new version with a higher number, and the old one stays exactly as it was. 0.1.1 (latest)
- Activity
- New: be the first to try it
Will this work for me?
- Effort
- Works out of the boxOur guess from what the kit says it needs.
- Works in
- Claude Code, claude.ai and the desktop app
- You need
- Nothing else. Add it to Claude and ask.
Safety label
- Who made it
- SlashClone house account
- What it touches
- Reads ./CLAUDE.md, ./docs/** and writes to ./CLAUDE.md, ./docs/DEPLOY.md
- Scan
How this works
- It is a CLAUDE.md file: standing instructions Claude reads at the start of every session in a project.
- While it works, it reads and changes files in the places it lists, nowhere else.
- Nothing runs until you choose to use it, and you can remove it any time.
What it can access
What this kit says it will touch, the same list you see before you add it. These are its Permissions: What a kit is allowed to touch on your computer or accounts, such as reading a folder or using the internet. You see them before you add it.. In Claude Code they become rules, so Claude stops anything not on the list.
Reads
Reads files in ./CLAUDE.md
Reads
Reads files in ./docs/**
Writes
Writes files in ./CLAUDE.md