Material Design 3 UI/UX Guide
skydashnet/material-design-3-ui-skill
Guides designing, reviewing or implementing interfaces that follow Google's Material Design 3 system: semantic tokens, component states, adaptive layout and accessibility.
Design interfaces that detect and respond to system-level user preferences.
Install User Preference Respect
$ npx skills add Owl-Listener/inclusive-design-skills --skill user-preference-respect -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills user-preference-respect --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/adaptive-interfaces/skills/user-preference-respect .claude/skills/user-preference-respect && 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 "user-preference-respect" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/adaptive-interfaces/skills/user-preference-respect into .claude/skills/user-preference-respect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-preference-respect", 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/adaptive-interfaces/skills/user-preference-respectType 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 user-preference-respect -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills user-preference-respect --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/adaptive-interfaces/skills/user-preference-respect .agents/skills/user-preference-respect && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "user-preference-respect" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/adaptive-interfaces/skills/user-preference-respect into .agents/skills/user-preference-respect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-preference-respect", 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 user-preference-respect -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills user-preference-respect --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/adaptive-interfaces/skills/user-preference-respect .cursor/skills/user-preference-respect && 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 "user-preference-respect" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/adaptive-interfaces/skills/user-preference-respect into .cursor/skills/user-preference-respect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-preference-respect", 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 adaptive-interfaces/skills/user-preference-respect--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 user-preference-respect -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills user-preference-respect --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/adaptive-interfaces/skills/user-preference-respect .gemini/skills/user-preference-respect && 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 "user-preference-respect" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/adaptive-interfaces/skills/user-preference-respect into .gemini/skills/user-preference-respect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-preference-respect", 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 user-preference-respectInstalls 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 user-preference-respect -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/adaptive-interfaces/skills/user-preference-respect .github/skills/user-preference-respect && 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 "user-preference-respect" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/adaptive-interfaces/skills/user-preference-respect into .github/skills/user-preference-respect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-preference-respect", 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 user-preference-respect -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 user-preference-respect --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/adaptive-interfaces/skills/user-preference-respect .opencode/skills/user-preference-respect && 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 "user-preference-respect" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/adaptive-interfaces/skills/user-preference-respect into .opencode/skills/user-preference-respect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-preference-respect", 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
user-preference-respect- GitHub stars
- 103
- Token cost
- ~1k tokens
- SKILL.md length
- 464 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design interfaces that detect and respond to system-level user preferences.
- Implementing dark mode
- SKILL.md covers The Preferences, Implementation Principles and Assessment Checklist
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Any user preference that affects how the interface renders
What it does
User Preference Respect is an agent skill from Owl-Listener/inclusive-design-skills. Design interfaces that detect and respond to system-level user preferences. Use when implementing dark mode, reduced motion, high contrast, text scaling, or any user preference that affects how the interface renders. Triggers on: user preference, system preference, prefers-reduced-motion, prefers-contrast, prefers-color-scheme, forced-colors, media query, user settings, system settings, accessibility settings, OS settings.
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 Theming and dark mode, Responsive design and Accessibility. 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
- Implementing dark mode
- Any user preference that affects how the interface renders
- : user preference
- System preference
Example prompts
- “/user-preference-respect”
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
User Preference Respect loads about 1k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 464 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). 464 words, ~1,020 tokens.
Download SKILL.mdSave it as
.claude/skills/user-preference-respect/SKILL.md (or your agent's skills folder).- name
- user-preference-respect
- description
- Design interfaces that detect and respond to system-level user preferences. Use when implementing dark mode, reduced motion, high contrast, text scaling, or any user preference that affects how the interface renders. Triggers on: user preference, system preference, prefers-reduced-motion, prefers-contrast, prefers-color-scheme, forced-colors, media query, user settings, system settings, accessibility settings, OS settings.
User Preference Respect
The operating system already knows what the user needs. Your job is to listen and respond. These preferences exist because people set them deliberately — ignoring them overrides the user's own accessibility decision.
The Preferences
prefers-reduced-motion
What it means: user experiences discomfort or harm from motion. What to do:
- Disable all decorative animation
- Replace slide/fade transitions with instant state changes
- Keep essential motion (loading spinners) but simplify
- Disable parallax, scroll-triggered animation, and auto-advance
- Never override this preference
How to detect: @media (prefers-reduced-motion: reduce)
prefers-contrast
What it means: user needs stronger visual distinction. What to do:
- Increase contrast beyond WCAG minimums
- Replace subtle shadows and gradients with solid borders
- Make focus indicators bolder and more visible
- Remove transparency and blur effects
- Increase border widths on interactive elements
How to detect: @media (prefers-contrast: more)
prefers-color-scheme
What it means: user prefers light or dark interface. What to do:
- Provide genuine dark mode (not just inverted colours)
- Ensure all content is legible in both modes
- Test images, charts, icons, and illustrations in both
- Don't use pure black (#000) on dark mode — use dark grey (#1a1a1a) for less eye strain
- Remember: dark mode is not just aesthetic — it reduces eye fatigue and helps some people with light sensitivity
How to detect: @media (prefers-color-scheme: dark)
forced-colors
What it means: user has enabled Windows High Contrast or similar. What to do:
- Don't fight the system colour override
- Ensure borders and outlines define interactive elements (the system will strip your colours)
- Use transparent borders that become visible in forced-colors mode
- Test that all interactive elements remain distinguishable
- Don't rely on background colour alone to indicate state
How to detect: @media (forced-colors: active)
Show full SKILL.md (188 more words)Show less
prefers-reduced-transparency
What it means: user finds transparent elements hard to read. What to do:
- Replace semi-transparent backgrounds with solid ones
- Remove frosted glass / backdrop blur effects
- Ensure overlays are fully opaque
How to detect: @media (prefers-reduced-transparency: reduce)
Implementation Principles
Progressive Enhancement
- Build the accessible version first
- Add motion, transparency, and visual flourishes as enhancements
- When a preference is detected, you're removing the enhancement, not degrading the experience
Don't Ask — Detect
- Don't make users configure accessibility settings in your app when the OS already has the setting
- Detect and respond automatically
- If you offer additional settings, they should layer on top of system preferences, not replace them
Test Every Preference
- Test with each preference enabled individually
- Test with combinations (reduced motion + high contrast + dark mode)
- Verify that the interface is complete and usable in every state
- Automated tests can check that media queries exist — manual testing verifies they work
Assessment Checklist
- prefers-reduced-motion is detected and all decorative motion stops
- prefers-contrast is detected and visual contrast increases
- prefers-color-scheme is detected and theme switches
- forced-colors mode doesn't break interactive elements
- Combinations of preferences work together
- No preference is overridden or ignored
© 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 adaptive-interfaces/skills/user-preference-respect of Owl-Listener/inclusive-design-skills.
Open the folder on GitHubat commit 6e0740f
Compare with similar skills
User Preference Respect 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 |
|---|---|---|---|---|---|---|
| User Preference Respect this skillOwl-Listener/inclusive-design-skills | 103 | — | ~1k | Automated safety check: Pass | MIT | |
| Material Design 3 UI/UX Guideskydashnet/material-design-3-ui-skill | 130 | — | ~3k | Automated safety check: Pass | MIT | |
| UI Design Systemtry-works/role-model | 118 | — | ~5k | Automated safety check: Pass | MIT | |
| Auditgrowupanand/ConvoForm | 101 | 6 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Dotnet UInovotnyllc/dotnet-artisan | 233 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Bmad UXaj-geddes/claude-code-bmad-skills | 487 | — | ~2k | Automated safety check: Notes | Custom licence |
Similar skills
UI Design System
try-works/role-model
React UI component systems with TailwindCSS + Radix + shadcn/ui.
Audit
growupanand/ConvoForm
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns.
Dotnet UI
novotnyllc/dotnet-artisan
Builds .NET UI apps across Blazor (Server, WASM, Hybrid, Auto), MAUI (XAML, MVVM, Shell, Native AOT), Uno Platform (MVUX, Extensions, Toolkit), WPF (.NET 8+, Fluent theme), WinUI 3 (Windows App SDK…
Bmad UX
aj-geddes/claude-code-bmad-skills
Solutioning-phase UX planning skill (optional; activate when the project has a UI).
I Audit
boussadjra/vuestrata
Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design.
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 User Preference Respect
What does User Preference Respect do?
Design interfaces that detect and respond to system-level user preferences. User Preference Respect is an agent skill from Owl-Listener/inclusive-design-skills. Design interfaces that detect and respond to system-level user preferences.
When should I use User Preference Respect?
User Preference Respect fits situations like: implementing dark mode; any user preference that affects how the interface renders; : user preference; system preference.
How do I install User Preference Respect in Claude Code?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill user-preference-respect -a claude-code`. Or copy the skill folder (adaptive-interfaces/skills/user-preference-respect in Owl-Listener/inclusive-design-skills) into .claude/skills/user-preference-respect in your project. Claude Code loads it when a task matches its description.
How do I install User Preference Respect in Codex?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill user-preference-respect -a codex`. Or copy the skill folder (adaptive-interfaces/skills/user-preference-respect in Owl-Listener/inclusive-design-skills) into .agents/skills/user-preference-respect in your project. Codex loads it when a task matches its description.
Can I use User Preference Respect 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 user-preference-respect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/user-preference-respect, .gemini/skills/user-preference-respect, .github/skills/user-preference-respect and .opencode/skills/user-preference-respect in your project.
What does User Preference Respect need to run?
SKILL.md names no scripts, command-line tools or credentials: User Preference Respect is instructions for the agent only.
Does User Preference Respect 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 User Preference Respect 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 User Preference Respect use?
User Preference Respect 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 User Preference Respect 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 User Preference Respect?
Skills that share tags, products or a category with User Preference Respect: Material Design 3 UI/UX Guide (skydashnet/material-design-3-ui-skill, 130 stars), UI Design System (try-works/role-model, 118 stars), Audit (growupanand/ConvoForm, 101 stars) and Dotnet UI (novotnyllc/dotnet-artisan, 233 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains User Preference Respect?
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.