HarshithNayakaL

UI UX Taste Skill — Design skill for Claude Code

Design community

How to install UI UX Taste Skill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open HarshithNayakaL/ui-ux-taste-skill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What UI UX Taste Skill does

Agent skill that discovers a user's UI taste through real reference moodboards instead of vague adjectives like "modern" or "clean," then turns their reaction into one opinionated frontend stack pick and an ASCII wireframe. Taste-discovery front end — hands off to a full-build skill once direction and stack are locked.

Alternatives in Design

Pair — Fuse two extracted designs into a single hybrid identity 3.6k ★
Part 3 — Technical Design Document Generator — I'll help you create a Technical Design Document for your MVP 2.1k ★
Hue — open-source skill that learns any brand and turns it into a complete design system 806 ★

README

ui-ux-taste

**A skill that figures out what your app should look like — by showing you, not asking you.**

Most people can't describe the UI they want. Ask someone "what style are you going for?" and you'll get *modern*, *clean*, *minimal but not boring* — adjectives that mean nothing and lead to a generic build. But show them six real interfaces and they'll point at one in two seconds.

`ui-ux-taste` exploits that gap. It shows you real shipped design work across distinct directions, reads your reaction, and turns it into two concrete deliverables: **one opinionated frontend stack** and an **ASCII wireframe** of your key screen.

It doesn't build the thing. It decides what the thing should be.

The flow

1. SCOPE      → what's the app, who's it for, web or mobile
2. MOODBOARDS → 4–6 real reference directions, you react
3. STACK      → one opinionated frontend stack, derived from what you picked
4. WIREFRAME  → ASCII wireframe of the key screen, in that direction's spirit

Stage 2 is the whole point and never gets skipped. Recommending a stack from a text description is exactly the failure mode this skill exists to prevent.

What you get

**A stack, not a menu.** Five parts, all covered: framework, styling approach, component baseline, motion, and icons/type. A menu of five viable frameworks makes you do the work the skill was supposed to save you.

**A stack that matches the look.** A brutalist direction gets unstyled Radix primitives to skin from scratch and CSS Modules over Tailwind — because Tailwind's defaults fight deliberate rawness. A clean SaaS direction gets shadcn/ui and Framer Motion for state transitions only. The visual direction drives the technical choice, not the other way around.

**Portfolio-aware picks.** If you're building to show employers, the skill checks the stack against what's already in your portfolio. Next.js across four projects reads as a coherent engineer with a real stack; a different framework in every pro