Design Loop — the front door of the design area

A reference you can open, mechanisms you can check, and three judges who did not build the thing.

This is where a design request enters. It owns the method: the bar, the judges, the rounds. It does not own the visual system — ../design/SKILL.md does, and this skill invokes it as the builder.

Why the method and not a rubric. A rubric scored by whoever built the piece measures intent, because the builder knows what they were going for and so they see it there. And scores drift upward every round: a 7 that becomes an 8 with nothing changed is how a loop declares itself finished early. Binary verdicts from someone who did not build it are the fix for both.

Four phases. Do not skip ahead, and do not start building during 1 to 3.

Phase 1 — Interview

Ask exactly these three, together, then stop and wait.