Taste Skill
Tune visual variance, motion, and density so agent-generated UIs feel intentional instead of generic template slop.
Overview
taste-skill is an agent skill for the Build phase that gives frontend-generation agents tunable design taste—variance, motion, and density—to reduce generic UI slop.
Install
npx skills add https://github.com/nexu-io/open-design --skill taste-skillWhat is this skill?
- Tunable design variance, motion intensity, and visual density knobs for agent UI work
- Anti-slop framing focused on editorial taste rather than default component soup
- Open Design catalogue entry with upstream bundle at Leonxlnx/taste-skill for full assets
- Trigger phrases: design taste, visual taste, good taste, anti slop, visual density
- Advertises design-system mode for discovery during agent planning
Adoption & trust: 810 installs on skills.sh; 61.4k GitHub stars; 1/2 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent keeps shipping visually interchangeable layouts that look like default SaaS templates with no deliberate motion or density choices.
Who is it for?
Solo builders iterating on web or app UI with Claude Code, Cursor, or Codex who want taste guardrails before committing to a visual direction.
Skip if: Teams that already have a locked design system and only need token-compliant codegen with no aesthetic exploration.
When should I use this skill?
User or plan mentions design taste, visual taste, good taste, anti slop, or visual density during frontend or design-system work.
What do I get? / Deliverables
You get explicit taste parameters the agent can follow while building UI, with a clear path to install the upstream Leonxlnx bundle for the complete design-system workflow.
- Taste-tuned UI direction aligned to variance, motion, and density settings
- Pointer to upstream taste-skill bundle for full assets
Recommended Skills
Journey fit
Canonical shelf is Build because the skill targets high-agency frontend output and design-system taste during implementation. Frontend is where layout, motion, and visual density decisions land in shipped UI.
How it compares
A design-taste skill package for agent UI generation, not an MCP server or automated visual regression tester.
Common Questions / FAQ
Who is taste-skill for?
Indie and solo builders using AI coding agents on frontend work who want stronger visual judgment than default component layouts.
When should I use taste-skill?
During Build frontend passes when you are defining or refining UI, and when triggers like anti slop, visual density, or design taste match your task.
Is taste-skill safe to install?
Review the Security Audits panel on this Prism page and inspect the upstream GitHub bundle before copying scripts into your agent skills directory.
SKILL.md
READMESKILL.md - Taste Skill
# taste-skill > Curated from @Leonxlnx. ## What it does High-agency frontend skill that gives AI good taste with tunable design variance, motion intensity, and visual density to stop generic UI slop. ## Source - Upstream: https://github.com/Leonxlnx/taste-skill - Category: `design-systems` ## How to use This catalogue entry advertises the skill in Open Design so the agent discovers it during planning. To run the full upstream workflow with its original assets, scripts, and references, install the upstream bundle into your active agent's skills directory: ```bash # Inspect the upstream README for exact paths open https://github.com/Leonxlnx/taste-skill ``` Then ask the agent to invoke this skill by name (`taste-skill`) or with one of the trigger phrases listed in this skill's frontmatter.