Index › Patterns
5 recipe families
Above the component.
Patterns are composed, opinionated recipes — several primitives wired into a ready-to-use solution. Where a Component gives you one part, a Pattern hands you the assembled whole: the filter bar already connected to its drawer, the board that already knows how to move a card between columns.
Filtering
01Pare a long index down to what matters — search, quick pills, and a drawer of deeper controls, every active filter shown as a removable chip.
Kanban Board
02A column board you drag work across — bookings or treatment plans moving through stages, card order and column committed on drop.
Dialogs
03Stop the client for one decision or one short form — a confirm before a destructive change, a focused form without leaving the page.
Notifications
04Tell the client what just happened, at the right volume — a transient toast, a standing banner, an inline line, a bell-and-panel centre.
States & help
05The honest in-between screens — empty lists, error pages, a search across everything, and the keyboard map that moves faster than the mouse.
Patterns compose Components + Layout & Shell. Reach for a Pattern when you want the assembled recipe; reach for a Component when you need one primitive.
Each recipe carries decisions already made — apply-vs-live filtering, where the toast stacks, what an empty list says. Take the default, or lift a primitive out and wire your own.
