Typeui Fundamentals
bergside/typeui
Universal UI/UX design principles covering visual hierarchy, interaction laws, typography foundations, and WCAG accessibility requirements.
Document accessibility decisions and the reasoning behind them so they survive team changes, redesigns, and time.
Install Decision Documentation
$ npx skills add Owl-Listener/inclusive-design-skills --skill decision-documentation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills decision-documentation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/accessibility-decisions/skills/decision-documentation .claude/skills/decision-documentation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "decision-documentation" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/decision-documentation into .claude/skills/decision-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-documentation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/decision-documentationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/inclusive-design-skills --skill decision-documentation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills decision-documentation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/accessibility-decisions/skills/decision-documentation .agents/skills/decision-documentation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "decision-documentation" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/decision-documentation into .agents/skills/decision-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-documentation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill decision-documentation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills decision-documentation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/accessibility-decisions/skills/decision-documentation .cursor/skills/decision-documentation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "decision-documentation" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/decision-documentation into .cursor/skills/decision-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-documentation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/inclusive-design-skills.git --path accessibility-decisions/skills/decision-documentation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/inclusive-design-skills --skill decision-documentation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills decision-documentation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/accessibility-decisions/skills/decision-documentation .gemini/skills/decision-documentation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "decision-documentation" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/decision-documentation into .gemini/skills/decision-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-documentation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/inclusive-design-skills decision-documentationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/inclusive-design-skills --skill decision-documentation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/accessibility-decisions/skills/decision-documentation .github/skills/decision-documentation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "decision-documentation" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/decision-documentation into .github/skills/decision-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-documentation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill decision-documentation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills decision-documentation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/accessibility-decisions/skills/decision-documentation .opencode/skills/decision-documentation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "decision-documentation" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/decision-documentation into .opencode/skills/decision-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "decision-documentation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
decision-documentation- GitHub stars
- 103
- Token cost
- ~984 tokens
- SKILL.md length
- 504 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Document accessibility decisions and the reasoning behind them so they survive team changes, redesigns, and time.
- Works in 4 steps: Are accessibility decisions documented… → Can a new team member find out why… → Are tradeoffs explicitly recorded? → …
- Making accessibility tradeoffs
- SKILL.md covers Why This Matters, Decision Record Format, When to Document and Where to Store, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Decision Documentation is an agent skill from Owl-Listener/inclusive-design-skills. 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.
Its SKILL.md is about 980 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Accessibility and Architecture decision records. The repository describes itself as: Inclusive design skills for AI coding agents — from cognitive accessibility to adaptive interfaces, inclusive research, and accessibility decision-making. The licence is MIT.
When your agent uses it
- Making accessibility tradeoffs
- Choosing between approaches
- A decision needs to be recorded for future reference
- : accessibility decision
Example prompts
- “/decision-documentation”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Are accessibility decisions documented with reasoning?
- Can a new team member find out why something was built a
- Are tradeoffs explicitly recorded?
- Is documentation stored where it won't be lost?
What it can do on your machine
Read from SKILL.md and the folder at commit 6e0740f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Decision Documentation loads about 984 tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 504 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/inclusive-design-skills at commit 6e0740f, republished under its MIT licence (© Owl-Listener). 504 words, ~984 tokens.
Download SKILL.mdSave it as
.claude/skills/decision-documentation/SKILL.md (or your agent's skills folder).- name
- decision-documentation
- description
- 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.
Accessibility Decision Documentation
Record accessibility decisions so that future teams understand not just what was decided, but why — preventing the cycle where good decisions get reversed because nobody remembers the reasoning.
Why This Matters
Accessibility barriers accumulate quietly through redesigns, framework updates, staff turnover, and rushed deadlines. The most common cause isn't malice or ignorance — it's a new team member changing something without knowing why it was built that way.
Documentation is the immune system. It protects good decisions from being undone by people who weren't in the room.
Decision Record Format
For each significant accessibility decision, record:
Title
A clear, searchable name. "Form validation: inline errors instead of summary banner"
Date and Author
When was this decided and by whom.
Context
What situation prompted this decision? What were the constraints? "During user testing, 3 out of 5 participants with cognitive disabilities missed the error summary banner at the top of the page. They corrected individual fields but didn't scroll up to see the banner, so they didn't know the form hadn't submitted."
Decision
What was decided, specifically. "All form validation errors will appear inline directly below the field that needs correction. The error summary banner is removed. Errors are announced to screen readers via aria-describedby on each field."
Alternatives Considered
What other options were evaluated and why they were rejected. "We considered keeping the summary banner alongside inline errors, but testing showed it created confusion — users didn't know which error indication to follow."
Accessibility Impact
Who benefits from this decision and how. "Benefits users with cognitive disabilities (don't need to remember which fields had errors), screen reader users (errors announced in context), and all users (faster error correction)."
Show full SKILL.md (225 more words)Show less
Risks and Tradeoffs
What might go wrong or what was sacrificed. "If a form has many errors, the user sees them one at a time as they move through fields, rather than all at once. For long forms, this could mean more scrolling. We accept this tradeoff because contextual errors have higher fix rates in testing."
Evidence
What research, testing, or standards support this decision. "User testing session 2024-03-15 (5 participants, 3 with cognitive disabilities). WCAG 2.2 SC 3.3.1 (Error Identification)."
When to Document
Document a decision when:
- You chose between two or more accessibility approaches
- You made a tradeoff that reduces accessibility in one area to improve it in another
- You decided NOT to fix something (and why)
- You implemented something differently from WCAG techniques for a good reason
- A design pattern was chosen specifically for accessibility reasons
- User testing revealed an accessibility insight that changed direction
Where to Store
- In the codebase alongside the code (preferred — travels with the implementation)
- In a shared decision log (wiki, Notion, Confluence)
- In design system documentation (for system-level decisions)
- Never only in someone's head or in a Slack thread
Assessment Questions
- Are accessibility decisions documented with reasoning?
- Can a new team member find out why something was built a specific way?
- Are tradeoffs explicitly recorded?
- Is documentation stored where it won't be lost?
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in accessibility-decisions/skills/decision-documentation of Owl-Listener/inclusive-design-skills.
Open the folder on GitHubat commit 6e0740f
Compare with similar skills
Decision Documentation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Decision Documentation this skillOwl-Listener/inclusive-design-skills | 103 | — | ~984 | Automated safety check: Pass | MIT | |
| Typeui Fundamentalsbergside/typeui | 2k | — | ~861 | Automated safety check: Pass | MIT | |
| Design Standardsrampstackco/claude-skills | 940 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 98 repos | ~308 | Automated safety check: Pass | None | |
| Accessibility Reviewmarkmead/hyperui | 12k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Web Animation DesignbaptisteArno/typebot.io | 11k | 2 repos | ~2.7k | Automated safety check: Pass | Custom licence |
Similar skills
Design Standards
rampstackco/claude-skills
Apply production-grade design standards when building or reviewing pages, components, or UI.
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
Web Animation Design
baptisteArno/typebot.io
Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.
Accessibility Fixer
ibelick/ui-skills
Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.
More from Owl-Listener/inclusive-design-skills
All 55 skills in this repoAssistive Technology Scenarios
Owl-Listener/inclusive-design-skills
Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks.
Error Prevention and Recovery
Owl-Listener/inclusive-design-skills
Designs forgiving forms and flows: prevent input errors, write messages that say what happened and what to do, and add undo, confirmation and recovery paths.
Accessible Heading Structure
Owl-Listener/inclusive-design-skills
Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.
Ability Spectrum Mapping
Owl-Listener/inclusive-design-skills
Maps a feature across a range of vision, hearing, motor and cognitive ability to find where the design starts to fail, and to explain accessibility scope to stakeholders.
Accessibility Debt Tracking
Owl-Listener/inclusive-design-skills
Track and manage accessibility debt — known accessibility issues that have been deferred.
Accessibility Testing Strategy
Owl-Listener/inclusive-design-skills
Plan what to test, how to test, and who should test for accessibility.
Related
Categories
Questions about Decision Documentation
What does Decision Documentation do?
Document accessibility decisions and the reasoning behind them so they survive team changes, redesigns, and time. Decision Documentation is an agent skill from Owl-Listener/inclusive-design-skills. Document accessibility decisions and the reasoning behind them so they survive team changes, redesigns, and time.
When should I use Decision Documentation?
Decision Documentation fits situations like: making accessibility tradeoffs; choosing between approaches; A decision needs to be recorded for future reference; : accessibility decision.
How do I install Decision Documentation in Claude Code?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill decision-documentation -a claude-code`. Or copy the skill folder (accessibility-decisions/skills/decision-documentation in Owl-Listener/inclusive-design-skills) into .claude/skills/decision-documentation in your project. Claude Code loads it when a task matches its description.
How do I install Decision Documentation in Codex?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill decision-documentation -a codex`. Or copy the skill folder (accessibility-decisions/skills/decision-documentation in Owl-Listener/inclusive-design-skills) into .agents/skills/decision-documentation in your project. Codex loads it when a task matches its description.
Can I use Decision Documentation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/inclusive-design-skills --skill decision-documentation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/decision-documentation, .gemini/skills/decision-documentation, .github/skills/decision-documentation and .opencode/skills/decision-documentation in your project.
What does Decision Documentation need to run?
SKILL.md names no scripts, command-line tools or credentials: Decision Documentation is instructions for the agent only.
Does Decision Documentation access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Decision Documentation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Decision Documentation use?
Decision Documentation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Decision Documentation use?
About 984 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Decision Documentation?
Skills that share tags, products or a category with Decision Documentation: Typeui Fundamentals (bergside/typeui, 2k stars), Design Standards (rampstackco/claude-skills, 940 stars), Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars) and Accessibility Review (markmead/hyperui, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Decision Documentation?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 103 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on June 9, 2026.
Source: Owl-Listener/inclusive-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.