---
name: fractal
description: "Select and apply Fractal design guidance when creating or editing product interfaces, reports, scientific visuals, presentations, or product showcase videos. Start here to load only the relevant domain and task references."
---

# Select the design domain

Read [core.md](core.md), then select the artifact being designed. Domain selection precedes individual skill selection. Do not retrieve across all domains or load a domain merely because its subject appears in copy.

| Artifact or work | Domain | Task bundles |
| --- | --- | --- |
| Mirror product interface, component, theme, typography, responsive layout, motion, or icon | `product-ui` | `product-ui`, `component-use`, `component-create`, `color-system`, `typography`, `layout`, `motion`, `icon-use`, `icon-create` |
| Axon HTML summary, scientific report, evidence brief | `reports` | `summary-report` |
| Chart, plot, quantitative encoding, scientific figure, or explanatory diagram | `data-visualization` | `product-visualization` for non-scientific product metrics; `scientific-visualization` for scientific data; both include fundamentals |
| New or existing presentation | `presentations` | Select format below; add brand profile only when requested |
| Product showcase or launch video of the real interface, scene by scene | `showcase-video` | `showcase-video`; the director owns story, beats, and timing |

For mixed artifacts, activate each actual domain. A report with a chart needs reports plus scientific visuals. A product page containing a chart needs product UI plus scientific visuals. Their rules apply to their respective parts; UI border rules do not set data-line widths, and a chart does not impose its palette on surrounding UI.

For a kind of artifact not covered here, ask for missing design direction. Do not force a new domain into the closest familiar template.

## Confirm the surface when boundaries are unclear

Follow the shared [button variants](shared/primary-actions.md). Their visual meanings are fixed across domains; a public-website main CTA can use Secondary.

At repository setup or when changes cross a surface boundary, use established project context or ask whether this is product UI or another domain. One repository may contain both. Do not infer a product domain merely from shared components or a button’s action verb. A full public-website design domain has not yet been authored and should not silently inherit the complete product-UI profile.

## Presentations: format, palette, and brand

- A new deck with no requested format defaults to PPTX: `presentation-create`.
- Reading or changing an existing PPTX uses `presentation-edit`.
- Explicit Figma Slides or an existing Figma Slides target uses `presentation-figma`.
- Explicit internal Mirror Physics use or an explicit Blueprint style request additionally uses `presentation-mirror-physics`.
- Other native formats need appropriate tools; never rename a PPTX or silently switch format.

New presentations use the shared Fractal palette unless the user supplies another brand/style. That palette default does not activate Blueprint geometry, select Figma, or impose product-UI typography. Existing decks retain their design unless restyling is requested.

## Shared foundations

`shared/` contains reusable foundations and assets, not another domain. Domains explicitly import the files they need through `manifest.json`. Shared palette values are the default color source; semantic application belongs to the active domain. Chart data marks use the selected product or scientific profile; 2D chemical colors preserve atomic identity.

Fonts and glyph coverage are shared resources. Product type tiers apply only where imported. Generic PPTX typography and Blueprint typography follow their own profiles. An explicit user brand/style overrides the default palette without waiving readability or scientific fidelity.

## Open only the selected domain skills

When the host has not already supplied a resolved bundle, open the relevant entry below and follow its required and conditional references. Do not open every entry.

- Product UI: [interface composition](domains/product-ui/skills/fractal-product-ui/SKILL.md), [components](domains/product-ui/skills/fractal-components/SKILL.md), [color/type/layout foundations](domains/product-ui/skills/fractal-foundations/SKILL.md), [motion](domains/product-ui/skills/fractal-motion/SKILL.md), or [icons](domains/product-ui/skills/fractal-icons/SKILL.md), according to the task.
- Reports: [report skill](domains/reports/skills/fractal-reports/SKILL.md).
- Scientific visuals: [visualization skill](domains/data-visualization/skills/fractal-data-visualization/SKILL.md).
- Presentations: [presentation skill](domains/presentations/skills/fractal-presentations/SKILL.md), then the selected format and optional brand profile.
- Showcase videos: [showcase video skill](domains/showcase-video/skills/fractal-showcase-video/SKILL.md).

## Loading contract

The manifest is the machine-readable source for bundle dependencies and situational references. Resolve it with `scripts/context.py`, or implement its contract in the host. Read the corresponding skill and required references before implementation. Re-evaluate needs when scope changes. Dependencies load once, and unknown selections fail visibly.

See `integration/pi.md` for host context delivery and model-switch/compaction behavior. Standard Pi skill discovery remains an optional consumption path, not a guarantee that required context was delivered.

## Charts inside products

For operational dashboards load product UI plus `product-visualization` (or signal `product-charts`). For scientific measurements inside an app load product UI plus `scientific-visualization` (or `scientific-charts`). Add chart-type signals such as `chart-line` or `chart-bar`. The generic `charts` signal loads only shared fundamentals; select the profile before choosing data colors. A mixed dashboard can use both profiles, scoped per plot. Do not infer scientific data from the mere presence of numbers.
