@design-intelligence/ghost 0.21.0 → 0.22.0

package/dist/init-payloads/skeleton/foundation.layout.md

@@ -0,0 +1,45 @@
+---
+description: "Layout — stacks with five gap steps, surface roles, three elevation tiers, the two radius roles, and misuse; radius values are an open question. Read before laying anything out."
+---
+
+## Usage
+
+All layout is stacks. Rhythm comes from relationships between siblings, not
+from isolated margins pasted onto whichever element was last touched. The
+gap steps are exactly five: `--gap-xs` through `--gap-xl`. Choose the gap
+that states the relationship; do not tune by single pixels to make a
+screenshot pass. The default is column, medium gap. Columns are for almost
+everything — forms, cards, modal bodies, settings, page sections. Rows are
+conditional: controls, metadata lines, paired label/value moments. If a row
+wraps awkwardly, it wanted to be a column.
+
+Surface is the only way an element gets a background, border, radius, or
+shadow. The vocabulary is closed: role, padding, radius, border, elevation.
+The default surface is flat — no border, no shadow. We do not outline
+everything to prove layout exists.
+
+The elevation tiers are exactly three: card, popover, modal. Elevation
+implies hierarchy — a card sits in flow, a popover floats above it, a modal
+interrupts the task. Pick the tier that matches the interaction.
+
+Borders are structural — inputs and overlays — not decorative frames around
+ordinary text. Use space, tone, and type hierarchy instead.
+
+## Radius
+
+Open — ask the human; do not freehand. The fixed relationship: controls and
+surfaces carry different radius roles, and the two never swap. Buttons and
+inputs take `--radius-control`; cards and containers take
+`--radius-surface`. One radius for what you click, one for what contains.
+The open question: how round is a control, and how round is a surface? When
+answered, restate this section as the brand's current answer. Until then,
+choose provisional values and label them.
+
+## Misuse
+
+- No ad-hoc margins between siblings — they hide the rhythm. Change the
+  stack gap or split the stack.
+- No custom shadows because a composition feels flat, and no modal gravity
+  on a routine card. Component shadows belong to the primitives that own
+  them.
+- Never one radius everywhere by reflex.

package/dist/init-payloads/skeleton/foundation.motion.md

@@ -0,0 +1,34 @@
+---
+description: "Motion — evidence of state change, three durations and one ease, nothing loops, and misuse; the ease's character is an open question shared with voice. Read for any transition or hover treatment."
+---
+
+## Usage
+
+Motion is evidence of a state change. It confirms hover, press, reveal,
+collapse, entrance, exit, and spatial movement. It does not entertain.
+
+The entire vocabulary is three duration roles and one ease. Fast is for
+hover and press. Normal is for reveals, fades, and small state changes. Slow
+is reserved for spatial transitions where the user needs to understand
+movement. Prefer opacity and small transforms.
+
+In editorial and marketing contexts, entrances may be staged — scroll
+reveals and section transitions are part of editorial rhythm, still built
+from the three durations and the one ease. In product UI the same staging is
+decoration.
+
+## Character
+
+Open — ask the human; do not freehand. Motion and voice share one
+temperature: however warm or cool the brand's words are, its movement
+matches. See the voice foundation for the other half of this answer. The
+open question here: what character does the one ease carry? When answered,
+restate this section. Until then, use a quiet standard ease and label it
+provisional.
+
+## Misuse
+
+- Nothing loops except explicit loading states. Decorative pulsing,
+  floating, glowing, and attention-seeking keyframes are off-language.
+- No novelty easings because a surface feels static.
+- If removing an animation does not reduce comprehension, it was decoration.

package/dist/init-payloads/skeleton/foundation.type.md

