Minimalism

# Implement Minimalism in your agent

## Objective
Create a minimalist interface around one primary goal, one primary action, and only necessary content. Use negative space, a limited palette, and clear typographic hierarchy to guide attention.

## Prerequisites
- Inspect existing components, tokens, and brand constraints.
- Confirm that this style fits the surface and content.
- Preserve existing structure, semantics, and interactions.

## Behavior and surfaces
- Active negative space — Empty space surrounds important elements and directs attention instead of filling the page.
- Restricted element count — Every control, message, and decoration must justify its presence.
- Limited palette — A short neutral range and one accent are enough to organize the screen.
- Structural typography — Strong typographic hierarchy replaces much of the ornament.

## States
- Cover existing default, hover, focus, active, disabled, loading, and error states.
- Provide a static state when reduced motion is requested.

## Accessibility
- Keep labels, help, errors, and confirmations even when they increase text quantity.
- Do not use spacing as the only signal for grouping or hierarchy.
- Maintain recovery paths and genuinely necessary secondary actions.

## When not to use
- Removing help and error information instead of removing redundancy.
- Spreading little content over a very large surface without hierarchy or intent.

## Acceptance criteria
- A page with one clear primary goal and few competing decisions.
- A product where content quality allows decoration and repeated explanations to be removed.

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

• Requires · Existing tokens, components, and brand constraints

# Audit Minimalism on the real surface

## Objective
Check that Minimalism remains consistent, accessible, and measured on the components that actually use it.

## Checks
- Compare interactive states and fallbacks.
- Check contrast, focus, and reduced motion.
- Report visual effects that weaken hierarchy or performance.

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

sha256:a8dd16d54e6188039d73a1edf1e820c6e17086ca500ea1c09b4c8f03cc660f8d

# Debug Minimalism in your agent

## Observed symptom
[DESCRIBE THE SYMPTOM HERE]

## Observable checks
- Compare the surface with the documented visual signals.
- Verify contrast, focus, reduced motion, and fallback behavior.
- Isolate the visual layer without changing functional structure.

## Possible causes
- The style hides hierarchy or reduces contrast.
- The effect is applied to too many surfaces or depends on an unavailable API.
- An interactive state is no longer perceivable.

## Bounded corrections
Repair this minimalism if useful information disappeared. Restore necessary labels, help, errors, and states, then simplify composition without sacrificing understanding or error recovery.

## Final verification
- Keep labels, help, errors, and confirmations even when they increase text quantity.
- Do not use spacing as the only signal for grouping or hierarchy.
- Maintain recovery paths and genuinely necessary secondary actions.

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

• Requires · Existing tokens, components, and brand constraints

# Prevent Minimalism drift

## Objective
Turn the visual fix into a reusable rule and focused check without freezing the whole interface.

## Checks
- Isolate the responsible tokens or variants.
- Add focused evidence for the affected states.
- Compare nearby styles before widening the rule.

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

sha256:f36785c4c66d8b94f6cd41862a3e6c06f04f26042caef66419432d45728efdfe