# Fractal

Fractal supplies design direction for an agent working across product interfaces, reports, scientific visuals, presentations, and product showcase videos. Load this contract automatically; load task guidance only for work the agent is actually performing. Mentioning a chart in prose does not mean creating a chart.

## Interpret the guidance

- Preserve the user's requested artifact, audience, format, and scope. Fractal does not automatically brand every output as Mirror Physics.
- Distinguish requirements, defaults, allowed choices, and examples. Examples are not source facts or mandatory templates.
- Explicit task requirements take precedence over design defaults. Preserve accessibility, factual accuracy, and scientific meaning. Surface unresolved conflicts instead of silently choosing.
- Within the same authority, the more specific rule governs only its stated scope. Product UI, scientific marks, and slide artwork have different geometry and styling rules.
- Never invent data, sources, transformations, assets, package exports, props, or available tools. Inspect the target environment and installed package for exact implementation facts.

## Load by task

Read `SKILL.md` to select the design domain first, then use `manifest.json` to select that domain’s task bundles. Shared files apply only when the domain explicitly imports them. The harness resolves each bundle's required files and dependencies; the model identifies additional needs as the work develops. Load matching situational references before making the decision they govern. Required context must not depend on similarity search.

Skills are task entry points, not commands the user must know. When using ordinary Pi skill discovery without the bundle resolver, read the skill's required references yourself. Relative links resolve from the document containing them, not from the target application's working directory.

## Apply design direction

Read [button variants](shared/primary-actions.md): Primary is blue, Secondary is neutral filled, Tertiary is outlined, and Ghost has no resting fill or border. These meanings are shared across domains. A main action may use Secondary; no Primary button is required.

For Mirror product UI, use `@mirror-physics/fractal-ui` and `@mirror-physics/fractal-icons`. Choose an existing component, compose existing components, or make a product-local composition before proposing a new reusable component. Inspect installed exports and supported styling APIs. Fractal owns design intent; the packages own their exact APIs and runtime behavior.

Choose hierarchy and composition from the task, content, reading order, comparison needs, and available room. Preserve equal treatment for true peers. Do not invent a winner or add decoration to manufacture variety. Consistent components do not require identical page layouts.

Read [shared color defaults](shared/colors/palette.md) and resolve exact values from [the primitive palette](shared/colors/primitives.json) when applying color. Use semantic tokens in generated UI. Primitive values belong in definitions and explicitly scoped scientific or artwork references. Check accessibility and final rendered contrast, not just token names. Keep keyboard access and non-color cues; preserve reduced-motion alternatives.

Before delivery, verify the active task's requirements against the result. Report what was checked and any material unverified output. A loaded document is not proof of compliance.
