Introducing a new way to review your PRs.

Read the announcement

twentyhq / twenty

The open alternative to Salesforce, designed for AI.

View on GitHub

22 documents · Updated Nov 20, 2026

docs / ui-component-system

UI component system

The UI component system is Twenty's shared React design layer. It gives product screens one set of theme, accessibility, layout, navigation, input, feedback, display, icon, and typography primitives. Feature code supplies domain meaning and state. The shared layer supplies the visual and interaction contract that keeps those features consistent.

System role

The system turns design rules into reusable controls and surfaces. Applications use it to show data, collect values, move between choices, and report system state without creating a separate interaction pattern for each feature.

The public twenty-ui package exposes two related layers:

LayerPurpose
PrimitivesFoundational controls and compound surfaces such as fields, buttons, selects, dialogs, popovers, and typography
Shared componentsProduct-ready combinations such as pickers, dropdowns, settings rows, banners, metrics, pagers, specialized inputs, and assistant avatars

Both layers receive content, labels, values, and callbacks from the application. The UI layer does not own the meaning of a CRM record, route, permission, or domain value. Focused subpath imports are preferred. The root package also re-exports the main public groups (packages/…/README.md• L53-84, packages/…/index.ts• L10-15, packages/…/index.ts• L10-17). The package exposes generated public API information for component and icon consumers (packages/…/components.ts• L104-1168, packages/…/public-exports.json• L1-24).

This relationship is the main mental model for the system:

flowchart LR
  T[Theme tokens and schemes] --> P[UI primitives]
  A[Accessibility and input rules] --> P
  P --> C[Shared components]
  F[Feature content and state] --> P
  F --> C
  C --> S[Consistent product screen]

Theme and accessibility

Theme and accessibility primitives set the conditions for every other component. Theme state provides the visual context. Accessibility helpers preserve meaning and keyboard access when a visual design uses a custom control.

Theme model

The theme model supports light and dark color schemes through shared CSS variables and JavaScript values. ThemeProvider applies a scheme to the document by default or scopes it to a subtree. A scoped provider can add local overrides without changing how components are used.

Theme values cover colors, spacing, type, icon sizes, borders, shadows, motion, layer order, and shape. Applications load the base style and scheme stylesheets once. Consumers that need values in JavaScript use useTheme; consumers outside normal DOM style resolution can pass an explicit theme such as THEME_LIGHT or THEME_DARK (packages/…/README.md• L86-94, packages/…/theme.md• L1-25). The provider also carries application scale and the nearest theme scope for portaled content. This keeps dialogs, popovers, date selectors, tooltips, and notifications in the visual context that opened them.

Theme tokens resolve from active CSS values when the browser can provide them. Numeric tokens use stable fallbacks when CSS is not available. This keeps CSS use and JavaScript use aligned across providers (packages/…/resolveThemeTokens.ts• L8-56, packages/…/computeThemeFromCss.ts• L4-18).

References: packages/…/theme.md• L1-29 packages/…/README.md• L86-94 packages/…/ThemeProvider.tsx• L22-30 packages/…/ThemeProvider.tsx• L76-125 packages/…/ThemeLight.ts• L1-18 packages/…/ThemeDark.ts• L1-18 packages/…/themeCssVariables.ts• L1-16 packages/…/themeTypes.ts• L1-15 packages/…/resolveThemeTokens.ts• L8-56 packages/…/computeThemeFromCss.ts• L4-18

Accessibility primitives

Accessibility primitives keep useful content available to assistive technology and give custom visual controls the behavior of native controls. VisuallyHidden hides content from the visual layout while keeping it available to assistive technology. The keyboard helper supports activation with Enter and Space for controls that are not native buttons.

Shared components use these primitives to provide roles, names, tab positions, focus behavior, and keyboard actions. Icon-only actions and custom rows must keep that contract when callers replace the rendered element. Labels and status text remain caller-owned so applications can supply the right language and context.

References: packages/…/index.ts• L10-12 packages/…/VisuallyHidden.tsx• L8-19 packages/…/handleClickableElementKeyDown.ts• L3-10 packages/…/label-ownership.md• L1-31

Reading direction

DirectionProvider supplies left-to-right or right-to-left reading direction to a UI subtree. Menus, dropdowns, tabs, avatar groups, date navigation, and other directional controls use it to keep order, alignment, keyboard movement, and directional icons meaningful.

Direction is shared with overlays and can be combined with a theme scope. A feature therefore does not need to pass direction through every nested control.

