Skip to content
GitHub
Sections

Reference · Principles

Frame 2: Every detail has a reason you can state

This is a spec: descriptive guidance, not a checkable rule. It carries no forbidden and instead pair, and no jig check detector applies to it directly.

The spec

Ask: why this way rather than another way?

Some elements are decorative. Everything else should have a rationale you can articulate — not "it looks better", which is an opinion and cannot be discussed, tested, or handed to someone else.

This is the test every rule in this system had to pass, and it is why the token files hold resolved numbers rather than ranges. A range defers the decision to whoever reads it next; a number is a decision that can be argued with.

Use it like this: when you make a call the rules do not cover, state the reason in one line. If you cannot, you are guessing — and a guess should be surfaced as a question, not shipped as a decision (Tiebreaker 5).

Kind
Spec
Section
Principles
Group
Frames

Read as plain text