← ClaudeAtlas

inclusive-designlisted

Reviews products, forms, and copy through an inclusive, equitable lens — surfacing who a design excludes and how to widen it — and rewrites language to be more inclusive ("copy that cares"). Use whenever the user wants a design or any writing made more inclusive, equitable, or welcoming; is designing names/identity/gender/pronoun fields or sign-up forms; worries about excluding, misrepresenting, or outing users; or wants copy reviewed for gendered, racialized, ableist, or otherwise non-inclusive language. Reach for it on identity, representation, and inclusive-language questions even when "inclusive design" isn't named. It reasons from patterns (catching "congressman" from the same rule as "fireman") and works in ANY language, not just English. NOT for disability/assistive-tech accessibility (screen readers, keyboard, contrast, WCAG) — that's the accessibility-review skill. Context-aware, centered on user safety, not blanket word-banning.
JoaoMonteiro100/ux-design-skills · ★ 0 · Web & Frontend · score 70
Install: claude install-skill JoaoMonteiro100/ux-design-skills
# Inclusive Design ("Designing from the Margins") This skill helps design *from the margins* — starting with the people a product would otherwise exclude — because a design that works at the edges works better for everyone at the center. It covers two connected jobs: **reviewing a design for who it excludes and how to widen it**, and **reviewing or rewriting copy** to be more inclusive. Use either or both. The single most important thing this skill does is bring **judgment, not rules.** Inclusive design done badly becomes performative box-ticking or heavy-handed word-policing that annoys everyone and helps no one. Done well, it's about questioning defaults, reducing avoidable harm, and giving people room to describe themselves — always explaining the *why*, and always weighing the user's safety and self-determination over a tidy checklist. Hold that bar. ## The core stance Carry these ideas into any review; they're the lens: - **"Neutral" isn't neutral.** Every default is a decision about who's normal and who has to adapt. A "name" field, a date format, a gender binary, an assumed family structure — each quietly centers some people and marginalizes others. Surfacing that hidden decision is the first move. - **The "average user" is a fiction.** Averaging away real diversity produces a person who doesn't exist and designs that fit no one at the edges. People are **overlaps, not boxes** — intersecting identities, not clean categories. - **"Edge cases" usually aren