agentleFS
Sign inStart free
podopodo/design-agent-skills/skills/taste-skill/SKILL.md

taste-skill

Skill32 starsChanged 6 months agoMITView on GitHub

Anti-slop frontend art direction (tasteskill v2). Deals researched design directions for a page or app screen from a library built from curated gallery sites, enforces a strict no-generic-AI-UI house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Works in any web stack.

15 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use animation-vocabulary, apple-design and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • attentiondotnetSkill

    animation-vocabulary

    Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.

    Also in 3 projects that use this

  • ozgureyilmazSkill

    apple-design

    Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.

    Also in 3 projects that use this

  • VercelSkill

    emil-design-eng

    This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

    Also in 3 projects that use this

  • VercelSkill

    web-design-guidelines

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    Also in 4 projects that use this

  • GoogleSkill

    prototype

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

    Also in 4 projects that use this

  • GoogleSkill

    grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

    Also in 3 projects that use this

  • +1 more from google

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user explicitly wants generic or template-style UI

    line 85

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

taste-skill

Catalogue stub — full skill: Leonxlnx/taste-skill

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed? Upstream names this skill design-taste-frontend, so it installs next to this pointer (the pointer is not replaced).
    • Global: f=~/.agents/skills/design-taste-frontend/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/design-taste-frontend/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → the skill is installed as design-taste-frontend, invoke it and proceed
    • pointer → go to step 2

  2. Detect scope, then install:

    [ -e ~/.agents/skills/taste-skill ] && echo "global" || echo "project"

    Global:

    npx skills add Leonxlnx/taste-skill --skill design-taste-frontend -g -y

    Project:

    npx skills add Leonxlnx/taste-skill --skill design-taste-frontend -y

    Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Claude Code plugin route:

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

Heads-up

  • Requires: Node.js 22 or later and an installed Chrome, Edge or Chromium (for the bundled inspector and screenshot scripts); network access for the asset script (it fetches pictures from open collections, no API keys)
  • License: MIT
  • Download size: ~39 MB.
<!-- das:install:end -->

Invoke after install

  • Skill name: design-taste-frontend
  • Trigger phrases: "design taste", "good taste", "anti slop", "premium UI", "make this look designed", "this page looks generic"

What it does

Art direction for websites and app screens, aimed at the generic look models default to (centred headline over three lines, a small label, a row of icon cards, a soft gradient). A script deals a few researched directions (idea, composition, type system, palette, hero and section blueprints, pictures of the subject's world) and you choose one; a house style with no ornaments is then measured in a real browser by an inspector script, and you look at screenshots at several widths, judge them against a rubric, fix, and look again. A separate run covers app screens such as dashboards, settings and inboxes. Use it whenever you build, restyle or review a landing page, product page, portfolio, one-pager or dashboard, or when a page looks generic or "AI-made".

The bundled scripts need Node 22+ and an installed Chrome, Edge or Chromium; one script fetches pictures from open collections over the network. Working files are written to .taste-skill/ in your project root.

When NOT to use

  • Backend code, APIs, data pipelines, CLI tools, or any non-UI task
  • When the user explicitly wants generic or template-style UI
  • Native iOS or Android interfaces (use mobile-app-design or swiftui-design-skill)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free