Welcome
Sign in or create an account.
Login & Registration
Storybook ↗Simple login, login with social auth, a registration form, and a tabbed login and registration form.
Patterns are higher-order compositions — assembled from primitives, wired to the same token system, and tested against the same accessibility checklist. When the tokens move, every pattern moves with them.
inputs
Components
43 typed primitives
Tokens
143 OKLCH colors
composed into
Patterns
15 reference compositions across 9 categories.
shipped as
Pages
Real product surfaces, end-to-end.
Sign-in, registration and account recovery examples, with validation states, error messages and social-auth placeholders.
Sign in or create an account.
Simple login, login with social auth, a registration form, and a tabbed login and registration form.
Enter your email and we will send a link.
Forgot-password email step, reset-password form, an invalid-link state, and a multi-step recovery flow.
Browseable grids and showcase grids. Both share the same card primitive but differ in density and what they ask the user to do next.
One source of truth for Figma and code.
Contrast and focus checked on every build.
Import only the components you use.
Small parts that fit together.
Responsive grid of cards with default, all-variants and interactive examples. CardGrid takes a column count per breakpoint.
One source of truth for Figma and code.
Contrast and focus checked on every build.
Import only the components you use.
Small parts that fit together.
A grid of features with icons, titles and short descriptions, with several column configurations.
When something fails, the pattern catches it. Error states aren't an afterthought — they're designed as carefully as the happy path.
This card has its own boundary.
A failure stays inside its boundary, so this card keeps working.
Basic and recoverable error boundaries, multiple and granular boundaries, custom fallback UI, and error logging.
Form composition and validation are the largest source of bespoke UI in any product. These patterns close the gap so teams stop reinventing field groupings, error display, and async submit states.
Contact, multi-step, preferences, project-creation, payment and settings forms built from the system's form components.
Errors show once a field has been visited.
Required-field, inline, password-strength, multi-step and async validation using the Form components and controlled state, with no external validation library.
Page-level layouts built from the system's components: a dashboard, a settings page, a landing page and a user profile.
Tokens
Components
Checks
Elena Mori
Published tokens
Jude Reyes
Reviewed a pull request
Ari Klein
Added a component
Dashboard, settings page, landing page and user profile layouts, each composed from cards, inputs and separators.
Pre-assembled marketing surfaces — the big building blocks of a public page. Each section composes lower-order patterns; the page composition wires them together end-to-end.
Headline, description, action buttons and an optional badge or image, in default, gradient and centered layouts.
One source of truth for Figma and code.
Contrast and focus checked on every build.
Import only the components you use.
Small parts that fit together.
Features section built on FeatureGrid, with optional badges, several column configurations and style variants.
The header, sidebar, content and footer share one page.
Full-page layout with header, footer, sidebar and main content, in several width variants with a left or right sidebar.
Breakpoint-aware layout decisions. Not just "shrink the desktop" — structural reflows that pick the right pattern for each surface size.
Fits the space it is given.
Fits the space it is given.
Fits the space it is given.
A responsive card grid, navigation and form. Use Storybook's viewport toolbar to compare mobile, tablet and desktop.
Components are tested against WCAG 2.2 AA. These patterns show focus management, live-region announcements, a keyboard-only form, color-contrast checks and skip navigation.
Press Tab. The ring comes from the focus tokens.
The message is tied to the field and announced when it appears.
Enter a full email address.
A polite status message, announced without moving focus.
Reference implementations for focus rings, live regions, error announcement, keyboard navigation, and skip links. The shared focus indicator is driven by --color-focus-ring and --color-focus-halo, so a token change updates it everywhere.
Components answer "what". Patterns answer "when, how, and in what order". Two teams shipping the same Input on the same Card with the same Button can still produce two different sign-in forms — that's the inconsistency patterns exist to eliminate.
Sign-in flows, error boundaries, responsive sidebars — these have all been designed before. Reach for the pattern; spend your novelty budget on the product, not the plumbing.
If no pattern fits, compose from components instead of bending a near-miss pattern out of shape. Then nominate the result for inclusion — that's how the catalog grows.
When --color-background-primary moves, every button, badge, and focus ring across every pattern moves with it — no pattern-by-pattern refactor required.
Ready to build?
Each pattern ships with full states, controls, and copy-paste source. The Storybook mirrors what you see on this page — minus the pixel gap.