@capra/core 1.5.3 → 1.7.0

package/docs/core-autocompletefield--design.md

@@ -0,0 +1,91 @@
+# Core/AutocompleteField - Design
+
+AutocompleteField combines a text field with a suggestions list. Consumers can supply static `AutocompleteField.Item` children or an `items` collection with an optional default item renderer. The field allows custom values that are not in the list.
+
+## Anatomy
+
+1. **Text input** — Entry is through a standard text input. The field keeps focus while the list is open so typing and keyboard
+   navigation stay in one place.
+2. **ListBox** — Filtered results appear in a ListBox under the field.
+
+## Properties
+
+### Label
+
+A label is required for input fields and succinctly describes the field’s purpose. If another text element is acting
+as the label, like a section title, ensure the proper aria relationships are linked.
+
+### Placeholder text
+
+<p>
+  Placeholder text is visible until a character is entered.
+</p>
+
+<p>
+  Because the placeholder text disappears, putting instructions or requirements as placeholder text is not
+  accessible. Helper text is the preferred method to convey this information.
+</p>
+
+### Helper text
+
+Helper text is placed below the field and informs the user of any requirements, disclaimers, and errors. Helper text
+is shown persistently but is replaced by error text when an error occurs.
+
+### Layout
+
+There are two layouts available for text fields, vertical and horizontal. Vertical labels are the preferred layout,
+appearing above the field. Horizontal labels appear on the leading side of the field, and should only be used when
+space is limited.
+
+## Layout and spacing
+
+* Input renders identically to [TextField](?path=/docs/core-textfield--design).
+* Suggestions are presented using a ListBox.
+
+## Behavior
+
+### Autocomplete vs. Select
+
+<p>
+  **Autocomplete** is an input box with text hints that users can type freely into. Hints are presented and refined
+  ina selection list as the user types. Freeform entry is allowed.
+</p>
+
+<p>
+  **Select**
+
+   allows selecting options only among a given set of choices.
+</p>
+
+### Filtering
+
+As the user types into the text field options are filtered based on the value.
+
+## Best Practices
+
+Do:
+
+* Do show a "no results" message when the filter returns nothing.
+* Do support keyboard-only navigation of suggestions.
+
+Don't:
+
+* Don't use AutocompleteField for small mutually exclusive sets (about seven or fewer visible options) — use [RadioGroup](?path=/docs/core-radiogroup--design) or Select.
+* Don't use AutocompleteField for plain freeform text with no list validation — use [TextField](?path=/docs/core-textfield--design).
+* Don't require picking from the list while still allowing arbitrary text without explaining that behavior.
+
+## Accessibility
+
+* `role="combobox"` on the input, `aria-expanded` reflects list open state.
+* `aria-controls` references the suggestion list `id`.
+* `aria-activedescendant` references the currently focused suggestion.
+* Suggestion list: `role="listbox"`, each suggestion: `role="option"`.
+
+### Keyboard interaction
+
+* Keyboard interactions follow Select and ListBox.
+
+## Related components
+
+* [TextField](?path=/docs/core-textfield--design) — For freeform text without suggestions.
+* [RadioGroup](?path=/docs/core-radiogroup--design) — For small mutually exclusive option sets.

package/docs/core-autocompletefield--usage.md

