Our take Editorial verdict
Taste Skill makes an aesthetic recommendation falsifiable in useful ways: the direction comes from a library, imagery has sources, and a real browser measures what shipped. Separating a page that persuades from a screen someone works in is a meaningful correction to one-size-fits-all anti-template advice.
Best for
Public-facing sites needing a subject-specific concept and a concrete visual inspection loop.
Keep in mind Limits and tradeoffs
Source inspection only; the underlying study is the author’s evidence, not our benchmark. The house rules are unusually restrictive, and full inspection requires a recent Node runtime and Chromium-family browser.
How to build a site around its subject and content
- Provide the subject, real content and assets, audience and working behavior to preserve.
- Ask for a subject-specific direction with sourced imagery and an editable implementation.
- Inspect the actual browser result on desktop and mobile, review source checks and resolve visual or behavioral regressions.
This is a source-based editorial review. No retained execution or installation test is published here. The starter request is illustrative, not an observed result. Check the setup and compatibility caveats before using it.
Explore Taste Skill · Skill reference and original instructions
Try this skill
Install · Individual skill
Run in a terminal from your target project. Requires Node.js 22.20+, npm/npx, Git and network access.
npx skills@latest add Leonxlnx/taste-skill --skill design-taste-frontend -a claude-code
Command / route checked 30 October 2026. Upstream installationCLI optionsAgent support
Setup requirements and caveats
Run in a terminal from the target project. Requires Node.js 22.20+ (current skills CLI), npm/npx, Git and network access. Review the installer summary before confirming. Keeps this skill’s supporting files.
Node 22+ and Chrome, Edge or Chromium for full inspection; network access for asset search
These are documented requirements; installation has not been tested here.
Your agent needs its own account, runtime and model access. Usage charges depend on your plan; unrecorded costs are unknown.
Run the example
Start a fresh session in the target project. Provide the relevant files or diff. This is the review’s example request, not a record of your execution.
Use the design-taste-frontend skill. Redesign this independent cinema website around its actual building and programme, preserving booking behavior and comparing mobile before and after.
Check your result · Successful first run
A subject-specific site direction, editable implementation and browser checks at desktop and mobile widths.
Confirm the agent loaded the named skill, inspect the output and run the relevant checks. Installation alone does not prove a successful run.
Something not working?
The skill is missing from my agent
Check that the skill is installed for the selected agent and project/global scope. Open a fresh session in that project and check the agent’s skill list. Plugin installs may also need to be enabled.
The wrong skill runs, or nothing happens
Start a fresh conversation, explicitly name the skill using the request above, and provide the requested inputs. Ask the agent to confirm which skill it loaded. Check for duplicate installed copies or overlapping instructions.
The skill runs but the result is poor
Compare the result with the successful-first-run check above. Supply the missing files, reproduction steps or constraints, then ask for one focused correction. If the skill addresses a different problem, return to the task guide and compare alternatives.
Installation troubleshooting · missing dependencies
If npx fails, check the Node/npm versions in setup requirements, Git and network access. For skills CLI installs, run npx skills list (add -g for global). If a route changed, follow upstream instructions.
Collection background and tradeoffs
Source review only; the author’s study and quality claims have not been independently reproduced. The v2 workflow is experimental, and its strict house style is an opinion rather than a universal design standard. Full inspection needs Node 22+ and Chrome, Edge, or Chromium; asset search needs network access. The frontmatter install name is design-taste-frontend even though its folder is taste-skill.
Source maintained by Leon. Read original skill. Compatibility guidance and published showcase runs remain separate from your first run.
Evidence and provenance Sources and retained files
Evidence and provenance
No executed test recorded. Compatibility guidance and source review do not establish tested behavior.
Source reviewed
Source review date:
Instructions and supporting source reviewed; no design, lint, or export execution recorded.
Evidence source · Verified revision: 12af471f627f866411b4bd785b19646d3672784c
Prerequisites: Node 22+ and Chrome, Edge or Chromium for full inspection; network access for asset search