References: packages/…/DirectionProvider.tsx• L1-15 packages/…/DirectionProviderProps.ts• L1-3 packages/…/DirectionProvider.interactions.stories.tsx• L1-80 packages/…/DatePicker.tsx• L53-59 packages/…/DatePicker.module.scss• L27-32

Composition primitives

Composition primitives arrange content and provide the common surfaces around feature content. They define layout, movement, popup, and focus patterns while the feature retains ownership of data and business state.

Layout and surfaces

Layout primitives provide stable sections, separators, labeled dividers, collapsible areas, bounded resizing, and responsive overflow. Surface primitives provide cards and temporary layers such as dialogs, popovers, tooltips, and dropdown content.

Card is a compound surface with root, header, content, footer, control, and action parts. Its action part gives a card a native button-like action. Its control part marks content that belongs inside the card without making the whole card interactive. OverflowingList keeps visible items inline and moves hidden items into a popup. ResizeHandle gives panels a bounded keyboard and pointer resize contract. Dialogs preserve title and description relations. Tooltips remain usable from hover and keyboard focus.

References: packages/…/index.ts• L10-25 packages/…/index.ts• L10-18 packages/…/index.ts• L10-124 packages/…/Card.tsx• L1-15 packages/…/CardRoot.tsx• L11-39 packages/…/OverflowingList.tsx• L31-75 packages/…/ResizeHandle.tsx• L17-103

Navigation primitives represent movement between destinations and choices. Links, list items, menus, breadcrumbs, tabs, drawers, pagers, and dropdowns share states for active, focused, selected, disabled, and nested content.

ListItem is the common row model for labels, descriptions, icons, actions, shortcuts, selection markers, and submenu cues. Dropdown is the main compound choice surface. It supports search, actions, loading and empty states, grouped choices, nested pages, and single or multiple selection. Its content can bound scrolling, hide inactive pages, and show clear focus states for rows with actions. Right-to-left navigation mirrors directional back cues. The feature owns values and selected state. The dropdown owns popup focus, page history, keyboard movement, type-ahead, and dismissal.

Tabs provides a related choice pattern for switching panels. A tab can include an icon, a badge, a highlighted state, and one of three sizes. The plain variant uses the active indicator. The filled variant keeps a background behind the active tab. Tabs support horizontal and vertical layouts, controlled or uncontrolled selection, manual or automatic activation, disabled-tab skipping, anchor composition, and optional mounted panels. Their behavior keeps focus movement separate from selection until activation when manual activation is used (packages/…/Tabs.behavior.test.tsx• L39-111).

StepBar presents ordered progress through a multi-step flow. On narrow screens it shows only the active step, or the first step when no step is active. On wider screens it connects the steps and marks completed steps with a checkmark. Step content remains available for the current and completed steps.

CountPager provides a small, controlled previous and next flow for a known collection. It reports a polite position string and disables navigation at collection bounds.

References: packages/…/ListItem.tsx• L15-116 packages/…/DropdownRoot.tsx• L27-218 packages/…/useDropdownKeyboardNavigation.ts• L22-212 packages/…/Dropdown.module.scss• L1-186 packages/…/CountPager.tsx• L12-72 packages/…/TabsTab.tsx• L9-30 packages/…/TabsTabProps.ts• L7-18 packages/…/TabsVariant.ts• L1 packages/…/Tab.module.scss• L43-187 packages/…/Tabs.behavior.test.tsx• L39-233 packages/…/Tabs.stories.tsx• L94-306 packages/…/index.ts• L19-40 packages/…/StepBar.tsx• L19-56 packages/…/Step.tsx• L69-146

Shared component compositions

Shared components package stable combinations of primitives. They shorten common product patterns while leaving state and product meaning with the caller.

CompositionProduct role
FormFieldRowPresents a labeled setting or form value with optional icon, trailing content, hover state, and divider
DetailsRowPresents one label-value pair with an optional leading icon and action
SettingsRowJoins a setting label and description with a control such as a switch
ReactionButtonPresents an emoji reaction count with pressed state and a standard button contract
Pickers and steppersProvide domain-neutral country, currency, phone-country, date, number, emoji, and segmented choice patterns

These compositions are useful when the visual and interaction contract is stable across features. Domain-specific labels, permissions, and value rules remain outside the shared component.