@@ -0,0 +1,18 @@
+# Core/AutocompleteField - Usage
+
+AutocompleteField combines a text field with a suggestions list. Consumers can supply static `AutocompleteField.Item` children or an `items` collection with an optional default item renderer. The field allows custom values that are not in the list.
+
+| Prop | Type | Required | Default | Description |
+| --- | --- | --- | --- | --- |
+| `canClear` | `boolean` | No | `--` | Whether to show a clear button for the input. |
+| `children` | `React.ReactNode \| ((     values: T & {       defaultChildren: React.ReactNode \| undefined;     },   ) => React.ReactNode)` | No | `--` | The children to render in the dropdown. |
+| `itemFilter` | `(textValue: string, inputValue: string) => boolean` | No | `--` | A function that filters the items based on the input value. |
+| `onChange` | `(value: string) => void` | No | `--` | A callback function that is called when the input value changes. |
+| `onOpenChange` | `(isOpen: boolean) => void` | No | `--` | A callback function that is called when the dropdown is opened or closed. |
+| `items` | `AutocompleteItem[]` | No | `--` | The items to display in the dropdown. |
+| `value` | `AutocompleteItem['value']` | No | `--` | The value of the input. |
+| `shouldAutoSizeDropdown` | `boolean` | No | `--` | Whether to automatically size the dropdown to the width of the input. Defaults to `true` |
+| `FORCE__className` | `string` | No | `--` | 🚨 This prop is meant to be an escape hatch. 🚨<br><br>If the desired style cannot be achieved using component props, use this as a last resort. The inner workings of Capra components are implementation details and this escape hatch gives one access to those implementation details. We cannot make any guarantees that styles will applied correctly across version updates. Please use it responsibly.<br><br>Add a CSS class to the component. |
+| `helperText` | `string` | No | `--` | Helper text below the field. Replaced by error message when status is error. Use for requirements, disclaimers. |
+| `label` | `string` | No | `--` | Label for the field. Required for accessibility; use aria-label if another element acts as label. |
+| `layout` | `'vertical' \| 'horizontal'` | No | `--` | Label and field layout: vertical (label above) or horizontal (label on leading side). Prefer vertical; use horizontal when space is limited. |

package/docs/core-badge--design.md

@@ -0,0 +1,70 @@
+# Core/Badge - Design
+
+Badges display an indicator/counter on an associated component.
+
+## Properties
+
+### Label
+
+A label is required to indicate the number of notifications.
+
+### Size
+
+Badges come in 3 sizes to support ones, tens, and values above 100.
+
+### Dot
+
+Use a dot to show notifications without a count.
+
+### Appearance
+
+Badges can be colored based on their status. The `attention` appearance is the general purpose color used for numbered badges and does not necessarily communicate severity.
+
+Using color as the only means to communicate status should be avoided (WCAG SC 1.4.1: Use of Color, Level A). Badges that communicate status must be accompanied by supplementary information that clearly communicates the status.
+
+## Behavior
+
+### Corner attachment
+
+Badges are placed in the top-right of the parent component to avoid obscuring the parent content.
+
+### Inline
+
+When used with text labels, badges are placed on the trailing side and vertically aligned to the text's line height.
+
+## Content
+
+### Maximum
+
+The maximum number shown in 99. When there are more than 99 notifications a "+" is appended to the label.
+
+## Best Practices
+
+Do:
+
+* Do cap displayed values at 99 with a "99+" label.
+* Do use the dot variant for simple presence indicators.
+* Do include count context in the parent's accessible label.
+
+Don't:
+
+* Don't use Badge for semantic status text — use Pill.
+* Don't use Badge for labels or tags — use Tag.
+* Don't place Badge on non-interactive decorative elements.
+* Don't use Badge colors as the only method to communicate status.
+
+## Accessibility
+
+* The badge is a nested static element; it is announced as part of its parent.
+* The parent element's accessible label should include the count context (e.g., "Notifications, 5 unread").
+* Use `aria-live="polite"` on the parent for dynamic badge updates.
+
+## Content
+
+* Numeric only.
+* Max displayed value: 99; use "99+" for larger counts.
+
+## Related components
+
+* [Pill](?path=/docs/core-pill--design) — For semantic status labels.
+* [Tag](?path=/docs/core-tag--design) — For removable text chips.

package/docs/core-badge--usage.md

@@ -0,0 +1,13 @@
+# Core/Badge - Usage
+
+Badges display an indicator/counter on an associated component.
+
+| Prop | Type | Required | Default | Description |
+| --- | --- | --- | --- | --- |
+| `variant` | `'counter' \| 'dot'` | No | `--` | The variant of the badge. 'counter' displays a count, 'dot' displays only a dot.<br>@default 'counter' |
+| `appearance` | `'danger' \| 'info' \| 'success' \| 'warning'` | No | 'danger' | Controls the Badge color.<br>@default 'danger' |
+| `count` | `number` | No | 0 | The number to display in the badge. Default is 0. |
+| `showZero` | `boolean` | No | false | Whether to display the badge when the count is zero. Default is false. |
+| `overflowCount` | `number` | No | 99 | The number to display in the badge when the count is greater than the overflow count. Default is 99. |
+| `FORCE__className` | `string` | No | `--` | 🚨 This prop is meant to be an escape hatch. 🚨<br><br>If the desired style cannot be achieved using component props, use this as a last resort. The inner workings of Capra components are implementation details and this escape hatch gives one access to those implementation details. We cannot make any guarantees that styles will applied correctly across version updates. Please use it responsibly.<br><br>Add a CSS class to the component. |
+| `aria-live` | `React.AriaAttributes['aria-live']` | No | `--` | `--` |

