Taste Skill
Anti-slop SKILL.md for the front-end. Instead of letting the agent ship yet another generic landing page, Taste Skill reads the brief, infers the design language and tunes three dials (variance, motion, density), with a hard em-dash ban and canonical GSAP skeletons. **It is no longer a file, it is a family spread over three repositories.** The `taste-skill` repository now holds a single skill, `design-taste-frontend`, which absorbed the redesign pass for existing projects. The others kept their install names but live elsewhere: the three committed styles (minimalist, brutalist, high-end visual) and their variants in `taste-skill-classics`, the image branch in `imagegen-skills`, including **brandkit**, which builds a full identity board (logo directions, palette, type pairing, applications) out of an idea that is still vague. The repository also announces TasteCode, Taste Skill as a desktop app with a built-in design agent, free and open source according to its README ([Instagram reel Devt4KiJUNC](https://www.instagram.com/reel/Devt4KiJUNC/)). **The image branch is worth pulling apart.** In `imagegen-skills`, `image-to-code` follows a fixed order: it generates site references, analyses them, then writes the front-end to match. `imagegen-frontend-web` and `imagegen-frontend-mobile` stop before code: they only produce design images, to run through a generator such as ChatGPT Images, which helps when you want to settle a direction before paying for a single line of code.
Strengths
- Infers the design language from the brief instead of applying a default theme
- Three explicit dials (variance, motion, density) to frame the output
- Canonical GSAP skeletons provided, motion does not scatter in every direction
Limitations
- Overlaps Impeccable and SkillUI, you pick one taste reference rather than stacking them
- Pairing with GPT Image 2 adds a dependency and a cost for visual references
Best for
- Agents that ship generic front-ends despite a precise brief
- Landing pages and showcase sites where visual taste makes the difference
- Workflows that start from generated visual references before coding the front-end
- A product with no settled visual identity, where brandkit produces the first board before anything gets coded