design-taste-frontendlisted

<!-- Vendored from https://github.com/Leonxlnx/taste-skill (MIT, © 2026 Leonxlnx), the skills/taste-skill/ variant. Copied rather than installed via `npx skills add` so it travels with the repository into cloud / autopilot sessions — same reasoning as skills/ponytail and skills/frontend-design. Body below is upstream verbatim; the only change is this note. The repo folder is `taste-skill`, so Claude Code registers it as `taste-skill` even though the frontmatter name is `design-taste-frontend` — wire it into agents as `taste-skill`. Scope (per §13): landing pages, portfolios, redesigns — NOT dashboards, data tables, or multi-step product UI. Upstream changes are not pulled automatically. Re-vendor to update. --> # tasteskill: Anti-Slop Frontend Skill > Landing pages, portfolios, and redesigns. Not dashboards, not data tables, not multi-step product UI. > Every rule below is **contextual**. None of it fires automatically. First read the brief, then pull only what fits. --- ## 0. BRIEF INFERENCE (Read the Room Before Anything Else) Before touching code or tweaking dials, **infer what the user actually wants**. Most LLM design output is bad because the model jumps to a default aesthetic instead of reading the room. ### 0.A Read these signals first 1. **Page kind** - landing (SaaS / consumer / agency / event), portfolio (dev / designer / creative studio), redesign (preserve vs overhaul), editorial / blog. 2. **Vibe words** the user used - "minimalist",