@@ -0,0 +1,44 @@
+---
+description: "Type — six text variants, seven tones, the one-voice rule, and misuse; the typeface is an open question. Read for any view that contains text."
+---
+
+## Usage
+
+Hierarchy is a closed vocabulary, not a size slider. Every piece of text
+picks from a named set; anything outside the set is a broken primitive, not
+a variant.
+
+The text variants are exactly six: display, headline, title, body, label,
+mono. Variant names are jobs. Display leads a rare editorial moment.
+Headline names a section. Title anchors a card, dialog, or compact region.
+Body carries reading. Label names structure — field labels, category tags,
+metadata, compact status. Mono carries code and machine detail.
+
+The tones are exactly seven: default, muted, inverse, success, warning,
+info, destructive. Tone is part of the message. Hierarchy starts with tone
+and weight before size — a secondary note usually wants muted body or label,
+not a smaller custom font. If prose needs emphasis, improve the sentence
+before adding a style.
+
+The heading scale is editorial: it exists for pages composed outside the
+text variants — heroes and editorial moments. Product UI never mixes the two
+vocabularies in one view. A modal title is not a poster.
+
+Balanced text is for headings and compact statements, never long body copy.
+
+## Typeface
+
+Open — ask the human; do not freehand. The fixed relationship: one typeface
+is the voice of the interface, everywhere, with a mono partner only for
+code, tool detail, and machine output. The open question: what typeface is
+this brand's voice, what mono partners it, and what rhythm does the
+editorial heading scale carry? When answered, restate this section as the
+brand's current answer. Until then, choose a quiet provisional pair and
+label it provisional.
+
+## Misuse
+
+- No faked hierarchy with arbitrary font sizes. Choose the variant that
+  matches the job.
+- Status tones appear only when the words carry that state meaning.
+- Never a second display face to make a view feel branded.

package/dist/init-payloads/skeleton/foundation.voice.md

@@ -0,0 +1,29 @@
+---
+description: "Voice and tone — copy states facts, no performed personality, and misuse; warmth is an open question shared with motion. Read for any copy."
+---
+
+## Usage
+
+Copy states what happened, what is possible, or what the user must decide.
+It does not perform personality. Confidence comes from precision, not
+enthusiasm.
+
+Voice and motion carry the same temperature: a brand whose copy is warm does
+not move coldly, and a brand whose copy is spare does not bounce. When you
+set one, check the other.
+
+## Warmth
+
+Open — ask the human; do not freehand. The open question: how warm or cool
+does this brand sound — and, by the shared temperature, how does it move?
+See the motion foundation for the other half. When answered, restate this
+section as the brand's current answer. Until then, write plainly and label
+the tone provisional.
+
+## Misuse
+
+- No exclamation points as a substitute for having something to say.
+- No apologizing for the interface ("Oops!"). State the fact and the next
+  step.
+- Never restate this section as answered when it was your own provisional
+  choice.

package/dist/init-payloads/skeleton/glossary.md

@@ -1,44 +1,39 @@
 ---
 kinds:
-  - name: grammar
-  - name: signature
-  - name: register
-  - name: anti-goal
-    posture: guard
+  - name: foundation
+  - name: context
+  - name: cliche
 ---
 
-# grammar
+# foundation
 
-The brand's decision logic: closed sets, role vocabularies, and assembly
-rules, stated in token roles and never in literal values. Grammar survives an
-adaptation unchanged — swap every value and these nodes still hold. Gather
-grammar before inventing structure.
+The core elements — color, type, controls, layout, motion, voice — plus
+composition, the rules for assembling them into a view. Each foundation
+node is a chapter: usage rules that hold no matter what the brand values
+turn out to be, the brand's open questions (unanswered in this starter,
+marked as decisions only a human can make), and the chapter's misuse list.
+Follow the usage rules as written. Never fill in an open value and present
+it as the brand's.
 
-# signature
+# context
 
-The dials: the choices that make a brand this brand. In this starter every
-signature node is unanswered — it states the fixed relationship worth
-keeping and asks the question only a human can answer. When the human
-answers, restate the node as the brand's current answer. Gather signature
-before setting any value a dial governs.
+Where the defaults bend: a context names a situation — an AI conversation
+thread, a data-dense console, a transactional email — and states only what
+inverts there. Read a context only when its situation matches the task.
+Rules from the wrong context are contamination, not guidance.
 
-# register
+# cliche
 
-A condition-scoped contract: a situation — data-dense consoles, editorial
-pages, transactional email — where parts of the default rules invert. Each
-register names its condition first. Truths from the wrong register are
-poison, not context; gather a register only when its condition matches the
-task. This starter declares the kind and ships no register nodes: registers
-invert answered defaults, and the dials are not answered yet.
-
-# anti-goal
-
-What this package refuses, each reject paired with its replacement.
-`anti-goal.median` is the model's floor, not the brand's taste. Gather
-anti-goals before styling anything greenfield.
+The defaults a generative model falls back on when no brand is steering it.
+These are nobody's brand. Each entry pairs the tired move with the honest
+replacement. Gather before styling anything greenfield; enforced by paired
+checks at review.
 
 ---
 
