Two design skills · both proven

accessibility-compliance vs design-taste-frontend-v1

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.

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,019 stars
License: MIT
Proof model: claude-sonnet-5-5
Brief: “Build a settings page with tabs for Profile, Notifications and Privacy, including toggles, a select menu, and a save button.”
Skill commit: 0874a27

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 · 98,855 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

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 design-taste-frontend-v1.