kisslisted

# KISS **Measure twice, cut once.** Every cut — every line written, edited, or deleted — is preceded by a measurement. Measure, cut once, confirm the cut landed clean. Most bloat and breakage is cheapest to prevent at the wellspring, *before* the cut exists; guards catch errors downstream, KISS prevents them at the source. This is the **front door**. It does three things: holds the measure-twice discipline, runs a one-time **kickoff** that makes a project start clean, and **routes** to the focused KISS skills. ## The pre-cut gate — before any write, edit, or delete The two measurements already live in the focused skills. This gate just makes sure they happened before you cut: | Measure (before the cut) | Skill | |---|---| | Does it already exist / where is it / does it have a twin? | `kiss-map` — consult `.kiss/inert.md` | | **Does this concept already have an OWNER?** (grep the **store**, not the name) | **`kiss-coherence`** | | **About to hardcode a visual constant** (font size, color, spacing, radius)? **Does a design token already own that value?** | **`kiss-coherence`** → *design values* | | Do I understand the frame and the slot it goes in? | `kiss-plan` | | Is the change scoped to one bounded unit? | `kiss-blast-radius` | | **If replacing a condition — what is it *incidentally* preventing?** | **`kiss-blast-radius`** | | **If DELETING an entity — what is its full footprint?** (assets, config rows, data dirs, build output) | **`kiss-blast-radius`** → *residue trap*