References: packages/…/index.ts• L10-58 packages/…/index.ts• L10-35 packages/…/FormFieldRow.tsx• L14-89 packages/…/DetailsRow.tsx• L11-59 packages/…/ReactionButton.tsx• L8-41 packages/…/SettingsRow.tsx• L11-59

Interaction primitives

Interaction primitives cover actions and value entry. They share size, focus, disabled, loading, grouping, and responsive behavior so workflows use familiar controls.

Input controls

The input layer includes buttons, icon actions, fields, text inputs, text areas, checkboxes, radios, switches, sliders, selects, autocomplete, search, number entry, image upload, code editing, and specialized pickers. Compound controls separate their trigger, popup, option, value, and status parts so a feature can supply content without rebuilding keyboard behavior.

Field joins a label, control, description, error, and validity state. Button is the base action contract and can report loading or act as a link. InputGroup supplies shared size and adornment context to inputs. RadioGroup and SegmentedControl provide named mutually exclusive choice sets with responsive layouts.

Textarea supports controlled and uncontrolled values with optional auto-resize. SearchInput adds a search icon and optional actions while preserving accessible naming. Autocomplete, Select, and the country, currency, and phone-country pickers adapt the same choice pattern for common data sets.

Front-end SelectInput and MultiSelectInput use searchable dropdowns for single and multiple choice. They keep the selected value with the caller, show an explicit empty result, and can offer a new option only when the trimmed search text is non-empty and does not match an existing option. Multi-select keeps the dropdown open while users toggle several values.

DatePicker keeps the selected date separate from the viewed month. It supports unavailable dates, read-only browsing, highlighted ranges, localized header labels, custom headers, and right-to-left direction. Its calendar surface uses theme spacing and font tokens, and its selected or ranged days use the shared blue selection treatment (packages/…/DatePicker.module.scss• L1-8, packages/…/DatePicker.module.scss• L70-122). EmojiPicker provides a searchable, localized emoji catalogue and returns the selected Unicode string.

References: packages/…/index.ts• L10-177 packages/…/index.ts• L10-58 packages/…/Field.tsx• L1-15 packages/…/Input.tsx• L12-37 packages/…/RadioGroup.tsx• L9-29 packages/…/Textarea.tsx• L15-103 packages/…/SearchInput.tsx• L12-53 packages/…/DatePicker.tsx• L25-110 packages/…/DatePicker.module.scss• L1-122 packages/…/EmojiPicker.tsx• L16-63 packages/…/SelectInput.tsx• L12-108 packages/…/MultiSelectInput.tsx• L15-103 packages/…/AddSelectOptionDropdownSection.tsx• L8-45 packages/…/SelectInput.test.tsx• L24-60

Input state ownership

Controls can use local state or accept state from a caller. A controlled control reports changes to the caller. An uncontrolled control manages its initial value and later interaction locally. Popup visibility, selected value, viewed date, search text, and page state are separate concerns.

Searchable pickers match the text shown to the user and return stable selected identifiers. Country and phone-country search use shared normalization so accents and special letters do not prevent a match. Select inputs use the same search text to decide when a clear action or a new-option action is available. Date selection reports a canonical date-only value, while month browsing does not change that value. Drag behavior respects nested inputs, and shared utilities identify Ctrl-wheel input as a page-zoom gesture rather than a component action.

References: packages/…/DropdownRoot.tsx• L22-105 packages/…/CountrySelect.tsx• L24-171 packages/…/matchesPhoneCountrySearch.ts• L5-22 packages/…/DatePickerProps.ts• L8-18 packages/…/SelectInput.tsx• L31-105 packages/…/MultiSelectInput.tsx• L32-80 packages/…/AddSelectOptionDropdownSection.tsx• L21-43 packages/…/shouldPreventDragActivation.ts• L5-41 packages/…/isPageZoomGesture.ts• L1-3

Feedback primitives

Feedback primitives tell users what the system is doing and what needs attention. They separate progress, information, warning, success, empty, and error treatments from the feature that caused the state.

Feedback states

The feedback layer includes loaders, progress bars and rings, banners, callouts, inline banners, skeletons, empty states, error states, and toasts. Banner provides the base message surface with status, optional action, and optional dismissal. InlineBanner specializes that surface for content embedded in a page.

