Design vs Testing · both proven

design-taste-frontend vs test-driven-development

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

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

Category: Testing
Source: obra/superpowers
License: MIT
Proof model: claude-opus-5-5
Brief: “Implement a function that parses a cron expression (the standard five fields) and returns the next run time after a given date, in TypeScript. Present the work as a single HTML page with two columns: the test file on the left and the implementation on the right, each in a code block, with a short note at the top on the order you did things in and anything you decided not to support.”
Skill commit: bb92a77

Without the skillWith test-driven-development

⇆

Without, runWith test-driven-development, 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 test-driven-development.