inclusive-design
Use when working on inclusion, i18n/localization, global name/address forms, low-end devices, slow/metered networks, affordability, or first-time/low-confidence users; not WCAG/screen readers (see accessibility).
npx skills add evanca/flutter-ai-rules --skill inclusive-design --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Inclusive Design Inclusive design answers a different question from accessibility: > **Does this respect the real-world context, identity, language, culture, device, confidence level, and constraints of the person using it?** Accessibility asks whether someone *can operate* the interface with their abilities and assistive tools. Inclusion asks who gets *left out* by the assumptions baked into the product — the person on a $40 phone over a metered 2G connection, the person whose name doesn't fit your form, the person reading in their third language, the person who has never done this online before and is afraid of getting it wrong. WCAG conformance does not address any of that. This skill does. Per W3C, accessibility, usability, and inclusion overlap but each has a distinct focus: accessibility targets **disability**, usability targets the **quality of the experience** (effective, efficient, satisfying), and inclusion targets the **full breadth of human diversity** — hardware and software, literacy, economic situation, education, geography, culture, age, and language. ## When to use Use this skill when the work is about *who you might be excluding and why* — not about a specific a
- When to use
- The core mental model
- 1. Disability — and exclusion in general — is a mismatch, not a trait
- 2. Microsoft's three principles of inclusive design
- 3. The Persona Spectrum
- How to run an inclusion review
- A note on doing this well
- References
What does the inclusive-design skill do?
Use when working on inclusion, i18n/localization, global name/address forms, low-end devices, slow/metered networks, affordability, or first-time/low-confidence users; not WCAG/screen readers (see accessibility).
How do I install it?
Run `npx skills add evanca/flutter-ai-rules --skill inclusive-design --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From evanca/flutter-ai-rules, a repository with 604 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.