Patterns
Pick a recurring product UI problem and see how three to four canonical systems document a serious answer to it. The horizontal cut through the rich breakdowns — for when "how does Polaris do it?" is the wrong question and "how does anyone good do it?" is the right one.
The pattern most systems duck and the small set that document it well.
Validation timing, error placement, save-and-resume — the pattern that separates serious systems from toolkits.
When the cost of a mistake is real, the dialog earns its design budget.
First-run, no-results-after-filter, lapsed-user — three distinct problems pretending to be one.
Tab bars, navigation drawers, top-bars — the pattern that anchors every other pattern on the page.
How the system says what your product says — the layer above components that shapes every word.
The keyboard-first surface that's eaten product navigation in the last five years.
The pattern that determines whether a search-result page is usable above 10 results.
Where users come to monitor — patterns that make complex state legible at a glance.
The pattern that exposes whether your color tokens are real tokens or just aliased hex.
Duration and easing tokens — the pattern that lets motion stay coherent without committing to choreography.
The accessibility pattern most teams botch — focus rings, focus traps, skip links.
