“Make it premium” is a mood. A product needs a direction someone can point at, a review with a result, and sometimes a component that already exists.
Missing constraints were yesterday’s problem. The next failure is a page that looks decided because the prompt used an adjective. Direction, inspection, and reuse answer three different gaps. None of them gives a coding agent an objective sense of beauty.
The same pattern holds: judgment is being written down because the model does not arrive with it.
-
Taste Skill. It deals an art direction from a researched set, brings in credited reference imagery, checks the page in a browser, and revises from screenshots. The README puts a build at roughly 30 to 45 minutes and a few hundred thousand tokens. App screens take a separate path, with their own checks. That is a procedure with a cost, not a faculty the model suddenly has.
-
Impeccable. Already covered in this series, and back here because the job is review rather than another visual style. The current README lists 24 commands and 62 deterministic detector rules, and names Claude Code, Codex, and Cursor among its hosts. The command surface differs by host.
/impeccable auditwrites a report. A clean run is evidence. It is not proof of accessibility, and it is not proof the product is ready to ship. -
React Bits. A component library of animated React components and backgrounds, shipped as source in JavaScript or TypeScript and CSS or Tailwind. Agents can discover them through the documented shadcn registry. Adding one is still integration work. The license is MIT plus a Commons Clause: use inside your product is allowed; selling or redistributing the components, the bundled tools, or the sound library is not.
Name a direction when the prompt is only a mood. Review when a page already exists. Reuse a component when the effect has a maintainer and a license you can accept. You do not need all three on every screen.
Review starting point, not a release standard:
- Does it fit the user’s task and the product’s design system?
- Does it work across the required devices and browsers?
- Can people use it with a keyboard and reduced motion?
- Have you checked loading, empty, error, and long-content states?
- Have you reviewed performance, dependencies, and licensing?
A more specific prompt still ends in a diff. Someone on the team has to accept it.
Source: github.com/Leonxlnx/taste-skill — README. github.com/pbakaus/impeccable — README (24 commands, 62 deterministic detector rules). github.com/DavidHDev/react-bits — README and LICENSE.md. Retrieved 23 October 2026.
#AgentSkills #ProductDesign #Frontend