# Component Tone

## General Tone

Components should feel precise, calm, and operational.

Avoid playful visual noise unless explicitly requested.

## Controls

- Buttons: clear priority tiers (`primary`, `secondary`, `ghost`), with firm focus rings.
- Inputs: soft-filled surfaces in default state.
- Inputs: no visible border in default state.
- Inputs: show focus ring only in active/focus state.
- Selectors and toggles: obvious active/inactive contrast without neon accents.
- Segmented choices should feel compact and utility-first, not pill-heavy marketing tabs.
- Toggles should carry a clear on/off silhouette with one restrained accent color.

## Containers

- Panels/cards: subtle elevation and radius consistency.
- Sidebars/rails: muted but legible; active item state should be unmistakable.
- Group containers for settings rows should prioritize divider rhythm over shadow depth.
- Active navigation rows should use a soft fill and shape cue instead of high-saturation highlights.

## Feedback States

- Loading: restrained, readable, non-distracting.
- Empty: informative and calm, not decorative.
- Error: strong legibility and actionable recovery tone.
- Success: present but not celebratory.
- Disabled states should be clearly subdued while preserving label readability.

## Text Tone

- Use concise, neutral, professional wording.
- Keep labels short and scannable.
- Use strong emphasis only for actionable or risky elements.

## Interaction Emphasis

- Emphasize intent over ornament.
- Focus/hover/active states must be visibly distinct and systematic.
- Keep hover deltas subtle; reserve stronger contrast for selected/focused/critical states.
- Primary form actions should live in a distinct bottom-right action zone when screen structure allows.
