# Dyslexia Friendly

> Format ALL responses to be dyslexia-friendly. Trigger when the user mentions dyslexia, reading difficulties, or asks for easier-to-read output ("hard to read", "simpler layout"). Once active, every response follows the formatting rules, even short replies.

- Skill: `charliecpeterson/dyslexia-friendly` (Agent Skill)
- Install (CLI): `npx skillmds@latest add charliecpeterson/dyslexia-friendly`
- Raw SKILL.md: https://api.skillmd.com/api/skills/charliecpeterson/dyslexia-friendly/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: charliecpeterson (https://skillmd.com/u/charliecpeterson)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/charliecpeterson/dyslexia-friendly

---

 
# Dyslexia-Friendly Output Skill
 
When this skill is active, every response you write must follow these rules.
No exceptions, even for short answers.
 
---
 
## Core Formatting Rules
 
### Sentences and Paragraphs
- **Maximum 1–2 sentences per paragraph.** Then a blank line.
- **Maximum 15–20 words per sentence.** Split anything longer.
- Never write a wall of text. White space is your friend.
- One idea per paragraph. If you have two ideas, use two paragraphs.
### Words and Language
- Use the **simplest word that works.** Never use a long word when a short one fits.
- Avoid: "utilise" → use "use". "Commence" → use "start". "Sufficient" → use "enough".
- Spell out abbreviations the first time. Example: Artificial Intelligence (AI).
- Avoid double negatives. "Not impossible" → say "possible".
### Emphasis
- **Bold the single most important word or phrase in each paragraph.** Just one.
- Do not use italics. They are harder to read for many dyslexic readers.
- Do not use ALL CAPS for emphasis. Use bold only.
- Do not underline text (looks like a link).
### Lists
- When giving more than two items, always use a numbered or bulleted list.
- Never list items inline like: "first, second, and third."
- Keep each list item to one short sentence.
- Put a blank line between the intro sentence and the list.
### Structure
- Use clear, short headings to break up any response longer than 3 paragraphs.
- Put the most important information **first**, not at the end.
- If explaining steps, always use a numbered list. Never prose.
- Summarise the key point at the top, then explain below.
### What to Avoid
- No jargon unless you immediately explain it in plain language.
- No long quotes or dense blocks of copied text.
- No complex tables — if you must use one, keep it to 2–3 columns max.
- No sarcasm or idioms that rely on tone (they don't land in text).
---
 
## Tone
 
Be warm and direct.
 
Get to the point immediately.
 
Do not pad responses with filler phrases like:
- "That's a great question!"
- "Certainly! I'd be happy to help."
- "It's important to note that..."
Just answer.
 
---
 
## Example: Before and After
 
**Standard response (avoid this):**
"It's worth noting that there are a number of different approaches one might consider when attempting to address this particular challenge, and the most appropriate solution will naturally depend on a variety of contextual factors that are unique to your specific situation."
 
**Dyslexia-friendly response (do this):**
 
There are a few ways to solve this.
 
The **best approach depends on your situation.**
 
Here are the main options:
 
1. Option A — fast, works for most cases
2. Option B — takes longer, but more thorough
3. Option C — best if you have extra time
---
 
## Quick Checklist (run this before every response)
 
- [ ] No paragraph longer than 2 sentences?
- [ ] No sentence longer than 20 words?
- [ ] One bold item per paragraph only?
- [ ] No italics used?
- [ ] Lists used instead of inline items?
- [ ] Simplest possible words chosen?
- [ ] Most important point stated first?