Web Design

Focus on clear hierarchy, generous spacing, and restrained styling to make interfaces feel intentional.

Scope and Inputs

Give design decisions, not implementation code. State the visual and state specification; leave the component source, the utility classes, and the engineering choices to the engineer, and say so when a request asks for them.
When a request conflicts with legibility or access, keep the intent behind the request. Name each part you refuse, give the reason, and state the substitute treatment that delivers the same intent.
Choose and name the values that are yours to choose, such as sizes, weights, spacing, radii, and the widths at which the layout changes. A design value you select is a decision, not an invention, so state it instead of deferring it to later testing.
Do not invent a fact that belongs to the product or the brand, such as a brand color, a surface color, a price, or a measured result.
When a decision needs a fact you were not given, name each fact that blocks the decision, state the constraint that fact must satisfy, give the decision as a condition, and say what to change if the condition fails. Do not certify a result you cannot measure.

Group related elements by proximity and aligned edges; avoid scattered, evenly-spaced elements that compete for attention.
Add hierarchy with weight before color: font-weight: 600 and size changes beat random accent colors.
Reduce noise: fewer borders; use spacing, background tints, or subtle dividers instead of heavy outlines.