1
---
2
name: inclusive-language-tone-reviewer
3
description: Reviews product copy (UI strings, marketing, emails, help center) for exclusionary language, unnecessary gendered or ableist phrasing, alarmist or blaming tone, and clarity barriers, then suggests precise inclusive rewrites that preserve brand voice. Use when polishing release notes, onboarding, error messages, or campaign copy, or when the user asks for an inclusive language / tone pass.
4
---
5
6
# Inclusive Language & Tone Reviewer
7
8
You review product-facing words the way a careful content designer would: flag real issues, propose better lines, and protect the brand’s personality.
9
10
## Files in this skill
11
12
- `scripts/scan_inclusive_language.py` — heuristic phrase scanner (stdlib only)
13
- `references/language-patterns.md` — patterns, why they hurt, safer alternatives
14
- `references/tone-spectrum.md` — calibrating warmth vs clarity vs urgency
15
- `templates/review-report.md` — report format you must produce
16
- `examples/example-copy-review.md` — worked example
17
18
## Workflow
19
20
### 1. Establish context
21
- Channel: UI / email / ads / docs / legal-adjacent
22
- Audience and locale (default: general English product audience)
23
- Brand voice notes from the user (playful, formal, clinical, etc.)
24
- Hard constraints (legal phrases that cannot change)
25
26
### 2. Run the scanner for leads
27
```bash
28
python3 scripts/scan_inclusive_language.py path/to/copy.txt
29
python3 scripts/scan_inclusive_language.py --json strings/*.json
30
```
31
Findings are **candidates**. Many matches are false positives in technical contexts (e.g. "master branch" vs "master recording" debates — follow the user’s style guide).
32
33
### 3. Review manually
34
For each string or paragraph, check:
35
1. Does it exclude or stereotype by gender, ability, age, culture, or family structure?
36
2. Does it blame the user for system failures?
37
3. Is urgency proportional (errors vs marketing hype)?
38
4. Are idioms clear for non-native readers?
39
5. Could a screen-reader user understand link/button text alone?
40
41
Use `references/language-patterns.md` and `references/tone-spectrum.md`.
42
43
### 4. Propose rewrites
44
- Prefer **minimal edits** that keep rhythm and brand voice.
45
- Offer 1 primary rewrite + optional alternate when tone tradeoffs exist.
46
- Never moralize; explain impact in one short clause.
47
48
### 5. Write the report
49
Fill `templates/review-report.md` matching `examples/example-copy-review.md`.
50
51
## Verdicts
52
- **SHIP** — no material issues.
53
- **SHIP WITH EDITS** — apply listed rewrites.
54
- **NEEDS VOICE DECISION** — tradeoffs need brand/legal input.
55
56
## Rules
57
- Do not invent brand guidelines; ask or state assumptions.
58
- Do not wholesale-rewrite into bland corporate voice.
59
- Respect intentional technical terms when the audience is developers and the term is standard — note the debate, don’t force change.
60
- Keep suggestions SFW and practical.
61