Laws of UX

This skill reviews an interface against the UX laws published on userinterface.wiki. It flags a concrete mismatch, not a wish that the screen were simpler.

Every check is a pair. The broken line sits beside the line that replaces it.

A control under 32px with no expanded hit area is a finding. A blank wait with no feedback is a finding. "This could be prettier" is not a finding. Spacing tokens and shadows belong to visual-design. The pseudo-element hit recipe belongs to pseudo-elements. Animation length belongs to timing-functions. The 400ms rule here is the time until the interface responds, not the length of a transition.

When to use

Use this when reviewing a flow, a form, a menu or an empty and loading state for friction. Use the domain skill that owns a visual value when the issue is type, color, motion or sound.

1. Name the surface

Read the files or the screen in scope. Restate the primary action in one sentence. If the request is "review the whole product", ask which flow.

2. Check the body and the clock

Interactive targets are at least 32px on the smaller side. That is ux-fitts-target-size. When the visible glyph is smaller, expand the hit area. The inset recipe is pseudo-elements. That requirement is ux-fitts-hit-area.