Design vs Docs & Writing · both proven

accessibility-compliance vs writing-plans

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,107 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

writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

Category: Docs & Writing
Source: obra/superpowers · 301,959 stars
License: MIT
Proof model: claude-opus-5-5
Brief: “Write the implementation plan for adding team accounts to a solo-user invoicing SaaS (Next.js, Postgres, Stripe): users must be able to create a team, invite members by email, assign owner or member roles, and share clients and invoices within the team, with billing moving from the user to the team. Present the plan as a single HTML page.”
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 writing-plans.