Progress communicates a known or unknown amount of work. ProgressBar accepts a caller-defined range and supports indeterminate progress, several sizes, color overrides, and reduced motion. Skeleton marks content that is not ready without presenting a false value. It can render as a block or inline placeholder, use a static or animated highlight, follow custom dimensions and corner shapes, and stay hidden from assistive technology. Its stories verify light and dark themes, right-to-left use, reduced-motion behavior, and composition with other content (packages/…/Skeleton.stories.tsx• L9-238). These states let a screen change from loading to real content without changing the surrounding layout contract.

The front-end EmptyState composition gives an empty screen a centered title, description, and action area. It can fit a defined width and enters with a short fade. The feature supplies the reason for the empty state and the actions that resolve it.

References: packages/…/index.ts• L10-37 packages/…/InlineBannerProps.ts• L1-12 packages/…/BannerComponent.tsx• L15-65 packages/…/ProgressBar.tsx• L12-60 packages/…/ProgressBarProps.ts• L3-9 packages/…/Skeleton.tsx• L9-45 packages/…/SkeletonProps.ts• L4-15 packages/…/Skeleton.stories.tsx• L9-238 packages/…/EmptyState.tsx• L4-62

Toast lifecycle

Toast notifications use a provider-scoped store. Features enqueue, close, or update entries through the toast API. Toaster renders active entries in the current theme and reading direction. A provider limit controls how many notifications can be shown at once.

Toast entries move from visible to closing and then to removed. An update can change a live entry from progress to success by its ID while preserving fields that the update does not mention. An exiting entry cannot be revived. Timers pause while the user points at or focuses the notification.

References: packages/…/ToastProvider.tsx• L9-19 packages/…/Toaster.tsx• L15-49 packages/…/updateToastInStore.ts• L9-48 packages/…/ToasterItem.tsx• L18-63

Content primitives

Content primitives give product data a stable visual form. They help screens show identity, status, labels, counts, structured values, links, icons, and text without repeating display rules.

Data display

Data-display primitives represent compact pieces of product information. Avatars, assistant avatars, badges, chips, tags, status markers, metrics, details rows, stacked icons, tinted icon tiles, command blocks, and JSON trees make repeated workspace values easy to scan.

Avatar provides an identity surface that can show an image, an icon, or a fallback initial. AssistantAvatar provides a themed assistant identity with fixed shapes, faces, sizes, and optional motion. Badge gives short statuses, counts, and markers a compact visual form. Chip presents a compact label with optional leading and trailing content, visual variants, click behavior, and bounded text. Its overflow path can expose the full label. DetailsRow and MetricRow present label-value information without deciding what the value means.

Compact values can truncate, clamp, or move into an overflow surface. The display contract must still provide a way to reach the full value. Feature code maps domain values into these forms and keeps ownership of their meaning.

References: packages/…/index.ts• L10-35 packages/…/Avatar.tsx• L11-60 packages/…/AssistantAvatar.tsx• L13-71 packages/…/Badge.module.scss• L1-72 packages/…/Chip.tsx• L15-89 packages/…/Chip.module.scss• L1-97 packages/…/DetailsRow.tsx• L11-59 packages/…/MetricRow.tsx• L12-61 packages/…/useJsonTreeContextOrThrow.tsx• L6-18

Icon vocabulary

The icon layer gives the product one named vocabulary for actions, objects, brands, relationships, and product concepts. Direct icon exports support typed use when the icon is known in advance. Icon supports string-based runtime lookup through IconsProvider and its provider-scoped catalog.

The icon dictionary groups concepts into data model, CRM, views, layouts, workspace and access, logic, AI, platform, and general categories. Each entry records when to use the concept and when to avoid it. The public catalog includes Tabler icons, brand assets, product illustrations, and custom assets. IconEuStars adds the EU stars mark as a theme-sized icon backed by the shared SVG asset (packages/…/eu-stars.svg• L1-14, packages/…/IconEuStars.tsx• L1-11).

The generated icon index exposes custom icons and the Tabler vocabulary through the same public boundary. Runtime lookup uses the provider catalog and falls back to a default icon when a name is unknown. The dictionary and export lists must stay aligned so a concept works both as a typed import and as a runtime name (packages/…/TablerIcons.ts• L1-471, packages/…/index.ts• L10-59, packages/…/index.ts• L527-538).

References: packages/…/Icon.tsx• L4-31 packages/…/IconsProvider.tsx• L10-21 packages/…/useIcons.ts• L6-20 packages/…/TwentyIconDictionary.ts• L4-40 packages/…/eu-stars.svg• L1-14 packages/…/IconEuStars.tsx• L1-11 packages/…/TablerIcons.ts• L1-471 packages/…/index.ts• L10-59 packages/…/index.ts• L527-538 packages/…/TwentyIconDictionary.test.ts• L20-63

