Typeui Fundamentals
bergside/typeui
Universal UI/UX design principles covering visual hierarchy, interaction laws, typography foundations, and WCAG accessibility requirements.
Analyse accessibility tradeoffs when a design decision improves accessibility for one group but may affect another, or when accessibility competes with other requirements.
Install Tradeoff Analysis
$ npx skills add Owl-Listener/inclusive-design-skills --skill tradeoff-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills tradeoff-analysis --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/tradeoff-analysis .claude/skills/tradeoff-analysis && 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 "tradeoff-analysis" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/tradeoff-analysis into .claude/skills/tradeoff-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tradeoff-analysis", 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/tradeoff-analysisType 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 tradeoff-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills tradeoff-analysis --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/tradeoff-analysis .agents/skills/tradeoff-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tradeoff-analysis" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/tradeoff-analysis into .agents/skills/tradeoff-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tradeoff-analysis", 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 tradeoff-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills tradeoff-analysis --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/tradeoff-analysis .cursor/skills/tradeoff-analysis && 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 "tradeoff-analysis" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/tradeoff-analysis into .cursor/skills/tradeoff-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tradeoff-analysis", 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/tradeoff-analysis--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 tradeoff-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills tradeoff-analysis --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/tradeoff-analysis .gemini/skills/tradeoff-analysis && 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 "tradeoff-analysis" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/tradeoff-analysis into .gemini/skills/tradeoff-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tradeoff-analysis", 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 tradeoff-analysisInstalls 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 tradeoff-analysis -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/tradeoff-analysis .github/skills/tradeoff-analysis && 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 "tradeoff-analysis" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/tradeoff-analysis into .github/skills/tradeoff-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tradeoff-analysis", 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 tradeoff-analysis -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 tradeoff-analysis --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/tradeoff-analysis .opencode/skills/tradeoff-analysis && 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 "tradeoff-analysis" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/tradeoff-analysis into .opencode/skills/tradeoff-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tradeoff-analysis", 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
tradeoff-analysis- GitHub stars
- 105
- Token cost
- ~1k tokens
- SKILL.md length
- 516 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyse accessibility tradeoffs when a design decision improves accessibility for one group but may affect another, or when accessibility competes with other requirements.
- Works in 6 steps: Who Benefits from Option A? → Who Benefits from Option B? → Who Is Harmed by Each Option? → …
- Facing conflicting accessibility needs
- SKILL.md covers When Tradeoffs Happen, Analysis Framework, Tradeoff Documentation and Red Lines, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Tradeoff Analysis is an agent skill from Owl-Listener/inclusive-design-skills. Analyse accessibility tradeoffs when a design decision improves accessibility for one group but may affect another, or when accessibility competes with other requirements. Use when facing conflicting accessibility needs, business pressure to reduce accessibility scope, or technical constraints that limit accessibility options. Triggers on: tradeoff, trade-off, compromise, accessibility vs performance, accessibility vs deadline, conflicting needs, which users, who do we prioritise, can't do both, accessibility…
Its SKILL.md is about 1k 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
- Facing conflicting accessibility needs
- Business pressure to reduce accessibility scope
- Technical constraints that limit accessibility options
- Accessibility vs performance
Example prompts
- “/tradeoff-analysis”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
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
Tradeoff Analysis loads about 1k tokens when it runs. Until then it costs about 135 tokens; SKILL.md has 516 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). 516 words, ~1,025 tokens.
Download SKILL.mdSave it as
.claude/skills/tradeoff-analysis/SKILL.md (or your agent's skills folder).- name
- tradeoff-analysis
- description
- Analyse accessibility tradeoffs when a design decision improves accessibility for one group but may affect another, or when accessibility competes with other requirements. Use when facing conflicting accessibility needs, business pressure to reduce accessibility scope, or technical constraints that limit accessibility options. Triggers on: tradeoff, trade-off, compromise, accessibility vs performance, accessibility vs deadline, conflicting needs, which users, who do we prioritise, can't do both, accessibility scope.
Accessibility Tradeoff Analysis
Analyse accessibility tradeoffs rigorously — because "we can't do everything" is often true, and the quality of the tradeoff decision determines who gets included and who gets excluded.
When Tradeoffs Happen
Conflicting User Needs
- Autoplay captions help deaf users but moving text distracts users with ADHD
- Simplified language helps cognitive accessibility but may feel patronising to some users
- High contrast helps low vision but can cause eye strain for some migraine conditions
Accessibility vs Other Requirements
- Performance: rich accessibility features vs page load speed
- Deadline: full accessibility vs shipping on time
- Complexity: accessible custom component vs simpler but less accessible native element
- Cost: comprehensive testing vs budget constraints
Partial Implementation
- You can make 80% of the feature accessible now and 20% later
- Which 80% do you choose and who does the 20% exclude?
Analysis Framework
For each tradeoff, work through:
1. Who Benefits from Option A?
- Which user groups gain accessibility
- How many users are affected (estimated)
- How severe is the barrier if Option A is not chosen
2. Who Benefits from Option B?
- Same analysis for the alternative
3. Who Is Harmed by Each Option?
- Which user groups lose accessibility or experience degradation
- How severe is the harm
- Is the harm permanent or temporary (will it be fixed later?)
4. What's the Severity Asymmetry?
- A user who CANNOT complete a task (blocked) is more severely affected than a user who finds a task HARDER (friction)
- Prioritise removing blockers over reducing friction
- Prioritise permanent disabilities over situational impairments (situational users have other options; permanent users may not)
5. What's the Reversibility?
- Can this decision be changed later without significant cost?
- If yes: choose the faster option and plan the improvement
- If no: choose the more inclusive option and accept the delay
Show full SKILL.md (223 more words)Show less
6. What's the Precedent?
- Does this decision set a pattern for future features?
- A shortcut taken once becomes a standard if not documented
- If it sets a bad precedent, the long-term cost exceeds the short-term saving
Tradeoff Documentation
Every tradeoff must be recorded using the decision-documentation format with these additional fields:
Who is excluded by this decision: Name the specific user groups affected.
Severity of exclusion: Blocked (cannot complete task) vs friction (harder but possible).
Remediation plan: When and how will the excluded users be served. "Screen reader support for the chart component is deferred to sprint 14. Workaround: data table below the chart provides the same information. Tracked in JIRA-4521."
Review date: When will this tradeoff be reassessed.
Red Lines
Some tradeoffs should never be made:
- Never ship a feature that is completely inaccessible by keyboard
- Never remove existing accessibility to meet a deadline
- Never deprioritise accessibility fixes that block task completion
- Never treat "we'll fix it later" as acceptable without a tracked ticket and a deadline
Assessment Questions
- Have both sides of the tradeoff been analysed for who benefits and who is harmed?
- Is severity asymmetry considered (blocked vs friction)?
- Is there a documented remediation plan for excluded users?
- Has a review date been set?
- Does this decision set a precedent that needs to be managed?
© 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/tradeoff-analysis of Owl-Listener/inclusive-design-skills.
Open the folder on GitHubat commit 6e0740f
Compare with similar skills
Tradeoff Analysis 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 |
|---|---|---|---|---|---|---|
| Tradeoff Analysis this skillOwl-Listener/inclusive-design-skills | 105 | — | ~1k | Automated safety check: Pass | MIT | |
| Typeui Fundamentalsbergside/typeui | 2k | — | ~861 | Automated safety check: Pass | MIT | |
| Design Standardsrampstackco/claude-skills | 945 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 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 Tradeoff Analysis
What does Tradeoff Analysis do?
Analyse accessibility tradeoffs when a design decision improves accessibility for one group but may affect another, or when accessibility competes with other requirements. Tradeoff Analysis is an agent skill from Owl-Listener/inclusive-design-skills. Analyse accessibility tradeoffs when a design decision improves accessibility for one group but may affect another, or when accessibility competes with other requirements.
When should I use Tradeoff Analysis?
Tradeoff Analysis fits situations like: facing conflicting accessibility needs; business pressure to reduce accessibility scope; technical constraints that limit accessibility options; accessibility vs performance.
How do I install Tradeoff Analysis in Claude Code?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill tradeoff-analysis -a claude-code`. Or copy the skill folder (accessibility-decisions/skills/tradeoff-analysis in Owl-Listener/inclusive-design-skills) into .claude/skills/tradeoff-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Tradeoff Analysis in Codex?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill tradeoff-analysis -a codex`. Or copy the skill folder (accessibility-decisions/skills/tradeoff-analysis in Owl-Listener/inclusive-design-skills) into .agents/skills/tradeoff-analysis in your project. Codex loads it when a task matches its description.
Can I use Tradeoff Analysis 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 tradeoff-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tradeoff-analysis, .gemini/skills/tradeoff-analysis, .github/skills/tradeoff-analysis and .opencode/skills/tradeoff-analysis in your project.
What does Tradeoff Analysis need to run?
SKILL.md names no scripts, command-line tools or credentials: Tradeoff Analysis is instructions for the agent only.
Does Tradeoff Analysis 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 Tradeoff Analysis 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 Tradeoff Analysis use?
Tradeoff Analysis 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 Tradeoff Analysis use?
About 1k tokens (SKILL.md is roughly 4.1k 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 Tradeoff Analysis?
Skills that share tags, products or a category with Tradeoff Analysis: Typeui Fundamentals (bergside/typeui, 2k stars), Design Standards (rampstackco/claude-skills, 945 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 Tradeoff Analysis?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 105 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.