Style guide

What lives here: design tokens, utilities, generic components (mirroring DaisyUI's organisation), and the surface index.

What doesn't: surface-specific composites. The live mockup pages document those by example.

Litmus test for adding a section: Would I reach for this on a surface I haven't built yet? If no, it stays with the surface.

Spec reference: _bmad-output/planning-artifacts/ux-design-specification.md
Theme: geoda-museum · Authored as Astro components in mockup/src/

Base

Design tokens — the values everything else is built from.

Colors, typography, spacing, radius.

Cross-cutting helper classes that aren’t tied to a single component.

Status colors, link utilities (.prose-link, .muted-link), typography utilities (.binomial, .lang-tag), section labels.

Generic components, organised the way DaisyUI organises its docs. Surface-specific composites live on the live mockup pages, not here.

Button, Modal.

Badge, Card, ImageCard, PageHero, CitationCard, StatCard, FactListCard, FigureCard, LinkListCard, SelectableCard, Table, List.

Breadcrumb, Tabs, TopBar, Footer, UserAnchor, LoadMore, ViewToggle.

Alert / Banner, Progress, Empty states, Error states.

Text input, Checkbox, Radio, Fieldset / Legend, SearchInput, Dropzone.

PageContainer, DetailLayout, Divider, Drawer.

Thin navigational layer over the live mockup pages.

One entry per surface, linking to the live mockup page.