WebFV
Agent skills / Field guide

Install Taste Skill in Claude Code

Choose the current skill, find moved packages, and check what actually installed.

By WebFV Editorial · Checked October 21, 2026 · Taste Skill v2.1.4 reference

What the evidence coversProject-local installation checked; design quality and browser inspection are not benchmarked.

Which Taste Skill should you install?

For the current Taste Skill workflow, install design-taste-frontend from Leonxlnx/taste-skill. It is a set of instructions your coding agent reads, not an MCP server to add to a JSON server list. You do not need an API key or an MCP registration merely to install the skill.

This guide covers a project-local Claude Code installation. The upstream reference checked for this guide is v2.1.4, dated October 20, 2026. The installation command follows the repository's default branch, so it can produce a later revision when you run it. Record the revision in your project's lockfile if you need a reproducible installation.

Install into one project

Open a terminal in the project where you want the skill. Review the official repository before installing: a skill contains instructions and can reference scripts that your agent may run.

npx skills add https://github.com/Leonxlnx/taste-skill \
  --skill design-taste-frontend --agent claude-code

The skills installer can ask where to install. Choose the current project for a bounded first test. A global installation makes the skill available across projects, which is a different scope. Do not select every agent just to get past the prompt.

The command is an installer invocation, not a prompt for Claude. After it finishes, return to the coding client and open that same project. If the client was already running, start a fresh session so its skill inventory can refresh. A terminal success message alone does not prove the agent has discovered the skill.

Verify the files and discovery separately

Check that the installed package contains a readable SKILL.md with the name design-taste-frontend. Depending on the installer version, the actual files can live under a shared project skills directory, with a Claude-specific link pointing there. Resolve that link before treating an empty-looking directory as a failed install.

Ask the agent to use design-taste-frontend on a small, reversible UI task. For example: “Use design-taste-frontend to improve the spacing and typography of this static settings page. Keep the existing behavior.” Read its proposed changes and compare the rendered page at desktop and phone widths.

There are three separate checks: files exist, the client discovers the skill, and the resulting interface meets your needs. Only the first is established by a filesystem installation test. No skill can guarantee a particular visual score or that every generated layout will be accessible.

Where did the other Taste skills go?

Skill you remember Current destination or replacement
design-taste-frontend Main taste-skill repository
high-end-visual-design, minimalist-ui, industrial-brutalist-ui taste-skill-classics
gpt-taste, stitch-design-taste, older v1 / experimental v2 taste-skill-classics
imagegen-frontend-web, imagegen-frontend-mobile, brandkit, image-to-code imagegen-skills
redesign-existing-projects Merged into design-taste-frontend
full-output-enforcement Removed; see the current unlazy reference

Use the upstream moved-skills table to follow current links. Do not fix a missing package by downloading an unrelated repository with a similar name. An older tutorial that installs every historical skill can be correct for its date and wrong for today's repository layout.

If the skill does not appear

First check the project path. An installation made in a temporary directory will not automatically appear in a different project. Then check the client chosen in the installer and the skill directory or link it created. Refresh the coding session after installation.

If the name still does not match, compare the installed front matter with the current repository. Issue 76 documents an older naming problem; its existence does not prove the current release has the same defect. Record the installer output and revision before attempting a reinstall.

The current upstream workflow includes browser inspection and requires a suitable Node and Chromium-family environment for those steps. Installing instructions and successfully running a browser inspector are separate milestones. Do not enable an inspector on a sensitive browser profile without reviewing how it connects and what it captures.

Test boundary and next step

Our installation check uses a temporary project, leaving existing personal skills untouched. It checks the package files, not the quality of a generated website or every supported client. For MCP configuration problems, use the local configuration checker; Taste Skill itself does not belong in that server configuration.