Set up safe, boring deploys

Goal

Ship to production on green tests and always know what is live

For

Small teams and solo builders on GitHub

Steps

5

About

90 minutes

5 steps, in order. Sign in to keep track as you go.

1. 1

   Step 1: Install npm packages safely

   Add the rule so your agent checks every package before installing it and pins exact versions.

   Passes on: Pinned dependencies and a rule your agent follows

   Use in Claude
2. 2

   Step 2: Stop bugs that only happen in production

   Add the rule that keeps development and production behaving the same, and list any real differences.

   Passes on: A short list of dev and production differences

   Use in Claude
3. 3

   Step 3: Document how your app is deployed

   Write down how your app ships: hosts, env vars, releases, and how to roll back.

   Passes on: docs/DEPLOY.md that the next steps follow

   Use in Claude
4. 4

   Step 4: Safe automatic deploys from GitHub Actions

   Set up a GitHub Actions release that ships main only when its tests pass, with one button.

   Passes on: An on-demand release workflow

   Use in Claude
5. 5

   Step 5: Check your site works after every deploy

   Run a smoke test after each release and roll back if it fails.

   Passes on: A release that checks itself

   Use in Claude