# Taste Layer

Use this reference when a surface is technically correct but visually generic,
unmemorable, or mismatched to the product's intent.

## Stance

Taste is a judgment layer above the design system. Tokens make choices
consistent; taste decides which choices are worth making.

Before changing pixels, name:

- audience and job;
- desired feel;
- product category;
- one or two visual references;
- one thing the surface must not become.

## Anti-Generic Checks

Watch for common agent defaults:

- card grids where a table, timeline, canvas, or inspector would be clearer;
- centered hero sections on tools that should start with the work surface;
- decorative gradients, blobs, and bokeh used as a substitute for hierarchy;
- one-note palettes dominated by a single hue family;
- generic Inter-plus-rounded-card SaaS styling;
- motion applied uniformly instead of tied to interaction meaning;
- icons, charts, or screenshots that do not show the actual product state;
- over-large headings inside dense dashboards or operational panels;
- visual polish that hides weak claims or unclear product logic.

## Direction Menu

Directions must differ structurally, not only by palette:

- **Operational/workbench:** dense, scannable, efficient repeated use.
- **Editorial/narrative:** guide attention through explanation or evidence.
- **Brand-forward:** make product, object, or client unmistakable.
- **Reference/catalog:** reliable information architecture and filtering.
- **Minimal polish:** preserve shape, improve hierarchy, rhythm, and states.

Name the sacrifice for each direction. A workbench sacrifices drama for speed;
an editorial page sacrifices density for comprehension.

## References And Mood Boards

Good visual references are specific:

- "GOV.UK component pages for trust and clarity"
- "Carbon component docs for anatomy and usage tables"
- "Linear settings screens for dense operational restraint"
- "Stripe docs for typography and code/content rhythm"

Bad references are vague:

- "modern"
- "premium"
- "beautiful"
- "like Apple"

Use references as lenses. Do not copy their brand, component library, or visual
language wholesale.
