Web Brutalism

# Implement Web Brutalism in your agent

## Objective
Create a strict Web Brutalist page with semantic HTML, system typography, underlined links, and visible document structure. Keep CSS minimal and remove shadows, gradients, decorative radii, and imitation materials.

## 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
- Browser materials — System fonts, clearly underlined links, and controls close to native rendering remain visible.
- Document structure — Headings, lists, tables, and separators directly carry the layout.
- No decorative rendering — No blurred shadow, decorative gradient, imitation material, or simulated volume.
- Useful density — Information stays compact and immediately navigable, without theatrical spacing.

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

## Accessibility
- Keep link underlines, visited states, and focus outlines.
- Maintain readable text and touch target sizes despite the density.
- Use real headings, lists, and table headers to match the visible structure.

## When not to use
- Intentionally breaking accessibility to make the page feel old.
- Adding loud colors, thick borders, and offset shadows, which shifts into Neobrutalism.

## Acceptance criteria
- A document, index, or archive where speed and density matter more than decoration.
- An identity that embraces native web materials and transparent structure.

## 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 Web Brutalism on the real surface

## Objective
Check that Web Brutalism 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:734a9be5e552c783186dc8911d9ebf299a1c6b3adb9a2ecbbfcb85cbbb51b753

# Debug Web Brutalism 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 page by restoring readability, target sizes, heading hierarchy, and table headers. Visual rawness does not justify broken structure or ambiguous controls.

## Final verification
- Keep link underlines, visited states, and focus outlines.
- Maintain readable text and touch target sizes despite the density.
- Use real headings, lists, and table headers to match the visible structure.

## 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 Web Brutalism 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:6e1e75e957154a7e65b722cc70bf82a53d13cacb7a38b7dad2014d2e29a05b0f