Design vs Testing · both proven

design-taste-frontend-v1 vs systematic-debugging

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-v1

The original taste-skill v1, kept for projects that depend on its exact behaviour. Opt-in: it runs only when called by name.

Category: Design
Source: Leonxlnx/taste-skill · 99,171 stars
License: MIT
Proof model: claude-opus-5-5
Brief: “Build the homepage for Northwind, a two-person brand and web design studio. Include a hero, a selected work section with four projects, services, how they work, a short founder note, and a contact section. Draw any project thumbnails with inline SVG and CSS.”
Skill commit: a9c73c3

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Category: Testing
Source: obra/superpowers · 301,947 stars
License: MIT
Proof model: claude-opus-5-5
Brief: “A Node.js API returns 500 for about 1 in 200 requests to POST /orders. Logs show 'TypeError: Cannot read properties of undefined (reading "id")' at orders.js:48, which reads req.user.id. The route is behind an auth middleware. The failures started after a deploy that added a 30-second cache on the session lookup. Present your diagnosis and fix as a single HTML page: what you checked, in order, the root cause, the code change, and how you would confirm it is fixed.”
Skill commit: bb92a77

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-v1 or alternatives to systematic-debugging.