#engineering patterns
10 build entries, newest first.
-
The agent designs. The script ships.
Claude decides what the about page should be. ship.sh decides nothing. The roles don't blur.
-
Atomic commits by default
Each ship.sh run produces three or fewer commits, each scoped to one logical change.
-
Best-effort patches with explicit fallbacks
The nav patcher tries two patterns, warns if both fail, and never blocks the ship.
-
Branch per feature, named for the moment
Each ship cuts a feature branch from master. The branch name is a sentence about the change.
-
The bundle shipper pattern
When the sandbox can't reach the repo, hand the human a single bash command that does everything.
-
Print cleanup commands. Don't auto-delete.
Every ship script ends with rm commands you can copy. None of them run on their own.
-
Saving alpha into WebP without a halo
alpha_quality=100 and exact=True kept the soft edges of the cutouts clean over the aurora.
-
The working tree must be clean before any ship
Every ship.sh aborts if git diff isn't empty. No exceptions, no auto-stash.
-
Extracting the noise URL instead of duplicating it
The about page reuses the home hero's noise texture by reading it out of hero.css at install time.
-
Vercel preview as the review loop
Every branch push gets a real URL. The review happens against the deployed preview, not the dev server.