Design vs Testing · both proven

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

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

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 prototype or alternatives to receiving-code-review.