Typography vocabulary

Typography primitives provide headings, labels, body text, links, shortcuts, and text containers. Heading keeps semantic heading level separate from visual size and color. Text supports shared size, weight, color, truncation, and line clamping values.

OverflowingTextWithTooltip gives truncated text a full-value view when it overflows. It preserves caller links, focus, reading direction, and the rendered element rather than adding an extra layout wrapper. Shortcut presents keyboard commands as keys, text, or button hints. It gives the visual sequence an accessible label and can hide desktop-only hints on mobile.

References: packages/…/index.ts• L10-22 packages/…/Heading.tsx• L8-27 packages/…/Text.tsx• L11-48 packages/…/OverflowingTextWithTooltip.tsx• L17-157 packages/…/Shortcut.tsx• L11-69 packages/…/Shortcut.module.scss• L1-47

Shared usage boundaries

The UI system owns presentation and common interaction behavior. Product modules own domain state, labels, permissions, routes, and the meaning of each value passed to a primitive.

When a feature needs a visual treatment, it should first use an existing primitive or shared composition. A new shared component is appropriate when the composition has a stable visual and interaction contract across features. Domain-specific rules should remain in the feature layer instead of becoming hidden assumptions in a generic component.

The UI system works beside the shared domain layer. Domain contracts describe what a value means. UI primitives describe how a user sees or changes it. See Shared platform and Client app shell for the wider package boundary and application shell context.

Change checklist

When these files or sections are changed, remember to consider these:

  • Theme token changes must keep generated light and dark JavaScript themes, CSS variables, runtime theme types, provider scopes, token fallbacks, scale behavior, and portaled content aligned.
  • Public barrel changes must keep root and subpath imports aligned with package exports, generated exports, and public documentation.
  • New shared components must have a stable public contract and must not move feature-specific domain rules into the UI package.
  • Input and field changes must preserve native roles, label and error relations, controlled and uncontrolled state, focus behavior, disabled state, and size variants.
  • Picker and dropdown changes must keep selected values, displayed labels, search text, empty and loading states, page history, resolved placement, bounded scrolling, hidden inactive pages, action-row focus, right-to-left cues, nested dismissal, and focus restoration aligned.
  • Select changes must keep clear actions and new-option actions consistent with normalized search text and existing-option checks.
  • Date picker changes must keep the selected date separate from the viewed month. Preserve date-only value rules, unavailable dates, range display, direction, and header labels.
  • Tabs changes must keep tab-panel relations, controlled selection, activation mode, disabled-tab navigation, indicator behavior, orientation, variant, and anchor composition aligned.
  • Step bar changes must keep active-step meaning, completed-step state, mobile visibility, connector display, and step content visibility aligned.
  • Icon changes must keep SVG assets, typed exports, Tabler aliases, runtime provider lookup, dictionary guidance, and generated references together.
  • Feedback changes must keep banner status, toast provider scope, notification limits, live-ID updates, exit state, reduced-motion behavior, skeleton accessibility, and reading direction aligned.
  • Progress changes must keep value range semantics, indeterminate behavior, accessible state, size variants, and reduced-motion behavior aligned.
  • Typography, shortcut, chip, and overflow changes must keep full-value access, shortcut labels and visibility, focus behavior, tooltip mode, link composition, hidden content state, and bounded layout aligned.

Important failure modes

