
Document
- 33 installs
- 87 repo stars
- Updated June 9, 2026
- owl-listener/inclusive-design-skills
Helps with ai & agent building tasks during AI-assisted development.
About
document is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.
- document
- AI & Agent Building
- AI-coding skill
Document by the numbers
- 33 all-time installs (skills.sh)
- +5 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #8,975 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/inclusive-design-skills --skill documentAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 33 |
|---|---|
| repo stars | ★ 87 |
| Last updated | June 9, 2026 |
| Repository | owl-listener/inclusive-design-skills ↗ |
What it does
Helps with ai & agent building tasks during AI-assisted development.
Files
Document Accessibility Decisions
Capture all accessibility decisions for a feature in a single, structured record that will survive team changes and redesigns.
Process
Step 1: Identify Decisions
List every design or implementation choice that affects accessibility:
- Interaction patterns chosen
- Content and language decisions
- Visual design decisions
- What was included and what was deferred
- Tradeoffs made under constraints
Step 2: Document Each Decision
Using decision-documentation, for each decision record:
- Context: what prompted the decision
- Decision: what was chosen
- Alternatives: what was considered and rejected
- Impact: who benefits, who is affected
- Evidence: what supported the decision
Step 3: Analyse Tradeoffs
Using tradeoff-analysis, for any decision where accessibility was compromised or where user needs conflicted:
- Who benefits from each option
- Who is harmed by each option
- Severity asymmetry (blocked vs friction)
- Remediation plan for excluded users
- Review date
Step 4: Map to Standards
Using compliance-mapping, map each decision to the relevant WCAG criteria:
- Which criteria does this decision satisfy
- Which criteria does this decision affect
- Are there any conformance risks
Output
Deliver a feature accessibility decision record:
1. Feature summary — what was built and for whom 2. Decision log — each decision in the standard format 3. Tradeoff register — any tradeoffs with remediation plans 4. Compliance map — WCAG criteria coverage and gaps 5. Open items — deferred decisions that need future resolution