Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By Owl-Listener
Document, communicate, and maintain accessibility decisions across teams and time, including tracking debt, mapping to WCAG compliance, planning layered testing, and translating designs into engineer-ready specs with context and tradeoffs.
npx claudepluginhub owl-listener/inclusive-design-skills --plugin accessibility-decisionsTrack and manage accessibility debt — known accessibility issues that have been deferred. Use when managing a backlog of accessibility issues, planning remediation, or when accessibility problems are accumulating faster than they're being fixed. Triggers on: accessibility debt, tech debt, known issues, backlog, deferred, we'll fix it later, remediation, accessibility backlog, accumulating issues, regression.
Plan what to test, how to test, and who should test for accessibility. Use when defining a testing approach, planning QA, setting up automated and manual testing, or deciding what level of accessibility testing a project needs. Triggers on: accessibility testing, how to test, test plan, automated testing, manual testing, screen reader testing, user testing, accessibility QA, what to test, testing strategy.
Map design decisions to accessibility standards and legal requirements. Use when documenting WCAG conformance, preparing for audits, tracking compliance status, or when legal or procurement requires accessibility documentation. Triggers on: WCAG, compliance, conformance, audit, VPAT, accessibility statement, legal requirement, ADA, EAA, European Accessibility Act, Section 508, EN 301 549, accessibility standard, success criterion.
Document accessibility decisions and the reasoning behind them so they survive team changes, redesigns, and time. Use when making accessibility tradeoffs, choosing between approaches, or when a decision needs to be recorded for future reference. Triggers on: accessibility decision, why did we, tradeoff, decision record, ADR, architecture decision, accessibility rationale, why is it like this, document the decision, decision log.
Document accessibility decisions and tradeoffs for a feature. Chains: decision-documentation, tradeoff-analysis, compliance-mapping. Use when a feature is being designed or shipped and accessibility decisions need to be captured.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Design for how people actually think: cognitive load, plain language, wayfinding, focus, memory, and error recovery.
Accessibility specialist skills for Claude Code and Codex. WCAG 2.2 review, conformance auditing, and improvement planning tools.
Design & UX skills: UX Research Plan, Design Critique, Accessibility Audit. Create research plans with discussion guides, critique designs using JTBD and Gestalt principles, and audit for WCAG 2.2 compliance.
Design workflow for coding agents: discovery, research, strategy, inclusive design, critique, and handoff — enforced automatically
Design with Intent. A comprehensive UX and design strategy system — 16 specialized skills and 6 named agents covering strategy, research, experience design, quality assurance, accessibility, measurement, and engineering handoff.
Build, document, and maintain scalable design systems — from tokens and components to accessibility and theming.
Craft polished user interfaces with layout grids, color systems, typography scales, responsive patterns, and visual hierarchy.
Plan and execute design validation through prototyping strategies, usability testing, heuristic evaluation, and A/B experiments.
Shape product direction through competitive analysis, design principles, experience mapping, and strategic alignment.
User research skills for designers: personas, empathy maps, journey maps, interview scripts, usability testing, and card sorting.
Design meaningful interactions with micro-animations, state machines, gestures, error handling, and feedback patterns.
Part of the Designer Skills suite. Install this collection and four more with one command in Claude Code:
/plugin marketplace add Owl-Listener/designer-skillsThis repo still works on its own. The suite just gives everyone one front door.
Agentic skills for designing accessible, inclusive products — from cognitive accessibility to adaptive interfaces, inclusive research, and accessibility decision-making. 40 skills and 18 commands across 6 plugins.
Works with any AI coding agent that supports the SKILL.md format: Claude Code, OpenAI Codex, Gemini CLI, Cursor, and others.
Every accessibility skill set that exists today is engineer-facing. They audit code, check WCAG compliance, validate ARIA attributes, and flag contrast ratios. They treat accessibility as a technical implementation problem that gets caught at the end.
This collection operates before code. It shapes decisions about information architecture, language, interaction patterns, cognitive demands, and inclusion — the design layer that determines whether something is genuinely usable, not just technically compliant.
Accessibility isn't a code review. It's a design commitment.
| Plugin | Skills | Commands | Description |
|---|---|---|---|
| cognitive-accessibility | 8 | 3 | Design for how people actually think: cognitive load, plain language, wayfinding, focus, memory, and error recovery. |
| inclusive-interaction | 7 | 3 | Design multi-modal interactions that adapt to how people move, perceive, and communicate. |
| accessible-content | 7 | 3 | Structure content that works for screen readers, cognitive differences, and diverse literacy levels. |
| inclusive-personas | 6 | 3 | Build user stories, personas, and scenarios that include disability from the start. |
| adaptive-interfaces | 6 | 3 | Design systems that respect user preferences and adapt to individual needs. |
| accessibility-decisions | 6 | 3 | Document, communicate, and maintain accessibility decisions across teams and time. |
Add the marketplace:
/plugin marketplace add Owl-Listener/inclusive-design-skills
Then run /plugin, open the Discover tab, and install the plugins you want.
Or get this collection plus four more in one go, through the full suite:
/plugin marketplace add Owl-Listener/designer-skills
Skills use the universal SKILL.md format. Copy the skill folders into your tool's skills directory, or reference them directly from this repo. Each SKILL.md file works as a standalone instruction set.
For manual use without a coding agent: open any SKILL.md file, copy the contents, and paste it as context at the start of a conversation with any AI assistant. The frameworks and decision criteria work regardless of the tool.