package/docs/core-breadcrumbs--design.md

@@ -0,0 +1,65 @@
+# Core/Breadcrumbs - Design
+
+Renders a breadcrumb trail with built-in support for collection behavior, keyboard support, and current-page semantics. Wrap items with {@link Breadcrumb}. The last item should represent the current page (typically without an `href`).
+
+## Usage
+
+Use Breadcrumbs on views that sit deeper than the home or root level so people see where they are in the hierarchy and can jump to ancestors.
+
+Place them above the page title, keep labels aligned with each destination's title, and render every segment except the current page as a link.
+
+## Layout and spacing
+
+* Place above the page heading.
+
+## Behavior
+
+* Current page item is not a link (no click interaction).
+
+## Content
+
+* Use the same label as the page heading for each item.
+* Title case.
+* Keep each label concise (1-3 words).
+
+## Best Practices
+
+Do:
+
+* Do make all items except the last one clickable links.
+* Do mark the current page with `aria-current="page"`.
+
+Don't:
+
+* Don't show breadcrumbs on top-level pages — there is no trail to show.
+* Don't use breadcrumbs when the IA is flat and would produce a single segment.
+* Don't use custom separator text that is read by screen readers.
+
+## Accessibility
+
+* Wrap in a `<nav aria-label="breadcrumb">` element.
+* Current page item uses `aria-current="page"`.
+* Separator characters are `aria-hidden="true"`.
+
+### Keyboard interaction
+
+| Key           | Function                                                                                                                                                                                                |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Tab`         | Move focus forward along the breadcrumb trail.                                                                                                                                                          |
+| `Shift + Tab` | Move focus back along the breadcrumb trail.                                                                                                                                                             |
+| `Enter`       | Activates the currently focused link. If a dropdown crumb has focus, opens the menu and gives focus to the currently selected option. If a menu item has focus, activates the item and closes the menu. |
+| `Space`       | If a dropdown crumb has focus, opens the menu and gives focus to the currently selected option.                                                                                                         |
+| `Down Arrow`  | If a dropdown crumb has focus, opens the menu and gives focus to the currently selected option. If a menu item has focus, moves focus to the next item.                                                 |
+| `Up Arrow`    | If a menu item has focus, moves focus to the previous item.                                                                                                                                             |
+| `Esc`         | If a dropdown crumb is open, closes the menu and returns focus to the trigger.                                                                                                                          |
+
+* If a dropdown crumb is open: the `tab` and `shift`+`tab` keys do not navigate.
+
+### Labeling
+
+* Breadcrumbs represent a hierarchy and need to announce themselves accordingly. Using `aria-label`, a crumb should identify itself and its parents.
+* Use `aria-current=”page”` to indicate the last page in the breadcrumb order.
+
+## Related components
+
+* [TabNav](?path=/docs/core-tabnav--design) — For in-page section navigation.

package/docs/core-breadcrumbs--usage.md

@@ -0,0 +1,16 @@
+# Core/Breadcrumbs - Usage
+
+Renders a breadcrumb trail with built-in support for collection behavior, keyboard support, and current-page semantics. Wrap items with {@link Breadcrumb}. The last item should represent the current page (typically without an `href`).
+
+:::warning[Partially implemented]
+
+The `Breadcrumbs` component is partially implemented and does not yet support dropdowns as items.
+
+:::
+
+| Prop | Type | Required | Default | Description |
+| --- | --- | --- | --- | --- |
+| `FORCE__className` | `string` | No | `--` | 🚨 This prop is meant to be an escape hatch. 🚨<br><br>If the desired style cannot be achieved using component props, use this as a last resort. The inner workings of Capra components are implementation details and this escape hatch gives one access to those implementation details. We cannot make any guarantees that styles will applied correctly across version updates. Please use it responsibly.<br><br>Add a CSS class to the component. |
+| `aria-label` | `string` | No | 'Breadcrumb' | Accessible name for the breadcrumb navigation landmark.<br>Defaults to `"Breadcrumb"`. |
+| `size` | `string` | No | 'md' | `--` |
+| `shouldEmpasizeCurrent` | `boolean` | No | true | `--` |

package/docs/core-button--design.md

@@ -0,0 +1,97 @@
+# Core/Button - Design
+
+Primary interactive element displaying text and supporting leading and trailing icons.
+
+## Usage
+
+Use a Button when someone needs to submit a form, confirm an action, or move a workflow forward, and the action warrants a dedicated, labeled control.
+
+Use at most one primary (`variant="primary"`) button per view or modal for the main outcome. Pair it with a secondary (`variant="secondary"`) button for cancel or alternate paths. Use `appearance="danger"` with primary or secondary for destructive or irreversible actions.
+
+## Properties
+
+### Variant
+
+| Variant     | Usage                                                                 |
+| ----------- | --------------------------------------------------------------------- |
+| `primary`   | Highest visual weight. Use once per view for the main action.         |
+| `secondary` | Pairs with a primary button for cancel or alternative paths.          |
+| `tertiary`  | Lowest visual weight. Use for supplementary or de-emphasized actions. |
+
+### Label
+
+Labels should use a verb + noun structure to describe what the button will do when pressed.
+
+### Icon
+
+Buttons have two icon slots; a leading and a trailing icon. Use the leading icons to visually reinforce their meaning and draw attention.
+
+Trailing icons are used for disclosure and additional behavior indications.
+
+### Size
+
+Buttons come is three different sizes. Medium is the default and preferred size for most situations.
+
+Small size is used when a button is inline with another element, such as a table or popover.
+
+### Appearance
+
+| Appearance | Default | Usage                                                       |
+| ---------- | ------- | ----------------------------------------------------------- |
+| `default`  | ✓       | Standard interactive actions.                               |
+| `neutral`  |         | Lower-prominence secondary actions within a filled surface. |
+| `danger`   |         | Destructive or irreversible actions (delete, revoke).       |
+
+### Size
+
+| Size | Default | Usage                                               |
+| ---- | ------- | --------------------------------------------------- |
+| `sm` |         | Compact toolbars, table row actions, dense layouts. |
+| `md` | ✓       | Standard form actions, modal footers.               |
+| `lg` |         | Call-to-action in empty states, hero sections.      |
+| `xl` |         | Marketing or onboarding hero sections.              |
+
+## Content
+
+* Use verb-first labels: "Save changes", "Add item", "Delete record".
+* Title case for all button labels.
+* Keep labels to 1-3 words when possible. Never exceed 5 words.
+* Use "Add" not "New" (e.g., "Add source", not "New source").
+* Avoid vague labels like "OK" or "Submit" — be specific about the action.
+
+## Behavior
+
+* Activated with mouse click, Enter key, or Space key.
+* Pending state (`pending` prop): replaces the leading icon or prepends a spinner while an async action is in progress; preserve button width to avoid layout shift.
+* Disabled state: buttons with `disabled` prop are non-interactive and non-focusable; use `aria-disabled` if the button should remain focusable (e.g., with a tooltip explaining why it's disabled).
+
+## Best Practices
+
+Do:
+
+* Do use a single `variant="primary"` button per view.
+* Do pair primary with secondary for confirm/cancel patterns.
+* Do use `appearance="danger"` for destructive actions.
+* Do use verb-first, title-case labels.
+
+Don't:
+
+* Don't use a Button for navigation to another page — use [Link](?path=/docs/core-link--design) or [Anchor](?path=/docs/core-anchor--design).
+* Don't use a Button for text-only inline navigation — use [Link](?path=/docs/core-link--design).
+* Don't use a Button for icon-only actions — use [IconButton](?path=/docs/core-iconbutton--design).
+* Don't use two primary buttons side by side.
+* Don't truncate button labels.
+* Don't disable a button without explaining why (use `aria-disabled` with a tooltip).
+
+## Accessibility
+
+* Always provide a visible text label; if the design requires a short label, add `aria-label` for context.
+* For icon-only use cases, use [IconButton](?path=/docs/core-iconbutton--design) instead (which enforces an accessible label).
+* Tab / Shift+Tab to focus. Enter or Space to activate.
+* The pending state must be communicated to assistive technology (e.g., `aria-label="Saving..."` when `pending` is true).
+
+## Related components
+
+* [IconButton](?path=/docs/core-iconbutton--design) — For icon-only actions.
+* [Link](?path=/docs/core-link--design) — For inline text navigation.
+* [Modal](?path=/docs/core-modal--design) — Buttons typically appear in modal footers for confirm/cancel patterns.

package/docs/core-button--usage.md

@@ -0,0 +1,17 @@
+# Core/Button - Usage
+
+Primary interactive element displaying text and supporting leading and trailing icons.
+
+| Prop | Type | Required | Default | Description |
+| --- | --- | --- | --- | --- |
+| `children` | `string` | Yes | `--` | The `label` for the button. |
+| `variant` | `(typeof variants)[number]` | No | 'secondary' | Which button style to use. Defaults to `secondary`. |
+| `appearance` | `(typeof appearances)[number]` | No | 'default' | Appearance to apply to the button. Defaults to `default`. |
+| `size` | `(typeof sizes)[number]` | No | 'md' | Size of the button. Defaults to `md`. |
+| `disabled` | `boolean` | No | false | Whether the button is disabled. |
+| `pending` | `boolean` | No | false | Whether the button is in a pending state. |
+| `leadingIcon` | `SvgIcon` | No | `--` | Icon to display before the button text. |
+| `trailingIcon` | `SvgIcon` | No | `--` | Icon to display after the button text. |
+| `block` | `boolean` | No | `--` | Whether to display the button as a block-level (full-width) component. Defaults to `false`. |
+| `onClick` | `React.ComponentProps<'button'>['onClick']` | No | `--` | Click handler for the button. |
+| `FORCE__className` | `string` | No | `--` | 🚨 This prop is meant to be an escape hatch. 🚨<br><br>If the desired style cannot be achieved using component props, use this as a last resort. The inner workings of Capra components are implementation details and this escape hatch gives one access to those implementation details. We cannot make any guarantees that styles will applied correctly across version updates. Please use it responsibly.<br><br>Add a CSS class to the component. |

package/docs/core-buttonlink--design.md

@@ -0,0 +1,7 @@
+# Core/ButtonLink - Design
+
+Primary interactive element displaying text and supporting leading and trailing icons.
+
+`ButtonLink` follows the design guidelines for [`Button`](?path=/docs/core-button--design) and uses [`Link`](?path=/docs/core-link--design) interally. Use it when you need a link styled as a button.
+
+See those pages for more details on the properties and usage of `ButtonLink`.

package/docs/core-buttonlink--usage.md

@@ -0,0 +1,24 @@
+# Core/ButtonLink - Usage
+
+Primary interactive element displaying text and supporting leading and trailing icons.
+
+| Prop | Type | Required | Default | Description |
+| --- | --- | --- | --- | --- |
+| `children` | `string` | Yes | `--` | The `label` for the link. |
+| `variant` | `(typeof variants)[number]` | No | 'secondary' | Which visual style to use. Defaults to `secondary`. |
+| `appearance` | `(typeof appearances)[number]` | No | 'default' | Appearance to apply to the link. Defaults to `default`. |
+| `size` | `(typeof sizes)[number]` | No | 'md' | Size of the link. Defaults to `md`. |
+| `disabled` | `boolean` | No | false | Whether the link is disabled. |
+| `pending` | `boolean` | No | false | Whether the link is in a pending state. |
+| `leadingIcon` | `SvgIcon` | No | `--` | Icon to display before the link text. |
+| `trailingIcon` | `SvgIcon` | No | `--` | Icon to display after the link text. |
+| `block` | `boolean` | No | `--` | Whether to display the link as a block-level (full-width) component. Defaults to `false`. |
+| `as` | `As` | No | `--` | The underlying element rendered by the component. Defaults to `a`. |
+| `href` | `unknown` | No | `--` | A URL to link to. See [MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#href). |
+| `hrefLang` | `string` | No | `--` | Hints at the human language of the linked URL. See[MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#hreflang). |
+| `target` | `HTMLAttributeAnchorTarget` | No | `--` | The target window for the link. See [MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#target). |
+| `rel` | `string` | No | `--` | The relationship between the linked resource and the current page. See [MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/rel). |
+| `download` | `boolean \| string` | No | `--` | Causes the browser to download the linked URL. A string may be provided to suggest a file name. See [MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#download). |
+| `referrerPolicy` | `HTMLAttributeReferrerPolicy` | No | `--` | How much of the referrer to send when following the link. See [MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#referrerpolicy). |
+| `routerOptions` | `unknown` | No | `--` | Options for the configured client side router. |
+| `FORCE__className` | `string` | No | `--` | 🚨 This prop is meant to be an escape hatch. 🚨<br><br>If the desired style cannot be achieved using component props, use this as a last resort. The inner workings of Capra components are implementation details and this escape hatch gives one access to those implementation details. We cannot make any guarantees that styles will applied correctly across version updates. Please use it responsibly.<br><br>Add a CSS class to the component. |

package/docs/core-card--design.md

@@ -0,0 +1,100 @@
+# Core/Card - Design
+
+The base component for the card.
+
+## Usage
+
+Use a Card to group related content—title, optional description, body, actions, and footer—into one scannable unit, often in grids or lists of similar items.
+
+Treat the card as a container: put links and buttons inside slots rather than making the whole surface ambiguous.
+
+## Properties
+
+### Title
+
+<p>
+  All cards must have a title identifying their content purpose. Use sentence case.
+</p>
+
+<p>
+  Card titles are wrapped by an `h2` by default, but can change based on their hierarchy within the page. Be sure to
+  note the heading level in your design file. The header's visual presentation remains the same regardless of
+  heading level.
+</p>
+
+### Description
+
+<p>
+  Optional. The description gives additional context to the contexts of the card. Descriptions should be brief,
+  taking up no more than a single line.
+</p>
+
+### Actions
+
+<p>
+  Contextual actions act on the main content area but keep the user's workflow within the card. Common examples
+  would be controls that act upon data visualizations, such as a View Switcher and range selections.
+</p>
+
+<p>
+  Supporting, non-interactive, data can also be displayed in this space.
+</p>
+
+### Content
+
+<p>
+  The primary content of the card. This is generally "one thing", though that could be a complex element such as a
+  graph or form.
+</p>
+
+### Footer
+
+<p>
+  Place actions or supplementary information to the primary content in the card's footer.
+</p>
+
+<p>
+  Actions placed here (e.g., a submit button for a form) take the user's workflow out of the card. There should be
+  an explicit indication of completion within the context of the card when the action is taken.
+</p>
+
+## Layout and spacing
+
+* Padding: `spacing.xl` on all sides (standard), `spacing.lg` for compact cards.
+* Title and description: `spacing.sm` gap between them.
+* Title/description block and content: `spacing.lg` gap.
+* Border: `shape.border.default`, `shape.radius.xl`.
+* Background: `color.background.panel.solid`.
+
+## Behavior
+
+* Cards are static containers by default.
+* If the entire card is interactive (e.g., a selectable card), use `role="button"` with keyboard support. Prefer [RadioTile](?path=/docs/core-radiotile--design) for selection scenarios.
+
+## Content
+
+* Title: sentence case, noun phrase.
+* Description: optional; one short line, sentence case with punctuation if needed.
+* Action labels: verb-first, title case.
+
+## Best Practices
+
+Do:
+
+* Do include a title in every card.
+* Do use the footer slot for secondary metadata (timestamps, status).
+
+Don't:
+
+* Don't make the entire card surface the only navigation affordance — put a [Link](?path=/docs/core-link--design) or [Button](?path=/docs/core-button--design) inside the content.
+* Don't use Card for tabular data — use a table.
+
+## Accessibility
+
+* Card titles are typically wrapped at an `h2` by default; choose the heading level (`h2`–`h6`) to match the page outline. Note the intended level in design specs—the visual style stays the same across levels.
+* If the card is a landmark region, wrap with `<section aria-labelledby>`.
+
+## Related components
+
+* [RadioTile](?path=/docs/core-radiotile--design) — For selectable card options.
+* [Modal](?path=/docs/core-modal--design) — For focused overlay containers.

package/docs/core-card--usage.md

@@ -0,0 +1,5 @@
+# Core/Card - Usage
+
+The base component for the card.
+
+## Card

package/docs/core-checkbox--design.md

@@ -0,0 +1,66 @@
+# Core/Checkbox - Design
+
+Checkbox component for capturing boolean user input. Supports controlled and uncontrolled modes with proper accessibility.
+
+## Usage
+
+Use a Checkbox when people can turn several options on or off independently within a group, and those choices apply when the form is submitted (or in another explicit save step).
+
+Use a visible group heading and stack options so each label stays associated with its control. Use `indeterminate` on a parent checkbox when a tree or grouped list is partially selected.
+
+## Properties
+
+### Label
+
+A label is required for all checkboxes. They should be short and represent a value or yes/no decision. Ensure
+`aria-label` or `aria-labelledby` is used if the checkbox label is not immediately associated with the control.
+
+### Checked
+
+A checkbox can be unchecked, checked, or in an indeterminate state
+
+### Disabled
+
+A checkbox can be disabled in any state if there is a prerequisite to enable the selection.
+
+## Content
+
+* Sentence case labels.
+* Describe the option, not the action (e.g., "Send email notifications", not "Enable email").
+
+## Behaviour
+
+### Single choice
+
+A single discrete checkbox can be used for yes/no decisions within a form.
+
+### Overflow
+
+Labels will wrap if they are wider than the parent container. The checkbox remains aligned to the top of the text
+box.
+
+## Best Practices
+
+Do:
+
+* Do use checkboxes for multi-select form options.
+* Do use `indeterminate` for parent checkboxes in tree structures.
+* Do provide a group heading for checkbox groups.
+
+Don't:
+
+* Don't use Checkbox for settings that apply immediately without submit — use Switch.
+* Don't use Checkbox for mutually exclusive options — use RadioGroup.
+* Don't use a lone Checkbox as a single on/off setting that applies immediately — use Switch.
+
+## Accessibility
+
+* `role="checkbox"`, `aria-checked` (including "mixed" for indeterminate).
+* Associate label using `<label for>` or wrapping `<label>`.
+* Checkbox group must have a group heading using `role="group"` with `aria-labelledby`.
+* Keyboard: Tab / Shift+Tab moves focus; Space or Enter toggles state when the checkbox is focused.
+
+## Related components
+
+* [Switch](?path=/docs/core-switch--design) — For immediate binary settings.
+* [RadioGroup](?path=/docs/core-radiogroup--design) — For mutually exclusive selections.

package/docs/core-checkbox--usage.md

@@ -0,0 +1,34 @@
+# Core/Checkbox - Usage
+
+Checkbox component for capturing boolean user input. Supports controlled and uncontrolled modes with proper accessibility.
+
+| Prop | Type | Required | Default | Description |
+| --- | --- | --- | --- | --- |
+| `indeterminate` | `boolean` | No | `--` | Whether the checkbox is in an indeterminate state. |
+| `checked` | `boolean` | No | `--` | Controlled checked state. Use with onChange for controlled component. |
+| `defaultChecked` | `boolean` | No | `--` | Default checked state for uncontrolled component. |
+| `children` | `string \| React.ReactNode` | No | `--` | The label for the checkbox. |
+| `FORCE__className` | `string` | No | `--` | 🚨 This prop is meant to be an escape hatch. 🚨<br><br>If the desired style cannot be achieved using component props, use this as a last resort. The inner workings of Capra components are implementation details and this escape hatch gives one access to those implementation details. We cannot make any guarantees that styles will applied correctly across version updates. Please use it responsibly.<br><br>Add a CSS class to the component. |
+
+## Integration Notes
+
+### Ant Design Form Compatibility
+
+When using Checkbox inside an Ant Design `<Form>` component, the focus ring may appear incorrectly due to Ant Design's global CSS:
+
+```css
+.ant-form input[type='checkbox']:focus {
+  outline-offset: -2px;
+}
+```
+
+Capra's Checkbox includes `!important` on its focus styles to override this, but if you encounter issues, add a local override where you're using this component:
+
+```css
+.checkbox {
+  input[type='checkbox']:focus,
+  input[type='checkbox']:focus-visible {
+    outline-offset: 2px !important;
+  }
+}
+```