Taste Skill: the free skill that teaches Claude Code, Codex and Cursor to stop building identical landing pages

If the pages you build with Claude Code, Codex or Cursor all look the same, Taste Skill is the fastest fix I know. It is a free, open source skill that gives the agent precise design rules against AI slop. You can use it even if you are not a developer: you keep describing the page you want, and the agent follows a design manual.

What is AI slop in landing pages?

AI slop in landing pages is the set of design choices that make an AI-generated page recognizable at first glance. The signs are always the same:

• purple gradients;
• heroes that are always centered;
• three identical cards side by side;
• fonts and layouts that always look alike.

AI agents naturally fall back on these patterns. Without guidance, they pick the most common solution. And the most common solution is the one they have already seen a thousand times.

It is the same problem I wrote about for recognizable AI content on LinkedIn: when an output looks generated, people notice right away.

What does Taste Skill actually do?

Taste Skill is a SKILL.md file of more than a thousand lines (1,206 in the version I show in the video), full of rules the agent must follow while building the page. The project is by developer Leonxlnx, it is MIT licensed and, as of October 2026, it has nearly 98,000 GitHub stars.

The version I show in the video works in three steps:

1. It reads the brief. Before generating anything, the agent works out what kind of page you are building, for which audience and in which style.
2. It sets three parameters. It decides how experimental the layout should be, how much animation to use and how visually dense the page should be. In the file these are three dials from 1 to 10: DESIGN_VARIANCE, MOTION_INTENSITY and VISUAL_DENSITY.
3. It applies the anti-slop rules. It discourages purple gradients, bans the row of three identical cards, avoids the centered hero when the layout should be more experimental, and forces the agent to check the result before calling the work done.

The point is simple: you do not need to know the rules of design. The skill knows them, and the agent applies them for you.

Which agents does it work with?

Taste Skill works with Claude Code, Codex, Cursor and the other agents that support the Agent Skills standard. The rules are about design, not about a framework: the repository lists React, Vue, Svelte and plain HTML.

How do you install Taste Skill?

The fastest way is one terminal command:

npx skills add Leonxlnx/taste-skill

In Claude Code you can also install it as a plugin:

/plugin marketplace add Leonxlnx/taste-skill
/plugin install taste-skill@taste-skill

The simplest alternative: add the SKILL.md file to your project and ask your agent to follow it.

What has changed since September?

Since I recorded the video in September 2026, the repository has changed its default skill. The version with the three dials is now called taste-skill-v2-experimental and is still available in the skills folder.

The new default Taste Skill works differently:

• it picks one of 20 design directions;
• it builds with real images from open collections, with credits;
• it checks the page in a real browser at three widths and fails it if it finds slop;
• it reviews its own screenshots and fixes the top three problems, for up to three rounds.

The repository estimates 30-45 minutes and a few hundred thousand tokens per page, and it requires Node 22 and Chrome, Edge or Chromium.

Which projects is it best for?

Taste Skill is designed mainly for three cases:

• landing pages and marketing sites;
• portfolio sites;
• redesigns of existing sites, with the redesign-skill variant that audits the interface first and then fixes layout, spacing, hierarchy and styling.

For dashboards and app screens the repository recommends other variants, such as minimalist-skill or soft-skill.

If you do vibe coding and want to stop getting the usual interface that obviously looks AI-generated, Taste Skill is the first skill to try. Install it on your next project and compare the page with the one you would have got without it.