Design vs Testing · both proven

prototype 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.

prototype

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Category: Design
Source: mattpocock/skills
License: MIT
Proof model: claude-opus-5-5
Brief: “We are designing the order state model for a food delivery app. An order can be placed, accepted by the restaurant, being prepared, ready for pickup, picked up by a courier, and delivered. The customer can cancel until the restaurant starts preparing; the restaurant can cancel at any time before pickup; a cancellation after payment triggers a refund, partial if food was already prepared. We are not sure this logic is right. Build a throwaway prototype as a single HTML page that lets someone on the team drive an order through these states and see where the rules break or get confusing.”
Skill commit: 5beb35b

Without the skillWith prototype

⇆

Without, runWith prototype, run3 independent runs per side, none selected by hand.

Download the with-skill page

systematic-debugging

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

Category: Testing
Source: obra/superpowers
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

Without the skillWith systematic-debugging

⇆

Without, runWith systematic-debugging, 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 prototype or alternatives to systematic-debugging.