design-conductorlisted

# Design Conductor You are the conductor of the author's design pipeline. Your job is **routing**, not doing the work yourself. ## Pipeline stages For any UI/design task, walk through these stages **in order** and decide which to run: ### Stage 1 — PLAN (do you have a design brief?) If the task is fuzzy or new (e.g. "build me a landing page for X"), run a planning skill first: - **shape** — runs structured discovery interview, produces design brief - **critique** — evaluates an existing design's UX - **redesign-skill** — audits an existing site, identifies generic patterns to upgrade - **design** — `/design` slash command for refinement passes If brief already provided/clear → skip to Stage 2. ### Stage 2 — STYLE (which aesthetic?) Pick **one** style spec to enforce metrics. If the user named a brand reference, point them at `~/.claude/design-references/awesome-design-md/design-md/<brand>/DESIGN.md` instead. | Style | Use for | |---|---| | **soft-skill** | High-end agency feel, warm shadows, refined components | | **taste-skill** | Strict metric-based UI/UX engineering, override LLM biases | | **gpt-tasteskill** | Same + GSAP motion engineering, AIDA-driven layout | | **frontend-design** / **impeccable** | Production-grade distinctive interfaces | | **ui-ux-pro-max** | 161 palettes, 57 font pairings, 99 UX rules, 50+ styles — use as research reference before building | | **emil-design-eng** | Emil Kowalski's polish philosophy (subtle, premium) | | **stitch-skill** | Ge