Design vs Testing · both proven

design-taste-frontend vs writing-guidelines

Both skills were run through Claude twice: once on a fixed brief without the skill, once with it. The briefs differ because each is written for the job the skill claims to do, so compare each skill against its own baseline, then decide which difference matters for your work. They are in different categories, so this is a choice of job, not a head-to-head on the same job.

design-taste-frontend

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use…

Category: Design
Source: Leonxlnx/taste-skill
License: MIT
Proof model: claude-opus-5-5
Brief: “Build the homepage for Fieldnote, a field-recording gear shop run by two sound engineers in Portland. Include a hero, a featured kit of three recorders and microphones, a short story about how they test every item outdoors, customer reviews, a newsletter sign-up, and a footer. Draw product shots with inline SVG and CSS.”
Skill commit: 6010f91

Without the skillWith design-taste-frontend

⇆

Without, runWith design-taste-frontend, run3 independent runs per side, none selected by hand.

Download the with-skill page

writing-guidelines

Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".

Category: Testing
Source: vercel-labs/agent-skills
License: Not stated
Proof model: claude-opus-5-5
Brief: “Review and rewrite this getting-started page for Pipewell, a data pipeline CLI. The draft opens with two paragraphs of company history, mixes 'you' and 'the user', buries the install command in the fourth paragraph, uses passive voice throughout, and ends without a next step. Write the improved page as a single HTML document, followed by a short list of what you changed and why.”
Skill commit: 063bee9

Without the skillWith writing-guidelines

⇆

Without, runWith writing-guidelines, run3 independent runs per side, none selected by hand.

Download the with-skill page

We don’t pick a winner for you: the pages are the evidence. Both proofs can be repeated with the brief, model and commit shown above. See alternatives to design-taste-frontend or alternatives to writing-guidelines.