Prototype design system.

Usage rules

• Use for every signed-in application page.
• Do not recreate a local header inside a page.
• Add final menus through navItems or the nav slot.
• Disable sticky only in isolated pattern previews.

Usage rules

• Use in global layouts, not inside pages.
• Limit to cross-application utility destinations.
• Add future utility pages through the links prop.

Usage rules

• Use in the header and any user-account context.
• Wire actions through events, not directly inside the component.
• Do not duplicate this popover in pages.

Usage rules

• Use for secondary section navigation.
• Place it in the first three columns of the 12-column grid at 2xl.
• Change the active color through the token, not inside the component.
• Keep item selection scrolling to the page top unless a page owns a custom scroll target.
• Keep the sticky offset tokenized so it tracks the application header height.

Usage rules

• Use for the main content of application views with side navigation.
• Do not recreate the content grid in every page.
• Remove debug once real content is wired.

Usage rules

• Use for a compact overview of catalogue metadata quality.
• Keep classification rules in the shared helper, not inside the pattern.
• Use legend clicks only to announce filter intent until the catalogue filter UI exists.
• Use semantic color tokens for every segment and legend item.

Usage rules

• Use for compact sales performance on dashboard cards.
• Keep sales aggregation in the shared helper, not inside the pattern.
• Use UiTrendAreaChart for the chart so the animation and accessibility stay centralized.
• Use text metrics and comparison badges so the chart is not the only source of information.

Usage rules

• Use for compact channel mix summaries on dashboard cards.
• Keep sales aggregation in the shared helper, not inside the pattern.
• Use UiDonutChart for the chart so rendering and accessibility stay centralized.
• Use legend clicks only to announce filter intent until catalogue filtering exists.

Usage rules

• Use below catalogue summary cards when the page needs to list real publications.
• Pass raw CatalogBook records and keep normalization in utils/publicationListItems.ts.
• Do not duplicate publication card or table markup inside pages.
• Keep filtering, sorting, and pagination route-backed so the list survives reloads.

Usage rules

• Use only with a normalized PublicationListItem.
• Keep row width controlled by the parent list.
• Do not add local status colors; use UiBadge variants.
• Add actions only after publication destinations and behaviours are defined.

Usage rules

• Use only with a normalized PublicationListItem.
• Use inside AppPublicationListSection compact mode, not directly in pages.
• Keep actions as UiButton instances until real publication destinations are defined.
• Keep long labels truncated so compact grids never create horizontal overflow.

Usage rules

• Use only with normalized PublicationListItem records.
• Keep sorting in utils/publicationListItems.ts instead of duplicating comparators in views.
• Use UiTableActionCell for prepared actions so constrained widths keep actions reachable.
• Do not add real publication actions until the publication routes and behaviours are defined.

Usage rules

• Use for ranked sales modules where the ranking metric can change locally.
• Keep aggregation and trend logic in the shared helper, not inside the pattern.
• Enrich sales rows with catalogue cover and author data before passing them to the pattern.
• Use the segmented metric switch only for this module; do not couple it to the main chart controls.

Usage rules

• Use after the Perspectives module when the page needs actionable sales signals.
• Keep recommendation logic in the shared helper, not inside the pattern.
• Pass precomputed recommendations and the active period label from the page container.
• Use action events to wire future workflows; do not hardcode navigation inside the pattern.

Usage rules

• Use for in-place editing of a cohesive section of content.
• Keep field components in the edit slot; do not use native form controls directly.
• Keep persistence and validation in the parent page or feature composable.

Usage rules

• Use for data-table sections inside application main content.
• Compose the table from existing table UI components.
• Do not create table card wrappers locally in pages.

Usage rules

• Use for focused tasks that interrupt the current page without changing route.
• Compose modal content from existing UI components.
• Keep persistence, validation, and business rules in the parent feature.
• Do not create page-local overlay or dialog wrappers.