-The ghost skill bundle teaches authoring — its `adapting-a-starter` recipe is
-the procedure for growing this skeleton into a real fingerprint: answer the
-dials, prune the median floor, edit your values, then generate refs and tells.
+The cover node (`brand.md`, declared in the manifest) is the one page always
+in context: what the brand is, its temperature, and the refusals only it
+makes. The ghost skill's `adapting-a-starter` recipe is the procedure for
+growing this skeleton into a real fingerprint: write the cover, answer each
+chapter's open question, prune the cliches your chapters absorb, then add
+materials and refs.

package/dist/init-payloads/vessel-light/anti-goal.tells.md

@@ -4,7 +4,9 @@ description: "Failure modes specific to this brand's own signature — gather al
 
 These are the near-misses of Vessel's own signature: outputs that got close
 enough to cite the brand and still missed it. Each reject names its
-replacement.
+replacement. When a tell fires, the fix direction is always toward the
+token, the role, or deletion — never toward adding a compensating style on
+top of the miss.
 
 Reject rectangular buttons. A rectangular button is not a variant; it is a
 different design system → controls take `--radius-control`, the pill.
@@ -21,9 +23,8 @@ Vessel; it is a different brand.
 Reject custom shadows that sit near a tier → the exact tier — card, popover,
 or modal — chosen by interaction importance.
 
-Reject borrowing `--shadow-btn` or `--shadow-kbd` for layout → component
-shadows belong to the primitives that own them; layout elevation comes from
-the three tiers.
+Reject borrowing `--shadow-btn` for layout → component shadows belong to the
+primitives that own them; layout elevation comes from the three tiers.
 
 Reject editorial display type in product UI, and product type timidity in
 editorial → each register keeps its own vocabulary; a modal title is not a

package/dist/init-payloads/vessel-light/checks/shape-matches-job.md

@@ -0,0 +1,43 @@
+---
+name: Shape matches the job
+description: Flags views composed for the wrong reader job — a form styled as a table, an announcement headline over a reviewable artifact, a live state presented as settled fact, a second primary, or a skeleton loader standing in for content.
+severity: high
+references:
+  - grammar.job
+  - grammar.deletion
+  - grammar.hierarchy
+---
+
+Apply this check to diffs that add or restructure a view. Classify the
+reader's job first — what they do next with the view — then judge the
+composition against the ref that job routes to. These flags catch the
+template-convergence failure: a plausible layout applied to a job it does
+not fit.
+
+Flag a view whose job routes to one ref but whose composition imitates
+another — a submit-and-done task laid out as a dashboard of cards, a
+records-scanning task rendered as prose sections, a stop-and-decide moment
+inlined into the page instead of interrupting it. (`grammar.job`)
+
+Flag an announcement headline in display or headline type above an artifact
+the reader will review — "Here's your draft", "Your plan is ready", "All
+set". The artifact opens the view; status lives in quiet metadata or
+nowhere. (`grammar.job`)
+
+Flag a live or ongoing value presented without its freshness — no timestamp
+or "updated" line in muted metadata near the figure. A moving value styled
+as a settled fact misleads. (`grammar.job`)
+
+Flag recommendation or verdict framing where the decision belongs to the
+reader and the system cannot honestly rank the options. Present the
+material; withhold the verdict. (`grammar.job`)
+
+Flag a second primary-variant action in a view, and flag a promoted primary
+on a view that honestly earns none — a steady status view, an open
+comparison. Zero is a valid spend of `--primary-budget`.
+(`grammar.hierarchy`)
+
+Flag skeleton loaders, placeholder shimmer, or staged construction where
+content will land — and any element that cannot name what breaks if it is
+removed. The fix is demotion or deletion, never more emphasis.
+(`grammar.deletion`)

package/dist/init-payloads/vessel-light/glossary.md

@@ -4,7 +4,6 @@ kinds:
   - name: signature
   - name: register
   - name: anti-goal
-    posture: guard
 ---
 
 # grammar

package/dist/init-payloads/vessel-light/grammar.color-roles.md

@@ -11,8 +11,8 @@ may not author around them. Raw color values are implementation detail, never
 product language.
 
 Author with semantic roles: `background`, `foreground`, `card`, `popover`,
-`primary`, `secondary`, `muted`, `accent`, `border`, `input`, `ring`, and the
-status roles. If a container needs a color, it first needs a role.
+`primary`, `secondary`, `muted`, `border`, `input`, `ring`, and the status
+roles. If a container needs a color, it first needs a role.
 
 The status roles — destructive, success, warning, info — exist only when
 meaning demands them. Destructive means destructive or error. Success means