TriggerConsequenceGuard
Generated theme values, CSS variables, and theme types drift apartComponents use missing tokens or disagree between CSS and JavaScriptRegenerate and review the light and dark token outputs as one contract
A scoped theme does not reach a popup or toasterThe overlay uses the wrong colors, scale, or contrastKeep portals tied to the nearest theme scope
A custom control loses its name, role, tab stop, or keyboard actionKeyboard and assistive-technology users cannot use itPreserve the complete accessibility contract when changing render targets
A field loses its label, description, or error relationUsers cannot identify the input or understand its invalid stateCompose the full Field contract around the control
A picker searches a different value from the displayed labelUsers cannot find a visible choice by its shown textKeep display labels and search text explicit and aligned
A select offers an existing hidden option as a new optionThe feature can create duplicate choicesCheck the trimmed option name against existing options before showing the add action
A date picker treats viewed month as the selected dateBrowsing changes product state or commits the wrong dayKeep selected date and viewed month as separate values
A dropdown page remains active after navigationFocus can move into stale or hidden contentRegister the active page and keep inactive content hidden or inert
A dropdown loses its bounded scroll or focus stateLong menus clip content or hide the active keyboard targetPreserve the content, section, and action-row layout states
A hidden overflow item stays focusableKeyboard users reach content that is not visibleKeep hidden items unavailable to focus and assistive technology
A mobile step bar renders every stepA narrow flow becomes crowded and loses the current-step focusRender the active step only on mobile and preserve the first-step fallback
A progress bar changes range or indeterminate handling without its accessible stateUsers see the wrong completion level or hear the wrong progressKeep minimum, maximum, value, and unknown-progress behavior aligned
A skeleton placeholder is exposed as page contentAssistive-technology users hear a false value or redundant loading contentKeep skeletons aria-hidden and replace them with real content in the same layout
A skeleton ignores reduced-motion settingsUsers who request less motion still see animated loading feedbackDisable the highlight animation when reduced motion is active
A toast update targets an exiting or removed entryA stale notification is revivedUpdate only live entries and keep exit completion separate
A tab change breaks tab-panel relations or separates focus from selection incorrectlyKeyboard users see the wrong panel or cannot activate a tabPreserve the tab behavior contract and its controlled state rules
A Tabler alias, custom icon, or SVG asset is not in the public indexTyped imports or runtime icon lookup failsKeep the asset, component, public index, and provider catalog aligned
A shortcut exposes visual keys without a usable accessible labelAssistive-technology users cannot identify the commandKeep the generated label and visual presentation separate
A chip or other truncated text has no overflow accessUsers cannot discover the full valueUse an overflow tooltip or another explicit full-value path

Key files

FileWhy to read it
packages/…/package.jsonDefines public package subpaths, CSS themes, peer boundary, and build output
packages/…/README.mdExplains the public package model, entry points, theming, and usage boundary
packages/…/theme.mdExplains root and scoped themes, explicit theme values, and portal context
packages/…/index.tsShows the shared component export boundary
packages/…/index.tsShows the primitive export boundary
packages/…/ThemeProvider.tsxShows theme scope, scheme, scale, and portal context
packages/…/index.tsShows the shared accessibility helpers
packages/…/DirectionProvider.tsxShows the reading-direction boundary
packages/…/TabsTab.tsxShows tab content, visual variants, and public tab state inputs
packages/…/Tabs.behavior.test.tsxShows the tab focus, activation, controlled state, disabled state, and panel guarantees
packages/…/StepBar.tsxShows responsive step visibility and active-step composition
packages/…/Step.tsxShows completed, current, and upcoming step states
packages/…/Card.tsxShows the compound card surface and its action/control distinction
packages/…/Dropdown.module.scssShows dropdown scrolling, page visibility, focus, grouping, and direction-aware surface states
packages/…/Field.tsxShows the label, control, description, error, and validity contract
packages/…/Input.tsxShows standalone and grouped input behavior
packages/…/SelectInput.tsxShows searchable single-select, clear, and add-option behavior
packages/…/MultiSelectInput.tsxShows searchable multi-select and repeated selection behavior
packages/…/AddSelectOptionDropdownSection.tsxShows the guard for offering a new select option
packages/…/SelectInput.test.tsxShows the select contract for hidden existing options and new options
packages/…/DatePicker.tsxShows date selection, month browsing, range display, and direction behavior
packages/…/DatePicker.module.scssShows the calendar layout, direction-aware navigation, and date states
packages/…/EmptyState.tsxShows the shared empty-screen title, description, and action composition
packages/…/ProgressBar.tsxShows the progress bar value and display contract
packages/…/Skeleton.tsxShows placeholder layout, animation, dimensions, and hidden accessibility state
packages/…/Skeleton.stories.tsxShows skeleton themes, motion, direction, layout, shape, and composition guarantees
packages/…/Chip.tsxShows compact label content, truncation, and overflow behavior
packages/…/Chip.module.scssShows chip sizing, variants, disabled state, and clickable state
packages/…/Shortcut.tsxShows shortcut presentation, accessible labels, variants, and mobile visibility
packages/…/Shortcut.module.scssShows shortcut key, text, and button-hint presentation
packages/…/TwentyIconDictionary.tsShows the product icon vocabulary and usage guidance
packages/…/TablerIcons.tsShows the public aliases for the shared Tabler icon set
packages/…/index.tsShows the generated public icon boundary, including custom icons