Brik Design System

Brik Design System

Four tenets in one repository, published as a single versioned package.

BDS is four tenets in one repository, shipped as a single versioned package. Each tenet is an independent vocabulary the portal, mockup generators, and client sites consume to ship work that looks and reads like Brik without anyone having to re-decide the basics every project.

This site is the guidance layer. For live prop exploration and visual variants, Storybook stays the playground.

The four tenets

TenetAnswersShips
Foundation"What color, size, type?"Design tokens, scales, primitives
Theming"What brand, mood, shape?"Tokens + atmospheres + navigation archetypes + blueprints
Motion"How does it feel to move?"Three-tier animation system — CSS reveals → GSAP scroll → premium effects
Content"What does it say, for whom?"Industry packs, voice patterns, locked vocabularies

Each tenet evolves on its own cadence but cross-links at the edges. An industry pack declares a default atmosphere and navigation archetype, so the Content tenet drives defaults for the Theming tenet that the client brand then optionally overrides.

Where to start

Foundation — the visual atoms

Design tokens are the atomic visual decisions that power BDS. Every component references tokens — never raw values.

Border radius, border width, shadow, and size scales are documented in Storybook today and migrate here next.

Theming — the multi-tenant instrument

Theming composes four orthogonal layers. Each is a decision a client can override independently of the rest.

LayerDecidesWhere it lives
TokensColor, type, spacing values per brandtheme-{client}.css in the consumer repo
AtmospheresAmbient mood — grain, glow, vignettes@brikdesigns/bds/atmospheres/{slug}.css
Navigation ArchetypesSite-header shape + scroll/drawer behaviorIndustry pack → BDS <SiteHeader>
BlueprintsSection composition + mood taggingAuthored in BDS, tagged per industry + mood

Motion — the three-tier system

TierUse for
LightweightReveals, hovers, transitions — pure CSS, no JS
GSAPScroll-driven sequences, complex orchestration
PremiumCinematic moments — typography flourishes, video overlays

See Primitives → Motion for the decision tree and per-tier specs.

Content — the vocabulary peer

The content-vocabulary peer to the visual tokens. Paired with BDS to drive end-to-end mockup generation and structured strategy documents.

Components

GroupComponents
ActionButton, IconButton, LinkButton, ButtonGroup, FilterBar
FormField, TextInput, Select, MultiSelect, DatePicker, Form, FieldGrid
IndicatorBadge, Chip, Tag, Counter, Spinner, Skeleton
FeedbackAlertBanner, Toast, Tooltip, EmptyState, ProgressBar
ControlSwitch, Slider, Stepper, Pagination, SegmentedControl, FileUploader
AddableAddableTagList, AddableEntryList, AddableFieldRowList
StructureCard, Divider, Accordion

See Components for the full index.

Token system — the naming contract

Components use CSS custom properties from the Style Dictionary token pipeline:

--[category]-[type]-[variant]

Primitives — raw scale values, never used directly in components:

--space-400;             /* 16px */
--font-size-700;         /* 32px */
--color-grayscale-darkest; /* #333 */

Semantic — purpose-bound aliases, always use these in components:

--background-brand-primary; /* brand background color */
--font-family-heading;      /* heading font family */
--padding-lg;               /* large spacing value */
--border-radius-md;         /* button/card corner radius */

Never write raw var() strings inline in app code. Import from @/lib/tokens and @/lib/styles in consumer projects. The cascade is a contract — bypassing it leaks brand drift into components.

On this page