taste-skill
Taste Skill organizes a coding agent’s website work around page classification, typography, color, visual material and browser inspection. It is relevant to developers who want a consistent company-site direction and are willing to accept the project’s visual conventions. The pinned 2.5.0 revision contains the design-taste-frontend skill; the commit is recorded alongside the version because older descriptions cover a different collection. We reviewed its deterministic scripts rather than installing the skill in an everyday host or asking a model to generate a site.
On macOS with Node.js and isolated Chrome profiles, we listed software typography choices, generated CSS from an explicit palette and type pairing, and checked refusal of missing or invalid page kinds. Two handwritten HTML pages then exercised the browser checker at 1440, 768 and 390 pixels. A fixed 1600-pixel container produced overflow findings at every width. Allowing the container to shrink removed those specific findings, with no per-width probe errors. The corrected page still had 22 failures and two warnings across the remaining rules, so this is a targeted correction rather than a passing design audit.
Quick mode and disabled sweep left motion, forms and other reported areas unchecked. The rules also encode preferences about company-site composition; teams maintaining dense applications or an existing design system should assess their fit. We did not measure visual quality, conversion rates, host activation or token savings, and did not verify the full image collection. Choose it for a bounded trial when explicit visual constraints and repeatable layout feedback match the work; preserve the omission list and manually inspect the resulting page.
Read the full review, verification scope and sources →Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-07
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 9
- Latest release
- v2.5.1 (2026-11-07)
- Open issues
- 6
- Recent issues with at least one comment
- 14/26
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #183 Website v2 Prompt Guide references missing sections 11.B, 11.D, Section 14, and undefined dials1 comments · 2026-10-30
- #202 Local servers serve files outside the served folder; headless Chrome exposes an unauthenticated debugging port0 comments · 2026-11-11
- #201 missing references/critique.md0 comments · 2026-11-11
- #200 claude.ai can't sync the plugin since 2.1.1: missing .claude-plugin/plugin.json0 comments · 2026-11-10
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You build company sites and want explicit visual constraints.
- You can run Chrome checks and manually review the output.
- Your product needs a different composition or strict existing tokens.
- You need evidence of model, business or token improvements.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!