minimalist-ui bans gradients in section 2, then offers them in sections 6, 7 and 8

The minimalist-ui skill for Claude Code tells the agent "DO NOT use gradients" in its ban list, and its own description ends with "No gradients, no heavy shadows." Three later lines in the same file offer a radial-gradient, an optional drifting gradient blob and "ambient gradients" as ways to add depth. If you install it, decide which side wins before the agent decides for you.

We run Skillselion, an independent directory of agent skills, not affiliated with Anthropic, OpenAI, Cursor or the taste-skill author. For this post we read skills/minimalist-skill/SKILL.md at commit d237dd39 of leonxlnx/taste-skill (95,270 GitHub stars, MIT, per the GitHub API on Oct 13, 2026). The file is 86 lines and 1,127 words. We did not run it or measure its output.

What is the minimalist-ui skill?

minimalist-ui is one of 13 SKILL.md files in the taste-skill repo. The README describes it as "Editorial product UI (Notion/Linear vibes), restrained palette, crisp structure." It has 401,249 installs on skills.sh as of Oct 13, 2026. Our minimalist-ui skill guide covers what it is and when to pick it. This post is about one conflict inside the file.

Install it on its own. The README gives this form:

npx skills add https://github.com/Leonxlnx/taste-skill --skill "minimalist-ui"

Where does the file ban gradients?

Two places. The frontmatter description, which is the text an agent reads when it decides whether to load the skill, says:

"Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows."

Source: minimalist-skill/SKILL.md, frontmatter description

Section 2 is a list of nine "DO NOT" lines. The fifth one reads:

"DO NOT use gradients, neon colors, or 3D glassmorphism (beyond subtle navbar blurs)."

Source: minimalist-skill/SKILL.md, "2. Absolute Negative Constraints (Banned Elements)"

The only exception in that line is for navbar blurs. It names no exception for gradients.

Where does the same file offer gradients?

Three places, and each one is further down the file than the ban.

Section 6 does not want flat section backgrounds:

"Sections should not feel empty and flat. Use subtle full-width background imagery at very low opacity, soft radial light spots (radial-gradient with warm tones at opacity: 0.03), or minimal geometric line patterns to add depth without breaking the clean aesthetic."

Source: minimalist-skill/SKILL.md, "6. Iconography & Imagery Directives"

Section 7 lists an optional background effect, "A single, very slow-moving radial gradient blob", at an opacity of 0.02 to 0.04 on a fixed layer.

Section 8 is the execution checklist. Step 6 tells the agent to "Ensure sections have visual depth through imagery, ambient gradients, or subtle textures".

So the count is two bans and three lines that offer a gradient. None of the three requires one. Sections 6 and 8 list it next to imagery, line patterns or textures, and the section 7 blob is marked optional. A charitable reading is that section 2 means loud, saturated gradients and the later sections mean a warm tint you can barely see. The file never says that. An agent that takes "Absolute Negative Constraints" at its word can still follow all three lines, as long as it never picks the gradient option the file keeps offering.

What will Claude Code do with the conflict?

We do not know, and we will not guess a rate. We did not test it. What the text tells you is that both outputs are defensible: a page with a 3 percent radial tint behind the hero follows sections 6 to 8, and a page with no gradient at all follows section 2 and still meets sections 6 to 8 through imagery or textures. If you review generated UI against the skill, neither one is a bug you can point at.

That matters more if you load a second style skill. The same repo ships the design-taste-frontend skill (600,042 installs, skills.sh, Oct 13, 2026) and the industrial-brutalist-ui skill (375,272 installs, same source and date). We did not read those two files for this post. Two style skills loaded together, plus one file that disagrees with itself, leave a lot to chance.

How do you resolve it in your own copy?

A skill is a markdown file in your project or home directory. You can edit it. Two small fixes, pick one:

Keep the ban strict. Delete the gradient options so the later sections agree with section 2:

- 6. Ensure sections have visual depth through imagery, ambient gradients, or subtle textures
+ 6. Ensure sections have visual depth through imagery or subtle textures. No gradients.

Then remove the radial-gradient clause from section 6 and the "Background Ambient Motion" line from section 7.

Allow the tint, and say so. Scope the ban instead:

- - DO NOT use gradients, neon colors, or 3D glassmorphism (beyond subtle navbar blurs).
+ - DO NOT use gradients (except a single warm radial-gradient at opacity 0.04 or lower), neon colors, or 3D glassmorphism (beyond subtle navbar blurs).

The + lines are ours. The - line in the first diff is cut short: upstream it goes on to forbid empty flat backgrounds. If you take the second option, change the description line too, because "No gradients" is what the agent sees first.

Your edit lives in your copy only. Reinstalling the skill can overwrite it, so keep the changed file in version control.

Is the rest of the file consistent?

Mostly, from our reading. The shadow rules look like a conflict and are not one. Section 2 bans shadow-md, shadow-lg and shadow-xl, and allows shadows that are "ultra-diffuse and low opacity (< 0.05)". The card hover in section 7 uses rgba(0,0,0,0.04), which is under that line. The pill rule holds up as well: rounded-full is banned for "large containers, cards, or primary buttons", while tags and status badges are pill-shaped on purpose.

One more thing to know before you ship. The line that makes prefers-reduced-motion mandatory was written on Jun 21, 2026 (commit 541c36ba) and merged into main on Oct 11, 2026 (PR #58). A copy installed before that merge does not have it. Step 5 of the checklist still says "Add scroll-entry animations to all major content blocks." Check that generated pages gate those animations.

FAQ

Does minimalist-ui allow gradients?

The file says both. Its description and section 2 ban gradients. Sections 6, 7 and 8 list a low-opacity radial-gradient or "ambient gradients" among the options for depth. This is the text at commit d237dd39, read on Oct 13, 2026.

How many things does minimalist-ui ban outright?

Nine. Section 2 has nine "DO NOT" lines covering Inter, Roboto and Open Sans, thin-line icon sets such as Lucide, heavy Tailwind shadows, primary-colored sections, gradients, pill-shaped large containers, emojis, placeholder names and a list of copywriting cliches.

Should you load minimalist-ui with another style skill?

Pick one style skill per project. The Skillselion listing for the minimalist-ui skill shows the others from the same repo, and the frontend design skills ranking compares the category by installs. If you want variance and density controls and no fixed look, our design taste skill guide covers that one.

Last updated: Oct 13, 2026.