
Set of open skill files that constrain...
When an assistant builds an interface, it often returns to the same cards and the same spacing. These skills turn typography, spacing, color, layout, and motion into rules the assistant reads before it touches the UI, split by task. The default skill handles a new interface: it reads the brief, infers a direction, audits first on a redesign, and runs a check before generating. An existing project can use the audit skill instead. Image-first implementation studies reference images before code. Soft, minimal, and brutalist styles are separate skills. It fits people who already build frontend with a coding assistant and want to switch design direction per page in one repository.
Taste Skill is a set of open skill files that constrain coding assistants which read skill files, so they stop repeating the same templated interface. The default skill reads the brief, infers industry, audience, mood, and layout, then decides whether an existing design system fits. One install also includes a redesign audit, image-first implementation, softer, minimal, and brutalist style skills, plus skills that generate reference images and brand boards. The second version is the current default and is still experimental. The first version remains available by name.
Difficulty: Intermediate
A default skill that reads the brief
The default skill infers industry, audience, mood, motion depth, and layout family, audits first on a redesign, and runs a pre-flight check before generating.
Redesign audit and image-first build
The redesign skill visually audits an existing project. The image-first skill generates references, studies them, and then implements the interface.
Three styles you can call separately
Soft, minimal, and brutalist skills each set contrast, whitespace, hierarchy, and structure so the assistant does not repeat one template.
Reference images and brand boards
Image skills can generate website or mobile reference frames. The brand skill assembles logo ideas, color, type, and mockups.
Set a style from a new-page brief
A frontend developer gives an event-page brief to the default skill so it infers audience and motion before writing the interface.
Audit an existing project first
On a redesign, the redesign skill runs first, points out templated parts, and leaves existing decisions that should stay.
Generate references before code
A design collaborator uses the image skill to make a web reference board, then has the assistant implement the frontend against it.
The page installs it with the skills command pointed at Leonxlnx/taste-skill. It targets assistants that read skill files, and the page names several coding assistants and builders. After install, pick the skill for the task: the default for a new interface, the redesign skill for an existing project, and the image-first skill when you want references before code. One repository does not need a separate install per style.
The page says version two is already the default. It reads the brief and infers a direction, with a stricter ruleset, but it is still marked experimental and the wording may change before the stable release. The install name stays the same. If version two breaks a project that depends on the old behavior, switch to the version-one skill name. A separate variant aimed at particular assistants emphasizes layout variation and motion, and you request it only when you want that.
Yes, through separate image skills rather than the default interface skill. Website references emphasize art direction, typography, and spacing. The mobile skill generates screen flows with a consistent hierarchy. The brand skill assembles logo concepts, color, type, and mockups. Those images are references for a later implementation. Changing an existing page should still go through the redesign audit rather than only producing a new picture.
Real reviews and feedback from users