# visual-design-taste

> Choose and apply high-quality frontend visual direction for websites, apps, dashboards, redesigns, landing pages, portfolios, and UI polish. Use when prompts mention design taste, anti-slop UI, redesign, premium visual design, minimalist, brutalist, legacy style inheritance, design direction, or the old taste-skill/gpt-tasteskill/soft-skill/brutalist-skill/minimalist-skill/redesign-skill skills.

- Skill: `rajanthar/visual-design-taste` (Agent Skill, multi-file: 9 files)
- Install (CLI): `npx skillmds add rajanthar/visual-design-taste`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rajanthar/visual-design-taste/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: RajanthaR (https://skillmd.com/u/rajanthar)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/rajanthar/visual-design-taste

---


# Visual Design Taste

Use this skill to avoid generic AI-looking interfaces and pick a deliberate visual direction.

## Routing

- Read `references/design-taste-frontend.md` for the current broad anti-slop frontend design workflow.
- Read `references/design-taste-frontend-v1.md` only when a project depends on the original v1 behavior.
- Read `references/redesign-existing-projects.md` for redesigns of existing projects.
- Read `references/high-end-visual-design.md` for premium agency-style polish.
- Read `references/gpt-taste.md` for strict advanced layout and motion taste rules.
- Read `references/industrial-brutalist-ui.md` for brutalist/mechanical UI direction.
- Read `references/minimalist-ui.md` for clean editorial minimalist UI direction.

## Workflow

1. Infer the product category, audience, and task surface.
2. Choose one coherent design direction; avoid stacking unrelated aesthetics.
3. Preserve owner-provided copy, data contracts, and existing design systems unless asked to change them.
4. Make concrete choices for spacing, typography, color, density, imagery, states, and responsive behavior.
5. Verify visually with screenshots where possible.

## Output

Describe the chosen direction, key UI changes, and verification performed.