---
name: fractal-product-ui
description: "Compose or revise Mirror product pages and application views using Fractal UI. Use for product interface work, not generic presentations or decorative artwork."
---

# Compose a product interface

## Load

Read [core](../../../../core.md), [interface direction](../../references/interface.md), [color](../../references/color.md), [typography](../../references/typography.md), [layout](../../references/layout.md), and [component selection](../../references/components/selection.md). The integrated host supplies these through `product-ui`; do not reread unchanged documents already present.

## Confirm the product surface

Apply the shared [button variants](../../../../shared/primary-actions.md) consistently. When setting up a repository or changing a mixed/unclear surface, establish the domain before applying broader product guidance. Retain established scope instead of asking on every edit.

## Decide and build

1. Inspect the target view, source content, installed `@mirror-physics/fractal-ui` / `@mirror-physics/fractal-icons` versions, and existing theme. Determine what the user must understand or do first.
2. Choose reading order, comparison structure, grouping, and density from that task. Give true peers equal treatment. A table, conversation, and editor need different compositions even though their components share a visual system.
3. Select existing components by purpose. Inspect actual exports and props before using them. Compose screen-specific behavior locally; move recurring new behavior into `fractal-ui` only when justified.
4. Establish shared content insets and peer padding. Keep adjoining navigation header dividers aligned. Put padding inside moving content so scrolling clips at visible boundaries. Use structural dividers only where real regions meet.
5. Use semantic tokens, the approved type tiers, and surface-aware boundaries. Keep resting surfaces flat; reserve shadows for floating layers. Color needs a real status, hierarchy, interaction, or brand meaning.
6. Implement complete relevant states: keyboard focus, hover/press, selection, disabled, pending, empty, and error. Preserve accessible names and the package's behavior.

## Load additional guidance when needed

- Motion, expansion, dismissal, or transitions: [motion skill](../fractal-motion/SKILL.md).
- Icons: [icon skill](../fractal-icons/SKILL.md); inspect the package instead of inventing a glyph/export.
- Non-scientific usage/operational charts: [product visualization skill](../fractal-product-visualization/SKILL.md). Scientific plots inside a product: [visualization skill](../../../data-visualization/skills/fractal-data-visualization/SKILL.md) plus its scientific profile.
- A scientific summary/report page: [report skill](../../../reports/skills/fractal-reports/SKILL.md).
- `SidePanel` or `Textarea`: their [panel](../../references/components/side-panel.md) or [textarea](../../references/components/textarea.md) reference.

## Verify

Inspect representative rendered states and narrow/enlarged-text layouts. Check shared edges, control alignment, meaningful hierarchy, scrolling boundaries, readable labels, contrast, keyboard operation, and reduced motion where applicable. Table cells default to one concise line and one hierarchy level; supporting detail belongs in an appropriate column or inspector. Do not claim rendering checks that were not performed.
