Design Rules

Not negotiable. These are the hard rules of UI craft for THIS product, and they hold every time you create or edit any frontend / user-facing surface -- page, feature, component, element, color, button, navigation, micro-interaction. Build to them while you write the UI, not as a cleanup pass afterward. The only things out of scope are pure backend with no UI (the database and the API / server routes).

This rulebook is the single source of truth. It is verified, not enforced by a build-time hook: landing-audit grades a landing page against these rules, and shipit checks the touched UI files against them after tests and before commit (the same way it scopes tests to the diff's blast radius). Keep the rules here; both of those skills point back to this file rather than restating it.

We are not generalists. The UI is specific to THIS product, and it earns "premium" by being minimal, tight, calm, and practically relevant to the user at all times -- not by adding more. Public-facing pages get the most scrutiny. We will make mistakes; we fix them by updating these rules, not by abandoning them.

This is about craft and feel, not marketing.

Broken hierarchically

Fix with:

• Size
• Contrast
• Spacing

Make the most important thing the biggest, give it room.