Neumorphism

# Implement Neumorphism in your agent

## Objective
Create a neumorphic surface limited to a few secondary controls. Use one shared matte color, a coherent opposing shadow pair, and inset states. Always add contrast and focus independent from shadows.

## 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
- One continuous surface — The background and controls share exactly the same matte color.
- Dual soft shadows — One light and one dark shadow describe a consistent diagonal light.
- Pressed inset state — Active states invert the shadows into the surface.
- Low-contrast edges — The shape appears through shadow transitions without a clear outline.

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

## Accessibility
- Add boundaries and states that remain perceptible without low-contrast shadows.
- Keep a high-contrast focus outline around every control.
- Avoid this treatment for critical forms and long action lists.

## When not to use
- Making every control nearly invisible to preserve a uniform surface.
- Changing the light direction between components.

## Acceptance criteria
- A few decorative controls in a simple interface with a constant background.
- A specimen or visual identity where softness matters more than density.

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

## Objective
Check that Neumorphism 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:ccc965b9dd05b7d59290fe149a758b671e811a65d11128af0f7e1523ba2f2f2a

# Debug Neumorphism 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 neumorphism by increasing label contrast and adding a border or color change to states. Keep shadows as visual depth, never the only way to understand an action.

## Final verification
- Add boundaries and states that remain perceptible without low-contrast shadows.
- Keep a high-contrast focus outline around every control.
- Avoid this treatment for critical forms and long action lists.

## 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 Neumorphism 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:2a67a24ff3865544fc194c88d028945bfcbc9453d9adf7d15b9dbe496d90267b