# Build with Meridian Page: /docs Meridian is the design system for Commenda’s website: Pathfinder’s tokens, icons and components, sized and extended for marketing pages. Every component ships as typed React from `@commenda/meridian/ui/`, with Pathfinder’s accessible behaviour underneath. ## Start building [#start-building] Read [Getting started](/docs/getting-started), then start with a [Button](/docs/components/button) or an [Input](/docs/components/input). Component pages pair live previews with copyable code, an API reference and the design rules from Figma. ```tsx import { Button } from "@commenda/meridian/ui/button"; import { Input } from "@commenda/meridian/ui/input"; ``` ## Explore the library [#explore-the-library] - **Foundations**: [color](/docs/foundations/color), [typography](/docs/foundations/typography), [spacing, sizing and elevation](/docs/foundations/spacing), [layout guidance](/docs/foundations/layout) and [motion](/docs/foundations/motion). - **Components**: from [actions](/docs/components/button) and [inputs](/docs/components/input) to [selection](/docs/components/checkbox), [tables](/docs/components/table), [calendars](/docs/components/calendar) and [dialogs](/docs/components/dialog). - **Assets**: [icons](/docs/assets/icons), [flags](/docs/assets/flags) and [logos](/docs/assets/logos). ## How it relates to Pathfinder [#how-it-relates-to-pathfinder] Most of Meridian is Pathfinder. Meridian changes only what marketing pages need: fields and the xl button at 40, 16px values and 14px labels, an Eyebrow, Web type roles and a few shadows and easings. Everything else is Pathfinder as it ships. Each page says which parts are Meridian’s and which are Pathfinder’s. ## For AI tools [#for-ai-tools] Start with [/llms.txt](/llms.txt) to discover the documentation, or [/llms-full.txt](/llms-full.txt) for all of it at once. Every page also has a **Read as Markdown** link. In the repo, agents read `web/packages/meridian/AGENTS.md` first. --- # Getting started Page: /docs/getting-started {/* Copy from Figma: Meridian → Getting started (node 52:84). */} Meridian is the design system for www.commenda.io. It is Pathfinder’s sister: the same tokens, icons and components, with a few additions for marketing pages. ## Who it is for [#who-it-is-for] Three readers, three sets of rules. ### Designers [#designers] - Enable Meridian from the Assets panel for every website file. - Place components as they are. An override is a bug report: post it, and the fix goes into the library. - Never detach. If a component cannot do the job, propose a new property. - Every page and section frame carries its layout grid. ### Engineers [#engineers] - Every variable carries its code syntax; Dev Mode shows it. - Component and property names match the code, so Code Connect maps one to one. - Each component has a .md spec in `docs/design-system/meridian`. - Token changes land in code and Figma on the same day. ### Agents [#agents] - Read a component’s description before using it: it names the source, every property and the rules. - Variant property names are prop names; values are prop values (`variant=primary`, `size=xl`). - Use only Meridian. Never reach into Pathfinder or anything on `_Internal`. - Two fonts only: Baskervville Medium and Inter. ## How the file is organized [#how-the-file-is-organized] Pages run from foundations to components, grouped under dividers in the page list. | Group | Pages | | --- | --- | | Start here | Cover, Getting started, Changelog | | Foundations | Color, Typography, Spacing radius and size, Layout, Elevation and borders, Motion, Icons, Flags, Logos | | Actions | Button, IconButton, SegmentedControl | | Inputs | Input, Textarea, Select, Multi-select, Tag, Pill, PhoneInput, AddressInput | | Selection controls | Checkbox, Radio, Switch | | Data display | Badge, Eyebrow, Table, Calendar | | Product elements | Dialog, Popover. Used in website animations and product shots. | | \_Internal | Parts the components are built from. Never place them in a design. | ## How a component page works [#how-a-component-page-works] Every component page has the same parts, in the same order, as in Pathfinder. - A header card with what it is for, and a link to its .md. - Live examples of each variant and state, built from the real component. - An anatomy blueprint, with its measurements and tokens. - Best practices, ending with its source: Pathfinder or Meridian. - The component set sits to the right of the docs, in a section named Component · Name. ## Where things live [#where-things-live] Three places, one source each. - **Figma:** this file, Meridian. Components, variables, styles and the docs pages. - **Specs:** `docs/design-system/meridian`, one .md per component, plus [llms.txt](/llms.txt) for agents. - **Code:** `web/packages/meridian` and the website app, using `@commenda/pathfinder` where the part is unchanged. ## Notes [#notes] - Most of Meridian is Pathfinder. Every component and token says its source in its description. - Meridian adds: the 40 control (Button xl, all fields), Button link-arrow, Tag md 24, the Web type roles, Label/14 and Label/16, shot/lift/ring shadows, pop/glide easings, four website grids, Eyebrow, brand logos and the Commenda submark. - Modelled on Pathfinder’s Getting started page. --- # Foundations Page: /docs/foundations Start with the foundation that matches your decision. Each page combines visual examples, usage guidance from Figma and the exact tokens available in code. Most foundations are Pathfinder’s; each page says what Meridian adds. The 38 Meridian tokens by job, and the Pathfinder scales behind them. Baskervville and Inter, the website roles and the UI styles. Spacing steps, corner radii, control heights, icon sizes, shadows and stroke widths. The four website grids and the spans that land on them. Springs, durations, easings and the recipes built from them. Icons, flags and logos are under [Assets](/docs/assets/icons). ## Use in your application [#use-in-your-application] The website imports the tokens once, in its global stylesheet. Components bring their own Pathfinder styles. ```css @import "@commenda/meridian/styles/tokens.css"; @import "@commenda/meridian/styles/theme-default.css"; ``` ## How to use these references [#how-to-use-these-references] Use a token by its job, never a raw value: `--color-text-secondary`, not `#57524d`. When a page shows a Pathfinder variable (`--pf-spacing-xl`), that is the token to use; Meridian adds its own only where Figma does. --- # Color Page: /docs/foundations/color {/* Figma: Meridian → Color (page 7:91). Laid out like Pathfinder’s Color reference. Meridian swatches render from their CSS variable. */} Every Meridian colour is a Pathfinder colour. Use the tokens in Meridian color; reach into the Pathfinder scales only when no token fits. Use the Meridian tokens below by their job. Each swatch shows the token, its hex and the Pathfinder step it points at; open the table under a group for CSS variables and usage. ## Text [#text] Text on light surfaces. ## Surface [#surface] Backgrounds, from the page to raised cards. ## Border [#border] Hairlines, control edges and focus. ## Brand [#brand] Commenda blue for actions and accents. ## Status [#status] Success, error, warning, info and accent. Never use colour alone to carry meaning. ## Overlay [#overlay] Translucent ink for rings, shadows and scrims. ## Pathfinder scales [#pathfinder-scales] 11 hues × 10 steps. 100–300 fills · 400–600 borders · 700–800 solid fills · 900–1000 text and icons. Choose a scale by its role, then check the foreground and background together. A scale step alone does not guarantee accessible contrast. ### Soft pearl [#soft-pearl] ### Blue [#blue] ### Red [#red] ### Amber [#amber] ### Green [#green] ### Purple [#purple] ### Rose [#rose] ### Orange [#orange] ### Indigo [#indigo] In Figma now; the `--pf-color-indigo-*` variables arrive with Pathfinder 0.3 (this repo pins 0.2.0). ### Teal [#teal] In Figma now; the `--pf-color-teal-*` variables arrive with Pathfinder 0.3 (this repo pins 0.2.0). ### Yellow [#yellow] In Figma now; the `--pf-color-yellow-*` variables arrive with Pathfinder 0.3 (this repo pins 0.2.0). ## Best practices [#best-practices] - Use a Meridian token by its job, never a raw hex. - Every token points at a Pathfinder step, so the two systems stay in sync. - Blue 700 is the only brand action colour. Status colours are for meaning, not decoration. - Gradients, sky art and illustrations live outside the colour system. - Source: Pathfinder Color (all 11 scales, unchanged). Meridian adds the 38 semantic tokens in the Meridian color collection. --- # Typography Page: /docs/foundations/typography {/* Figma: Meridian → Typography (page 7:92). Laid out like Pathfinder’s Typography page. */} Two typefaces. Baskervville Medium for titles, statements, quotes and figures. Inter for everything else. Baskervville numbers are always lining and tabular. ## Typefaces [#typefaces] Baskervville is a Google font; Inter is the UI face shared with Pathfinder. ## Website roles [#website-roles] The marketing and blog styles, `Web/` in Figma. Desktop size shown; tablet and phone sizes are in each style’s description in Figma. These are Meridian’s own and do not exist as CSS classes yet. ## UI styles [#ui-styles] Pathfinder’s Heading, Label and Copy styles for controls, plus Meridian Label/14 and Label/16 for 40px fields and xl buttons. Where Pathfinder ships a class, the specimen below uses it. ## Use a complete text style [#use-a-complete-text-style] A Pathfinder class carries family, size, line height, weight and tracking in one go. Colour and the HTML tag stay your choice. ```tsx import "@commenda/pathfinder/styles.css"; export const FieldLabel = () => ; ``` Tracking is in em: Figma’s −2% is `-0.02em`, not −2px. ## Roles [#roles] - **Display, Statement, Quote, Figure** are Baskervville Medium. They carry the page’s message, never UI. - **H2, H3, Title** are Inter Medium and organise content under a Baskervville headline. - **Article H2, Article H3, Body Article** are for blog posts, TP guides and country pages, sized for long reading. - **Eyebrow** is Inter Semi Bold 13/16, uppercase, tracked 10%, and always sits above a heading. - **Label** is compact UI text: fields, buttons, chips. **Copy** is wrapping prose inside product UI. - Choose h1–h6 by document structure, never by font size. ## Blog spacing [#blog-spacing] Every heading, paragraph, table and image in an article brings its own space above and below. Writers never add spacing by hand, so every post, guide and template looks the same. | Element | Role | Above | Below | | --- | --- | --- | --- | | h2 | Article H2 · 24/32 | 48 | 16 | | h3 | Article H3 · 20/28 | 32 | 12 | | h4 | Title · 18/26 | 24 | 8 | | p | Body Article · 16/26 | 0 | 16 | | ul, ol | Body Article | 0 | 16 | | li | Body Article | 0 | 8 | | table | Table, reading size | 32 | 32 | | img, figure | – | 32 | 32 | | figcaption | Caption · 12/16 | 8 | 0 | | blockquote, callout | Lead · 18/28 | 32 | 32 | | hr | 1px border/subtle | 48 | 48 | When two spaces meet, the bigger one wins: 16 below a paragraph and 48 above an h2 give 48, not 64. The first element has no top space. A heading straight under a heading drops its top space. Phone: h2 top 40, h3 top 24. ## Fonts in code [#fonts-in-code] The website loads both faces with `next/font`: Inter as `--font-sans`, Baskervville as `--font-serif`. Use `font-serif font-medium` for Baskervville. Do not import `@commenda/pathfinder/fonts.css`; Inter is already loaded, and a second copy is a duplicate download. ## Best practices [#best-practices] - Only two fonts: Baskervville Medium and Inter. No third font, even as a placeholder. - Baskervville numbers are lining and tabular. In Figma set Type settings → Details → Numbers on every Baskervville style; the API cannot set it. - Article spacing lives on the element: h2 48 above, 16 below; h3 32 / 12; p 16 below. - Same use case, same role, on every page. - Source: Pathfinder Typography for UI styles. Meridian adds the Web roles and Label/14, Label/16. --- # Spacing, sizing, elevation Page: /docs/foundations/spacing {/* Figma: Meridian → Spacing, radius and size (page 7:93) and Elevation and borders (page 7:95), one page here as on Pathfinder's docs. Previews render from Pathfinder's CSS variables. */} Pathfinder’s spacing, radius, size, shadow and border scales, in one place as on Pathfinder. Meridian uses five of the radii, control/xl (40) for its buttons and fields, and adds three shadows for marketing pages. ## Spacing [#spacing] 17 steps. 8xl and above are for page layout only. ## Radius [#radius] Meridian uses xs 4, md 8, xl 12, 2xl 16 and full. sm 6 and lg 10 stay for Pathfinder parts only. ## Size [#size] Control heights, icon sizes and strokes. control/xl (40) is Meridian’s height for buttons and fields. ## Elevation [#elevation] Six Pathfinder shadows named by job and three Meridian shadows for marketing pages. Flat is the default and is not a style. ## Borders [#borders] A border is a soft-pearl step plus a width. ## Best practices [#best-practices] - Bind every padding, gap, radius, height and shadow to a token. No hand-typed numbers. - Section padding 96 desktop, 48 phone. Card padding 24. Gap between cards is the grid gutter. - 12 between buttons, and between an input and its button. - Fields and the buttons beside them are control/xl, 40. - Use a shadow by its job: control, raised, soft, menu, panel, modal. - shot is only for hero product windows. lift for photos and video on cream. ring for image, logo and flag edges. - Source: Pathfinder Spacing, Radius and Size (unchanged), and Pathfinder Elevation and borders. Meridian adds shot, lift and ring. --- # Layout guidance Page: /docs/foundations/layout {/* Figma: Meridian → Layout (page 7:94). Rules also in docs/design-system/layout-grids.md. */} Four grids. Every page and every section frame carries one, and boxes start and end on a column. ## Grids [#grids] Margin: the empty strip at each edge (hatched). Columns: the slots content snaps to (grey). Gutter: the gap between two columns. Apply the grid style to every page frame and section frame. ## Spans at 1440 [#spans-at-1440] Box widths that land on the columns. ## Best practices [#best-practices] - Every page frame and every section frame gets its grid. No fifth grid. - Gaps between cards are the gutter: 40 on desktop, 24 on tablet and phone. - Wide holds content at 1280, centred. - Grid styles: Grid/Phone 390, Grid/Tablet 768, Grid/Desktop 1440, Grid/Wide 1920. - Source: Meridian (website grids). Pathfinder’s grids are for the app shell. --- # Motion Page: /docs/foundations/motion {/* Figma: Meridian → Motion (page 7:96). */} Motion explains a change. Pathfinder’s springs, durations and easings, plus two Meridian curves for marketing pages: pop for things appearing and glide for cursor travel. Things close faster than they open; only success bounces. ## Principles [#principles] Every transition is checked against these. 1. **Motion explains change.** Things arrive from where they came from: a menu from its trigger, a row from its list. 2. **Change the element.** A state change happens on the element itself. Nothing blinks out and back. 3. **Open with weight, close fast.** Opening uses a spring; closing takes about 70% of the time and never bounces. 4. **Respond within 100ms.** Press feedback starts on pointer down and never waits on the network. 5. **Bounce is earned.** Only success bounces. Data, errors and anything to be read never bounce. ## Springs [#springs] The default for anything that moves. Each spring is a visual duration and a bounce. | Token | Duration · bounce | Use | | --- | --- | --- | | spring/snappy | 0.2s · 0 | Press, switches, checkboxes, menus opening. Must feel instant. | | spring/smooth | 0.3s · 0 | The app-wide default. Sliding indicators, expanding content, size and layout changes, dialogs, list rows. | | spring/release | 0.3s · 0.15 | Motion a gesture started: a drag or sheet settling after release, a flick, a rubber band springing back. Carries the release velocity. | | spring/expressive | 0.4s · 0.25 | Moments of success only (a check landing). Never on expand, data or errors. | `spring/release` and a non-bouncing `smooth` come with Pathfinder 0.3; the pinned 0.2.0 still has `smooth` at bounce 0.15. ## Duration [#duration] For CSS transitions, exits and anything that cannot run on a spring. Nothing goes above 300ms except sheets. ## Easing [#easing] Curves for duration-based transitions. pop and glide are Meridian (`--ease-pop`, `--ease-glide`); the rest are Pathfinder’s `--pf-easing-*`. ## Recipes [#recipes] Every animation is one of these. If none fits, add a recipe here first. | Recipe | Motion | Tokens | Used by | Source | | --- | --- | --- | --- | --- | | Press | Scale to 0.97 on pointer down, back on release. Keyboard never scales. | spring/snappy | Button, IconButton, Pill | Pathfinder | | Hover | Colour only. No movement, no scale. | duration/instant · easing/standard | Every control | Pathfinder | | Open from the trigger | Opacity 0 to 1, scale 0.96 to 1 from the trigger. Closes in 120ms. | spring/snappy · menu exit 120 | Select, Popover, menus | Pathfinder | | Panel and dialog | Fade and rise 8. Exit is a fade only. | spring/smooth · duration/fast | Dialog, panels | Pathfinder | | Sheet | Slides in 500, out 400. | easing/sheet · duration/deliberate | Mobile nav drawer | Pathfinder | | Row in | Rows rise 8 and fade in, 40 apart. | easing/out · duration/slow | Tables in product shots | Meridian | | Badge pop | Scale 0.8 to 1 with a small overshoot. | easing/pop · 360 | Status pills, chips, nodes in shots | Meridian | | Cursor glide | The fake cursor travels between targets. | easing/glide · 850 | Product-shot animations | Meridian | | Success | A check lands with a bounce. | spring/expressive | Button done, form sent | Pathfinder | ## Best practices [#best-practices] - Pick a recipe; never invent a curve. - Reduced motion: no movement, fades only. - Source: Pathfinder Motion. Meridian adds easing/pop, easing/glide and the Row in, Badge pop and Cursor glide recipes. --- # Icons Page: /docs/assets/icons {/* Figma: Meridian → Icons (page 7:97). Explorer over @commenda/pathfinder/icons at size 24. */} The 132 Pathfinder icons the website uses, copied from Pathfinder and grouped into its categories, plus 15 that sit inside Meridian components. Pathfinder icons only: lucide and hand-drawn SVGs are retired. ## Usage [#usage] ```tsx import { SearchMdIcon } from "@commenda/pathfinder/icons/SearchMdIcon"; ; ``` Import each icon from its own subpath so a page ships only the artwork it uses. ## Rules [#rules] - Sizes: every icon is a component set with size = 12 · 16 · 20 · 24. 16 in md and lg controls and fields, 20 in xl buttons and lg icon buttons, 24 for feature icons. - Colour: an icon takes the colour of the text beside it. - Names match Pathfinder (search-md, arrow-right), so code and Figma use the same name. - Missing an icon? Ask for it in Pathfinder first, then copy it here. Brand logos and the Commenda submark are on the Logos page. - Source: Pathfinder Icons. Also used inside components, from other Pathfinder subpaths: `logo-quickbooks` (`logos/integrations/QuickbooksLogo`), `progress-ring`, `status-completed` and `status-failed` (`status-icons/*`). `file-pdf` is Meridian’s `PdfFileIcon`. --- # Flags Page: /docs/assets/flags {/* Figma: Meridian → Flags (page 7:98). Explorer over @commenda/pathfinder/flags at size 24. */} 256 round country flags, copied from Pathfinder. Named by ISO code; the description gives the country name. ## Usage [#usage] ```tsx import { USFlag } from "@commenda/pathfinder/flags/USFlag"; ; ``` Import each flag from its own subpath so a page ships only the artwork it uses. ## Rules [#rules] - Always round: entity, country and jurisdiction flags are circles, never 3x2 rectangles. - Sizes: every flag is a component set with size = 12 · 16 · 20 · 24, the same as Icons, so a flag can swap into any icon slot. - A 0.5 soft-pearl 300 hairline sits inside the edge so white flags (Japan, Cyprus) keep a shape. - Search the Assets panel by ISO code (GB, US, SG) or by country name. - Grouped by UN region, then A to Z by country name. - Source: Pathfinder Flags. Abkhazia (GE-AB) and South Ossetia (GE-OS) are in Figma but not in the pinned Pathfinder 0.2.0. --- # Logos Page: /docs/assets/logos {/* Figma: Meridian → Logos (page 7:99). Imported from @commenda/meridian/icons. */} Brand logos for social links and AI partners, and the Commenda submark. These are Meridian’s own; everything else on the site is a Pathfinder icon. ## Brand logos [#brand-logos] 24 square, ink by default. Footer social links use them at 20 inside a plain IconButton. Instagram is in Figma but not yet in Meridian; today it only exists as app art in `web/apps/website/src/assets/svg/home-v2/instagram.svg`. ## Commenda submark [#commenda-submark] The sparkle. It sits inline with Baskervville headings or alone as a mark. In code: `SparkleStar` (standalone) and `SparkleIcon` (sized to sit inline with a heading). ## Best practices [#best-practices] - Brand logos stay monochrome: ink on light, white on dark. - The submark is not an icon. Never replace it with stars-02 or any Pathfinder glyph. - OpenAI is still to come: the file on the site is truncated, so it needs a clean SVG. - Customer and partner logos for logo rails live with the page art, not in this library. - Source: Meridian. --- # Button Page: /docs/components/button {/* Figma: Meridian → Button (docs 14:53, component set 12:633). Spec: docs/design-system/meridian/button.md */} Starts an action. Pathfinder Button with one more size, xl 40, so a button sits next to the 40 Input, and a link-arrow variant for card and section links. Five variants, three sizes and seven states. Click **Save changes** to preview loading and completion. It resets on its own so you can try again. ```tsx "use client"; import { Button } from "@commenda/meridian/ui/button"; import { useState } from "react"; import type { ReactNode } from "react"; function Stage({ children }: { children: ReactNode }) { return (
{children}
); } /** Click to run loading → done, then it resets, like Pathfinder's feedback demo. */ export function ButtonFeedback() { const [phase, setPhase] = useState<"idle" | "loading" | "done">("idle"); const run = () => { setPhase("loading"); setTimeout(() => setPhase("done"), 1200); setTimeout(() => setPhase("idle"), 2700); }; return ( ); } ``` ## Usage [#usage] ```tsx import { Button } from "@commenda/meridian/ui/button"; ; // Navigation is a real link: render the button as an anchor. ; ``` The Pathfinder stylesheet comes with the component; there is nothing else to import. ## Sizes [#sizes] md 32 inside cards and tables, lg 36 in the nav and on phones, xl 40 for page CTAs. Height comes from the control token; width hugs the label. ```tsx import { Button } from "@commenda/meridian/ui/button"; import type { ReactNode } from "react"; function Stage({ children }: { children: ReactNode }) { return (
{children}
); } function Labelled({ label, children }: { label: string; children: ReactNode }) { return (
{children} {label}
); } export function ButtonSizes() { return ( ); } ``` ## Variants [#variants] Primary for the one main action in a view, secondary beside it, tertiary for quiet repeated actions. Link sits inline with copy; link-arrow ends a card or section. ```tsx import { Button } from "@commenda/meridian/ui/button"; import type { ReactNode } from "react"; function Stage({ children }: { children: ReactNode }) { return (
{children}
); } function Labelled({ label, children }: { label: string; children: ReactNode }) { return (
{children} {label}
); } export function ButtonVariants() { return ( ); } ``` ## Icons [#icons] A left icon only when it adds meaning. A right icon for a trailing arrow. link-arrow always carries its arrow. ```tsx import { Button } from "@commenda/meridian/ui/button"; import { ArrowRightIcon } from "@commenda/pathfinder/icons/ArrowRightIcon"; import { PlusIcon } from "@commenda/pathfinder/icons/PlusIcon"; import type { ReactNode } from "react"; function Stage({ children }: { children: ReactNode }) { return (
{children}
); } export function ButtonIcons() { return ( ); } ``` ## States [#states] Hover and pressed come from interaction, focus only from the keyboard. Loading puts the spinner beside the label; done confirms with a check. Disabled stays focusable and can explain why. ```tsx import { Button } from "@commenda/meridian/ui/button"; import type { ReactNode } from "react"; function Labelled({ label, children }: { label: string; children: ReactNode }) { return (
{children} {label}
); } /** Static states: hover and pressed come from the pointer, focus from Tab. */ export function ButtonStates() { const rows = [ ["primary", "Book a demo"], ["secondary", "Book a demo"], ["tertiary", "Book a demo"], ] as const; return (
{rows.map(([variant, label]) => (
))}

Hover and press any button above; Tab to see focus.

); } ``` ## Next to an input [#next-to-an-input] A button beside a field is always xl 40, 12 apart. On phones they stack, both full width. ```tsx import { Button } from "@commenda/meridian/ui/button"; import type { ReactNode } from "react"; function Stage({ children }: { children: ReactNode }) { return (
{children}
); } export function ButtonNextToInput() { return (
{/* Placeholder field until Meridian Input lands: 40 tall, border/default. */}
); } ``` ## Anatomy [#anatomy] Every part is optional except the container and label. Icons take the label colour. | Part | md · lg | xl | | --- | --- | --- | | Container height | 32 · 36 (`control/md`, `control/lg`) | 40 (`control/xl`) | | Padding | 12 | 16 (`spacing/xl`) | | Gap, label to icon | 6 | 8 (`spacing/md`) | | Icon | 16 · 20 | 20 | | Label | Label/13 Strong · Label/15 Strong | Label/16 Strong | | Radius | 8 (`radius/md`) | 8 (`radius/md`) | ## API reference [#api-reference] | Prop | Type | Description | | --- | --- | --- | | `variant` | `"link" \| "primary" \| "secondary" \| "tertiary" \| "link-arrow"` | Figma `variant`. One primary per view. | | `size` | `"md" \| "lg" \| "xl"` | Figma `size`: md 32 in cards and tables, lg 36 in the nav and on phones, xl 40 for page CTAs. | | `completionConfig` | `CompletionConfig` | Figma state `done`: the label and check shown after a successful action. | | `className` | `string` | | | `style` | `CSSProperties \| ((state: ButtonState) => CSSProperties \| undefined)` | Style applied to the element, or a function that returns a style object based on the component's state. | | `focusableWhenDisabled` | `boolean` | Whether the button should be focusable when disabled. | | `nativeButton` | `boolean` | Whether the component renders a native `