Agent skill · Frontend

design-taste-frontend-v1

The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.

Leonxlnxgithub.com/LeonxlnxGitHub ↗
claude-codecodexMIT
Install
npx skills add Leonxlnx/taste-skill --skill taste-skill-v1 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 21 KB
Bundled scripts: none
Path: skills/taste-skill-v1/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 71,680
Language: JavaScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# High-Agency Frontend Skill ## 1. ACTIVE BASELINE CONFIGURATION * DESIGN_VARIANCE: 8 (1=Perfect Symmetry, 10=Artsy Chaos) * MOTION_INTENSITY: 6 (1=Static/No movement, 10=Cinematic/Magic Physics) * VISUAL_DENSITY: 4 (1=Art Gallery/Airy, 10=Pilot Cockpit/Packed Data) **AI Instruction:** The standard baseline for all generations is strictly set to these values (8, 6, 4). Do not ask the user to edit this file. Otherwise, ALWAYS listen to the user: adapt these values dynamically based on what they explicitly request in their chat prompts. Use these baseline (or user-overridden) values as your global variables to drive the specific logic in Sections 3 through 7. ## 2. DEFAULT ARCHITECTURE & CONVENTIONS Unless the user explicitly specifies a different stack, adhere to these structural constraints to maintain consistency: * **DEPENDENCY VERIFICATION [MANDATORY]:** Before importing ANY 3rd party library (e.g. `framer-motion`, `lucide-react`, `zustand`), you MUST check `package.json`. If the package is missing, you MUST output the installation command (e.g. `npm install package-name`) before providing the code. **Never** assume a library exists. * **Framework & Interactivity:** React or Nex

What's inside
Steps it walks through
  1. 1. ACTIVE BASELINE CONFIGURATION
  2. 2. DEFAULT ARCHITECTURE & CONVENTIONS
  3. 3. DESIGN ENGINEERING DIRECTIVES (Bias Correction)
  4. 4. CREATIVE PROACTIVITY (Anti-Slop Implementation)
  5. 5. PERFORMANCE GUARDRAILS
  6. 6. TECHNICAL REFERENCE (Dial Definitions)
  7. DESIGNVARIANCE (Level 1-10)
  8. MOTIONINTENSITY (Level 1-10)
  9. VISUALDENSITY (Level 1-10)
  10. 7. AI TELLS (Forbidden Patterns)
  11. Visual & CSS
  12. Typography
  13. Layout & Spacing
  14. Content & Data (The "Jane Doe" Effect)
More from taste-skill
All skills →
About this skill
What does the design-taste-frontend-v1 skill do?

The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.

How do I install it?

Run `npx skills add Leonxlnx/taste-skill --skill taste-skill-v1 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Leonxlnx/taste-skill, a repository with 71,680 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going