taste-test

Elicit visual direction by rendering divergent design variants and reading user reactions.

4|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/laicluse/agent-fieldkit --skill taste-test-laicluse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: taste-test
Source: https://github.com/laicluse/agent-fieldkit/tree/main/.agents/plugins/generated/eye-of-the-beholder/skills/taste-test
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill taste-test-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users often know a design looks wrong but cannot articulate why, responding with gut-words like "too busy" or "feels cheap" instead of specifications. Asking them to describe a direction pushes the burden onto the exact skill they lack, and building from vague words produces generic output they will reject. ## Core Features & Use Cases - Variant Fan: Renders 3 to 5 genuinely divergent design directions of the same screen side by side, each committed to a distinct stance, so the user's pick becomes the specification. - Reaction-Card Axes: Offers word-axes (calm/energetic, warm/clinical, dense/airy) so users point at positions instead of producing design vocabulary. - Contemporary Harvest: Researches how credible current products solve the same problem and extracts transferable moves rather than copying pixels. - Decision Recording: Appends each decision, with the user's verbatim reaction, to a growing visual-language.md so the direction persists across sessions. - Use Case: A user says a new dashboard "feels cheap" but cannot say more. Render three divergent dashboard directions, let them point at one, and record the chosen direction in visual-language.md for future sessions. ## Quick Start Ask the agent to show you three divergent visual directions for the screen you are unhappy with so you can react to them instead of describing what you want.

Frequently Asked Questions about taste-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a design direction from a client who cannot describe what they want?▼

Show divergent rendered options instead of asking for a description. Present 3 to 5 variants that each commit to a different stance, let the person point at one, and treat their reaction as the specification rather than asking them to compose design vocabulary.

What is a variant fan in UI design exploration?▼

A variant fan is a set of 3 to 5 genuinely divergent renderings of the same screen, each taking a distinct position on type, density, and color. Variants must differ enough that a stranger could describe each in a sentence; tints of one layout do not count.

When should I not use a variant fan for design feedback?▼

Skip the fan when the user names a concrete axis to match a reference, when the change is a single measurable tweak on an agreed direction, or when the direction is only slightly uncertain. A full fan is the expensive move; use one best-guess render for small uncertainties.

How do I make a UI look modern without it looking generic?▼

Research how credible current products in the same category solve the problem and extract transferable moves, not exact colors or layouts. Avoid generated-interface tells like gradients, bordered-card grids, and decorative status dots, and pick typography as a deliberate stance.

Where are taste-test design decisions stored?▼

Decisions are appended to a visual-language.md file at the project root, one entry per decision. Each entry records the user's verbatim reaction, the move chosen, and the slop tell avoided, so the direction persists across sessions and is not re-litigated.