Design vs Testing · both proven

design-taste-frontend vs receiving-code-review

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

receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Category: Testing
Source: obra/superpowers
License: MIT
Proof model: claude-opus-5-5
Brief: “I received this code review on my pull request that adds caching to our product API. Decide what to do with each comment and present your responses and planned changes as a single HTML page. 1. "Cache TTL of 24h is too long, prices change during the day." 2. "Use Redis instead of the in-memory Map so all 4 instances share the cache." 3. "Rename getProd to getProduct." 4. "You should rewrite this whole module in TypeScript." 5. "The cache key ignores the currency query param, so EUR users can get USD prices." 6. "Add a test."”
Skill commit: 2ce8aa1

Without the skillWith receiving-code-review

⇆

Without, runWith receiving-code-review, 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 receiving-code-review.