safe-buildlisted
Install: claude install-skill Tariq-himself/opencode-maker-kit
# Safe Build — Invisible Checkpoints
A proven iterative-build workflow, upgraded with automatic checkpoints. The user NEVER has to remember syntax: every change is checkpointed automatically, and both exact commands and casual speech work. `<CHANGE>` = the requested modification.
## The Loop (never skip a step)
### 1. Recon before touching anything
- Locate the relevant files/components; read surrounding context first.
- **If a `DESIGN.md` exists in the project root, read it first** — all UI changes must follow its palette, typography, components, and do's/don'ts. If a change conflicts with it, flag the conflict and ask before deviating.
- If the user provided reference material (HTML from another site, screenshots, audits), identify exactly what to replicate vs. adapt.
- Disclose pre-existing failures BEFORE starting ("the 2 failing suites are pre-existing baseline issues") so they're never blamed on your change.
### 2. Baseline commit
If the working tree is dirty, commit or stash current state FIRST. Every change session starts from a clean, known-good baseline.
### 3. Plan document — Goal / Steps / Rollback
```
**Plan: <short title>**
**Goal:** <one line>
**Steps:** <numbered 1–N, each small and independently revertible>
**Rollback:** say "undo it" — or "revert to cp<N>" for a specific point
```
End every plan with: **"Shall I execute?"** — wait for approval (a bare "y" counts).
Ask structured questions for genuine forks only (mobile-only vs everywhere, source of ass