package/dist/init-payloads/vessel-light/grammar.deletion.md

@@ -0,0 +1,35 @@
+---
+description: "The deletion pass — every element must name what breaks if it goes; the fix for a crowded view is always demotion or deletion, never more emphasis; surfaces arrive settled, with no skeleton theater. Gather as the final pass over any composition, and whenever a view feels crowded, busy, or dressed up."
+---
+
+Restraint is not a mood; it is a test every element has to pass. Before a
+view ships, run the pass: each label, divider, icon, caption, and helper
+line must name what breaks if it is removed. If nothing breaks, delete it.
+Convention is not a reason — "forms usually have this" keeps nothing.
+
+The test has a direction. When a view is crowded, or two elements compete
+for attention, the fix is always demotion or deletion — never adding
+emphasis to the loser. Raising the volume of one element to beat another
+starts an arms race the composition always loses; removing the weaker claim
+ends it.
+
+Some deletions we have already made, permanently: no decorative dividers
+where a gap step states the relationship; no icons that restate their
+adjacent label; no tooltips explaining obvious controls; no onboarding
+chrome on routine views; no credibility costume — a small factual source or
+timestamp line beats a dashboard of gauges.
+
+A view also arrives settled. No skeleton loaders, no placeholder shimmer
+promising content that is not there — a fake page is hedging rendered as UI.
+While work is genuinely pending, show the smallest true statement (a quiet
+loading state, per the motion doctrine's loop exception) and nothing else.
+When content lands, it lands in its final position: no reflow, no staggered
+construction, no element arriving late to shift its neighbors.
+
+Do: a settings page whose every row survives the what-breaks question, with
+one primary action and gaps doing the dividing. Never: the same page with
+icon-per-row decoration, a divider under every group, a progress shimmer on
+load, and a bolded second CTA competing for the eye.
+
+After everything deletable is gone, whatever remains is unmistakably the
+point.

package/dist/init-payloads/vessel-light/grammar.hierarchy.md

@@ -28,9 +28,13 @@ wants muted body or label, not a smaller custom font. If the prose needs
 emphasis, improve the sentence before adding a style.
 
 The control emphasis ladder is exactly five rungs: primary, secondary,
-outline, ghost, link. One primary action per view is the rule; everything
-else steps down the ladder. Primary is for the action the screen exists to
-complete — if two buttons both look primary, the hierarchy failed.
+outline, ghost, link. At most one primary action per view is the rule
+(`--primary-budget: 1`); everything else steps down the ladder. Primary is
+for the action the screen exists to complete — if two buttons both look
+primary, the hierarchy failed. And some views honestly earn none: a steady
+status view or an open comparison has no action the screen exists to
+complete, and promoting one anyway puts the system's thumb on the scale.
+Zero is a valid spend.
 Destructive is a meaning, not a rung: it is rare, it names the destructive
 act directly, and it is never borrowed for urgency, emphasis, or brand heat.
 
@@ -40,6 +44,12 @@ guidance, not decoration. Errors state facts next to the field that caused
 them — do not hide field errors in modals, toasts, or generic banners when
 the user needs to fix one input.
 
+Figures that will be compared or scanned — amounts, counts, dates in
+columns, any metric — set in tabular numerals (`--numeric-tabular`), with
+the unit tight to the number. Proportional figures in a data column wobble,
+and a wobbling column reads as sloppy arithmetic. Mono already carries this
+for machine detail; the rule extends to any numeric data in product UI.
+
 Balanced text is for headings and compact statements. Do not balance long
 body copy into jagged reading.
 

package/dist/init-payloads/vessel-light/grammar.job.md

@@ -0,0 +1,54 @@
+---
+description: "The routing rule — name the reader's job before composing anything; the job picks the ref to imitate and the register that applies, never the topic. Gather first for any new view, before structure exists."
+materials:
+  - materials/ref/composition.form.html
+  - materials/ref/composition.table.html
+  - materials/ref/composition.editorial.html
+  - materials/ref/composition.overlay.html
+  - materials/ref/composition.conversation.html
+  - materials/ref/email.html
+---
+
+Before any structure exists, name what the reader does next with the view.
+The topic never picks the shape; the reader's job does. A billing question
+is not "a billing page" — it is a form to fill, a table to scan, a decision
+to confirm, or a thread to continue, and each of those is a different
+composition. A view built for the wrong job does not merely look off; it
+misleads.
+
+The jobs and where they route:
+
+- **Fill something in** — settings, signup, any submit-and-done task → the
+  form ref. Stacked labels and fields, one submit, secondary escape.
+- **Scan and compare records** — lists, audits, anything with rows and
+  figures → the table ref, in the data-density register.
+- **Read a narrative** — a landing page, an announcement, a story → the
+  editorial ref, in the editorial register.
+- **Stop and decide** — a confirmation, a destructive act, a choice that
+  interrupts the task → the overlay ref. The decision is the view.
+- **Converse with the system** — an AI thread, an agent console, a prompt
+  composer → the conversation ref.
+- **Be notified elsewhere** — receipts, alerts, anything that lands in an
+  inbox → the email ref, in the email register.
+
+Read the request's verbs, not its nouns: "edit / set up / submit" routes to
+form; "compare / list / review the records" to table; "announce / tell the
+story" to editorial; "confirm / are you sure" to overlay; "ask / draft with
+me" to conversation. When two jobs fold into one request, build for the job
+the reader performs on this view, now — the other job is the next view. When
+a job fits none of these, compose from the grammar and say so; do not force
+the nearest ref.
+
+Three shapes lie about the job, and we refuse them everywhere:
+
+- A view whose content is an artifact the reader will review — a draft, a
+  filled form, a generated plan — leads with the artifact, never with an
+  announcement headline. "Here's your draft" in display type demotes the
+  actual deliverable; the artifact sitting there with its actions is the
+  statement that it is ready.
+- A view reporting a live or ongoing state carries its freshness — "updated
+  2 min ago" — in quiet metadata. Presenting a moving value as a settled
+  fact is a small lie the reader eventually catches.
+- A view where the decision belongs to the reader presents the material and
+  withholds the verdict. Recommendation framing on a choice the system
+  cannot honestly make is manufactured confidence, and it reads that way.

package/dist/init-payloads/vessel-light/index.md

@@ -5,33 +5,29 @@ materials:
 ---
 
 vessel-light is Vessel without the React package: the design language as a
-repo-local steering packet for agents writing raw HTML and CSS.
+steering packet for agents writing raw HTML and CSS.
 
 The contract is narrow. Style only with the tokens. Compose only with the
-closed sets the grammar enumerates. Imitate the refs when the task matches
-them — they are worked examples to copy from, not a framework to import.
+closed sets the grammar enumerates. Imitate the refs when the task matches —
+worked examples to copy from, not a framework to import.
 
-The corpus carries three trust tiers. Grammar and the median floor are law:
-safe to consume verbatim, unchanged by any adaptation. Signature nodes are
-dials awaiting your values: each states Vessel's current answer and stands
-until you replace it. Registers are conditions: editorial, email, and
-data-density each name the situation where parts of the default contract
-invert. Gather against the actual task and pull only the nodes whose
-conditions apply, because truths from the wrong register are poison, not
-context.
+Grammar and the median floor are safe verbatim, unchanged by any adaptation.
+Signature nodes state Vessel's current answer and stand until you replace
+them. Registers — editorial, email, and data-density — name the situations
+where parts of the default contract invert; pull only the nodes whose
+conditions match the task, because truths from the wrong register are
+poison, not context.
 
-The reset raises the floor; only the fingerprint escapes the median.
+Monochrome comes first. Status color is functional language — danger,
+success, warning, information — never atmosphere. Atmosphere is catered: a
+five-hue expression palette whose volume rises with the register, from
+charts-only in product to two hues in editorial, and never on controls.
 
-Monochrome comes first. Status color is functional language for danger,
-success, warning, and information — never atmosphere. Atmosphere exists, but
-it is catered: a five-hue expression palette whose volume rises with the
-register, from charts-only in product to two hues in editorial, and never on
-controls.
+It protects the taste that disappears when an agent freehands: quiet
+surfaces, deliberate spacing, one obvious action, restrained motion.
 
-The fingerprint protects the taste that disappears when an agent freehands:
-quiet surfaces, deliberate spacing, one obvious action, and restrained
-motion.
-
-When a requested UI is not covered by a ref, compose from the grammar. Do
-not invent a new styling system. If the result needs a new pattern, the new
-pattern should come from observed drift, not anticipation.
+Name the reader's job before composing anything — the job picks the ref and
+the register, never the topic. When a requested UI is not covered by a ref,
+compose from the grammar; do not invent a new styling system. Before
+anything ships, run the deletion pass: every element names what breaks if
+it goes, and the view arrives settled.

package/dist/init-payloads/vessel-light/manifest.yml

@@ -1,2 +1,3 @@
 schema: ghost.fingerprint-package/v1
 id: vessel-light
+cover: index

package/dist/init-payloads/vessel-light/materials/primitives.css

@@ -30,42 +30,24 @@ body {
   background: var(--muted);
   color: var(--foreground);
 }
-.surface--accent {
-  background: var(--accent);
-  color: var(--accent-foreground);
-}
-.surface--dark {
-  background: var(--surface-dark);
-  color: var(--surface-dark-text);
-  border-color: var(--surface-dark-border);
-}
 .surface--pad-xs {
-  padding: 8px;
+  padding: var(--gap-sm);
 }
 .surface--pad-sm {
-  padding: 12px;
+  padding: 12px; /* off-scale surface geometry: between --gap-sm and --gap-md */
 }
 .surface--pad-md {
-  padding: 16px;
+  padding: var(--gap-md);
 }
 .surface--pad-lg {
-  padding: 24px;
+  padding: var(--gap-lg);
 }
 .surface--radius-sm {
   border-radius: var(--radius-sm);
 }
-.surface--radius-md {
-  border-radius: var(--radius-md);
-}
-.surface--radius-lg {
-  border-radius: var(--radius-lg);
-}
 .surface--radius-surface {
   border-radius: var(--radius-surface);
 }
-.surface--radius-control {
-  border-radius: var(--radius-control);
-}
 .surface--border {
   border: 1px solid var(--border);
 }
@@ -121,9 +103,6 @@ body {
 .stack--align-end {
   align-items: flex-end;
 }
-.stack--align-baseline {
-  align-items: baseline;
-}
 .stack--justify-center {
   justify-content: center;
 }
@@ -143,25 +122,25 @@ body {
   color: var(--foreground);
   font-family: var(--font-sans);
   font-size: var(--text-body-size);
-  line-height: 1.625;
+  line-height: var(--text-body-line-height);
 }
 .text--display {
   font-size: var(--heading-display-font-size);
-  font-weight: 400;
-  line-height: 1;
+  font-weight: var(--heading-display-font-weight);
+  line-height: var(--heading-display-line-height);
   letter-spacing: var(--heading-display-letter-spacing);
 }
 .text--headline {
   font-size: var(--text-headline-size);
   font-weight: 400;
   line-height: 1.25;
-  letter-spacing: -0.025em;
+  letter-spacing: var(--text-heading-letter-spacing);
 }
 .text--title {
   font-size: var(--text-title-size);
   font-weight: 600;
   line-height: 1;
-  letter-spacing: -0.025em;
+  letter-spacing: var(--text-heading-letter-spacing);
 }
 .text--label {
   font-size: var(--label-font-size);
@@ -201,7 +180,7 @@ body {
   gap: var(--gap-sm);
   min-width: 0;
   height: var(--control-height);
-  padding: 8px 24px;
+  padding: var(--gap-sm) var(--gap-lg);
   border: 1px solid transparent;
   border-radius: var(--radius-control);
   background: var(--primary);
@@ -237,8 +216,8 @@ body {
   color: var(--primary-foreground);
 }
 .button--secondary {
-  background: var(--muted);
-  color: var(--foreground);
+  background: var(--secondary);
+  color: var(--secondary-foreground);
 }
 .button--ghost {
   background: transparent;
@@ -271,43 +250,27 @@ body {
   color: var(--muted-foreground);
   box-shadow: none;
 }
-.button--size-xs {
-  height: 24px;
-  padding: 4px 8px;
-  gap: var(--gap-xs);
-  font-size: 12px;
-}
 .button--size-sm {
   height: 32px;
-  padding: 6px 16px;
+  padding: 6px var(--gap-md);
   gap: 6px;
 }
 .button--size-lg {
   height: 40px;
-  padding: 8px 32px;
+  padding: var(--gap-sm) var(--gap-xl);
 }
 .button--icon,
-.button--icon-sm,
-.button--icon-xs,
-.button--icon-lg {
+.button--icon-sm {
   padding: 0;
 }
 .button--icon {
   width: var(--control-height);
   height: var(--control-height);
 }
-.button--icon-xs {
-  width: 24px;
-  height: 24px;
-}
 .button--icon-sm {
   width: 32px;
   height: 32px;
 }
-.button--icon-lg {
-  width: 40px;
-  height: 40px;
-}
 
 /* field — defaults: label plus pill input with input border, muted placeholder, ring focus, compact error. */
 .field {