Design vs Testing · both proven

accessibility-compliance 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.

accessibility-compliance

Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.

Category: Design
Source: wshobson/agents · 41,103 stars
License: MIT
Proof model: claude-opus-5-5
Brief: “Build the settings page for a team workspace app with tabs for Profile, Notifications and Privacy, including toggles, a select menu, a danger zone, and save and cancel buttons with success and error states. Make it fully keyboard-navigable and screen-reader friendly, and make it look like a finished product.”
Skill commit: 0874a27

test-driven-development

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

Category: Testing
Source: obra/superpowers · 301,947 stars
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

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 accessibility-compliance or alternatives to test-driven-development.