Find components, patterns, tokens, and docs
Usage, variants, states, accessibility, and do / don’t — one page per component.
A button is the primary way a user commits to something on the current page: save, submit, confirm, or start a process.
Icon buttons save space in dense toolbars, tables, and editors.
Groups mutually related actions so they scan as one control.
The basic building block of forms. Collects a single value with a visible label.
Selects constrain input to a known set and prevent typos.
Checkboxes let users opt into independent choices.
Radios make every option visible so comparison is cheap.
Switches represent a state, not a step in a form.
Textareas give room for prose, notes, and unstructured detail.
The navbar orients users: where they are, where they can go, and how to act.
Sidebars hold the product map when there are more destinations than a navbar can carry.
Tabs keep related views of one object on the same page.
Breadcrumbs recover context in deep trees: projects, folders, records.
Alerts persist in the layout until the condition is resolved or dismissed.
Toasts confirm something that already happened, then get out of the way.
Modals demand attention because continuing without an answer is unsafe or confusing.
Tooltips supplement a control that is already understandable from context.
Cards chunk related information so a collection can be scanned.
Badges encode status at a glance: environment, state, or category.
Avatars make people and workspaces recognizable in dense lists.
Tables excel when users compare, sort, and act on many similar records.