.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/owl-listener/inclusive-design-skills
home/skills/owl-listener/inclusive-design-skills
owl-listener avatar

owl-listener/inclusive-design-skills

50 skills

View on GitHub
$npx skills add owl-listener/inclusive-design-skills
SkillInstalls
ability-spectrum-mappingMap how a product or feature works across the full spectrum of human ability — not just 'can use' and 'can't use'.—accessibility-debt-trackingTrack and manage accessibility debt — known accessibility issues that have been deferred.—accessibility-testing-strategyPlan what to test, how to test, and who should test for accessibility.—adaptive-personalisationDesign help systems and support patterns that work for people with cognitive disabilities.—alt-text-designWrite meaningful alternative text for images, charts, diagrams, and visual content.—assess-loadAssess cognitive load across a complete multi-step process and produce a load map.—assistive-technology-scenariosWrite usage scenarios that include assistive technology and diverse interaction methods. Use when writing scenarios, use cases, user journeys, or storyboards.—auditAudit an interface for multi-modal interaction support. Chains: keyboard-navigation, touch-target-design, multi-modal-input, gesture-alternatives,…—audit-storiesAudit user stories for disability inclusion. Chains: inclusive-user-stories, edge-case-identification.—cognitive-load-assessmentAssess and reduce cognitive load in interfaces, flows, and content.—colour-independenceDesign interfaces where colour is never the only way information is communicated.—compliance-mappingMap design decisions to accessibility standards and legal requirements.—contextual-help-designdecision-documentationDocument accessibility decisions and the reasoning behind them so they survive team changes, redesigns, and time.—design-flowDesign an interaction flow with inclusive input and output options from the start.—documentDocument accessibility decisions and tradeoffs for a feature. Chains: decision-documentation, tradeoff-analysis, compliance-mapping.—error-prevention-recoveryDesign error prevention, error messages, and recovery flows for cognitive accessibility.—feedback-and-statusDesign feedback and status communication that works across senses — visual, auditory, and haptic.—flexible-typographyDesign typography systems that adapt to user needs — scaling, spacing, and font preferences.—focus-attention-designDesign interfaces that support sustained focus and reduce distractions.—form-labellingDesign form labels, instructions, and grouping that work for screen readers and cognitive accessibility.—gesture-alternativesDesign alternatives to gesture-based and motion-based interactions.—handoffGenerate an accessibility decision handoff for engineering. Chains: decision-documentation, compliance-mapping, accessibility-testing-strategy.—heading-structureDesign heading hierarchies and content structure that work for screen readers and cognitive accessibility.—information-densityDesign interfaces where information density can be adjusted to suit different cognitive needs and preferences.—keyboard-navigationDesign keyboard navigation and focus management for users who cannot or prefer not to use a mouse or touch screen.—keyboard-reviewReview keyboard navigation and focus management in an existing interface. Chains: keyboard-navigation, feedback-and-status.—link-text-designWrite link text that makes sense out of context for screen reader users and improves usability for everyone.—memory-load-reductionDesign interfaces that minimise demands on working memory. Use when designing multi-step flows, dashboards, comparison tools, forms that span multiple screens,…—motion-sensitivityDesign for people with vestibular disorders, motion sensitivity, or seizure conditions.—multi-modal-inputDesign interfaces that offer multiple input methods so users can choose what works for their abilities and context.—multimedia-accessibilityDesign accessible video, audio, and multimedia content with captions, transcripts, and audio descriptions.—plain-language-designWrite and review content for plain language accessibility. Use when writing interface copy, error messages, instructions, onboarding text, help content, legal…—preference-auditAudit an existing interface for respect of user preferences including motion, contrast, colour scheme, and text scaling.—readable-contentWrite and structure content for diverse reading abilities and cognitive styles.—responsive-accessibilityDesign responsive layouts that maintain accessibility across screen sizes, zoom levels, and orientations.—responsive-reviewReview responsive and flexible layout for accessibility across devices, zoom levels, and orientations.—reviewReview and surface undocumented accessibility assumptions in an existing feature or product.—rewriteRewrite content in plain language while preserving meaning. Chains: readable-content, link-text-design.—simplified-viewsDesign simplified and reduced-complexity views of interfaces for users who need less visual noise and fewer options.—simplifySimplify content and interactions to reduce cognitive load. Chains: plain-language-design, cognitive-load-assessment, focus-attention-design.—specifySpecify adaptive behaviour for an interface. Chains: user-preference-respect, responsive-accessibility, flexible-typography, colour-independence,…—stakeholder-communicationCommunicate accessibility decisions, requirements, and value to stakeholders who aren't accessibility specialists.—structureStructure content for screen reader and assistive technology use. Chains: heading-structure, alt-text-design, table-accessibility, form-labelling.—table-accessibilityDesign data tables that work for screen readers and cognitive accessibility.—touch-target-designDesign touch targets and pointer interactions that work for people with motor difficulties, tremors, limited dexterity, or who use assistive pointing devices.—tradeoff-analysisAnalyse accessibility tradeoffs when a design decision improves accessibility for one group but may affect another, or when accessibility competes with other…—user-preference-respectDesign interfaces that detect and respond to system-level user preferences.—voice-interactionDesign voice interactions and speech interfaces that work for people with diverse speech patterns, accents, and communication styles.—wayfinding-navigationDesign navigation and information architecture for cognitive accessibility.—