Design Taste

Design taste

Lane adapter of taste-skill. It reviews landing pages, portfolios, and redesigns, and guides isolated branded mockups. It does not write product UI, and it does not turn cabinets, admin screens, or data tables into landing pages.

Info (print and stop)

If $ARGUMENTS is info / справка, print this block verbatim, then stop:

design-taste — визуальный аудит и направление для изолированного макета.

1) Design read: kind / audience / job / vibe / evidence from the brief, screen and DESIGN.md.
2) Three dials: DESIGN_VARIANCE / MOTION_INTENSITY / VISUAL_DENSITY. Existing tokens win.
3) Evidence audit: type, color, layout/rhythm, assets, states, motion, a11y.
4) Preflight: every finding has evidence, impact and an owner.

Агент: design-lead MODE=audit или MODE=mockup
Чинить: UI-ран после «делай»
Роутер: /lane-stack:web-design info

Design read (before the checklist)

Read the brief, requested route or screenshot, relevant DESIGN.md, current components, and the project's stack before judging taste. Identify:

• page kind and user job (landing, portfolio, editorial, redesign, cabinet);
• audience, references, vibe, brand assets, tokens, and existing component language;
• accessibility, responsive, performance, and product constraints.

Write one line: Reading this as: <kind> for <audience>, serving <job>, with a <vibe> language, using evidence from <paths/screenshots>.

For an existing UI, describe what is already true before proposing change. Preserve information architecture, working accessibility patterns, and the project's brand unless the brief asks for a change. If evidence is missing, write DEGRADED: <missing evidence> and make the smallest safe recommendation. Ask one question only when two plausible design reads would lead to different work.

Three dials

Use the existing DESIGN.md reading when it exists. Otherwise choose a starting range from the brief; these are review dials, not quotas:

Low variance favors a stable grid; high variance can justify asymmetry only when it helps the page job. Motion and density must follow the same reading.

Evidence audit

Report findings as finding → evidence (path, line, screenshot, or observed state) → impact → recommendation → owner. Classify by consequence: blocker (primary task cannot be completed), major (material usability/accessibility barrier), or minor (polish). Do not call a pattern slop merely because it is common; explain why it fails this page's job.

Review these headings:

• Type: role hierarchy, readable measure, line-height, weight contrast, tracking, number alignment, wrapping, and whether the existing typeface fits the brand.
• Color and surfaces: one coherent palette, contrast, surface hierarchy, border/shadow logic, and consistent lighting. Inter is valid when the brand or product already uses it; do not swap fonts for novelty.
• Layout and rhythm: container, alignment, grid, responsive changes, section pacing, baseline alignment, and a spacing scale that comes from the project tokens. Use cards only when elevation communicates hierarchy.
• Assets and content: real project assets first, correct aspect ratios and crops, meaningful alt text, and no fake screenshots or decorative assets that compete with the job. Record an asset gap instead of inventing a replacement.
• States: hover, focus-visible, active, disabled, loading, empty, error, and current navigation state where the surface needs them. Check keyboard behavior.
• Motion: every animation must communicate hierarchy, storytelling, feedback, or a state change. Match the motion dial, use the project's existing tools, and provide a prefers-reduced-motion path. If the reason cannot be stated in one sentence, remove the animation.