Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By Owl-Listener
Build accessible user stories, personas, and scenarios from the start — maps product features across ability spectrums (vision, hearing, motor, cognition), audits stories for disability inclusion gaps, and generates diverse personas with built-in accessibility acceptance criteria for keyboard, screen reader, visual, motor, and cognitive needs.
npx claudepluginhub owl-listener/inclusive-design-skills --plugin inclusive-personasMap how a product or feature works across the full spectrum of human ability — not just 'can use' and 'can't use'. Use when planning accessibility coverage, identifying gaps, or communicating accessibility scope to stakeholders. Triggers on: ability spectrum, range of users, who can use this, who can't use this, accessibility coverage, accessibility scope, ability range, spectrum of needs.
Write usage scenarios that include assistive technology and diverse interaction methods. Use when writing scenarios, use cases, user journeys, or storyboards. Triggers on: assistive technology, AT, screen reader, switch, voice control, magnifier, braille display, head pointer, eye tracking, how people use our product, usage scenario, use case.
Audit user stories for disability inclusion. Chains: inclusive-user-stories, edge-case-identification. Use when reviewing an existing backlog, sprint, or set of user stories to check whether they account for diverse abilities.
Create user personas that include disability as a natural dimension of human diversity — not as a separate 'accessibility persona'. Use when creating personas, user profiles, proto-personas, or any representation of target users. Triggers on: persona, user persona, proto-persona, user profile, target user, who is the user, disability persona, accessibility persona, inclusive persona.
Identify and design for edge cases that disproportionately affect users with disabilities. Use when reviewing designs for completeness, planning test cases, or when someone says 'that's an edge case.' Triggers on: edge case, corner case, that's unlikely, only a few users, exception, unusual scenario, we'll handle that later, happy path, unhappy path, error state, empty state.
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 multi-modal interactions that adapt to how people move, perceive, and communicate.
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.
Design workflow for coding agents: discovery, research, strategy, inclusive design, critique, and handoff — enforced automatically
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.
UX/マーケティング向けのユーザーペルソナを、5つの専門エージェントチームで作成するスキル。 ペルソナ設計、ユーザーリサーチ、ナラティブ執筆、バイアスレビュー、データ検証の 5観点からペルソナをディスカッション型で議論・作成し、Markdownドキュメントとして出力する。 data-critic がライブモデレーターとして矛盾を検出・収束を判定する。
User research skills for designers: personas, empathy maps, journey maps, interview scripts, usability testing, and card sorting.
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.