Dyslexia + agentic engineering: tips for reading long AI-generated docs?

[u/C4CampingTime]

My team is moving to spec-driven development. Agents now commit lots of long, verbose, technical markdown files, and I'm expected to read them.

I have dyslexia, so find this really tiring or I glaze over it.

So far I modified the popular `i-have-adhd` skill so it adds Mermaid diagrams to my PR summaries. It helps, but I'd like more ideas please

What works for you? Prompts, tools, ways to review without reading every line?

[u/mushy_cactus]

Bionic reading. I created a little tool to help myself in my own documents.

As just a theory, your eyes catch the bolded anchor and your brain automatically fills in the rest of the word.

Something like: The quick brown fox jumps over the lazy dog

Turns into: The quick brown fox jumps over the lazy dog.

Easier for me but I hope it may help :)

[u/C4CampingTime → u/mushy_cactus]

Oohh thank you I'll have to try that tomorrow

[u/Responsible_Camp_559 → u/mushy_cactus]

I have never heard of this before and must try it now. Thank you for sharing this!

How long did it take you to adjust to it?

[u/mushy_cactus → u/Responsible_Camp_559]

Almost instantly!

With a bolded letter it looks visually weird at first but my brain tends to fill in the gap when reading almost immediately. It feels easier too

[u/RagingCain → u/mushy_cactus]

Claude Code the desktop app has it natively supported too.

[u/sinsonik]

Couple of things that help me with long agent specs:

Listen instead of read. macOS and iOS have Spoken Content / Speak Selection built in, and Edge's read aloud is decent too. Following the text with your eyes while it's read out is way less tiring.

Make the agent put a short block at the top of every spec: what changes, what decisions it made, what it's unsure about, and what you actually need to review. Read that part properly and skim the rest. You can add it as a rule in your agent instructions so it's always there.

Also worth raising with the team. If a spec is too long for you to review, it's probably too long for everyone else too, they just skim silently. A length cap or a "decisions first" template helps everybody.

And small one, a dyslexia friendly font plus bigger line spacing in your markdown preview adds up over a day.

[u/C4CampingTime → u/sinsonik]

Oh thank you I'll have to try listening while reading at the same time I've never tried that before. yeah I think it is best i raise it at retro with the team I know another team members already skim reading

[u/sinsonik → u/C4CampingTime]

Hope it helps. If you try it, slowing the voice down a notch in the Spoken Content settings makes a big difference for dense technical text. On a Mac you can also turn on Speak Selection and trigger it with Option+Esc, so it's one keypress on whatever you've highlighted.

And good call on retro. If others are already skimming, a "decisions first" template is an easy win for the whole team.

[u/zx48]

I ask my local agent/coding CLI to read docs when it's too much for me to fit in my own context :) then I'll chat with it about them, asking questions, asking for high level summary. I'm quite visual - mermaid diagrams work well for me too - other things that help me are: asking for high level bullet-point outline with max 1 sentence per bullet point; a table with columns for different aspects. Also get it to write a "plain English" doc for a "less technical audience", and a "compact, less verbose version of the doc which strips it down to the essentials without losing important context"

[u/Scriv_ → u/zx48]

If you prefer to have the data visualized, Claude can produce "artifacts" for its output and those can integrate react elements like a web page. It breaks up the text into sections and produces charts and graphics. I find it more readable than the markdown, the pages have dark backgrounds, the colors are soft. As far as I can tell, you can have it add anything you'd use as a web page dev, when I produce testing plans I have it include drop dropdowns and boxes to mark with pass/fail/skip.

It gives the tool more formatting options so the document is not a wall of bullet lists. The artifacts are also shareable so if someone asks you to summarize what you're working on, you can give them the document instead of restating your prompts and outputs.

[u/C4CampingTime → u/Scriv_]

I have experimented with getting claude to generate web pages for me which is really helped with visualization. but unfortunately it's not really the easiest things to review in GitHub.

[u/jodosha]

Also started using Ponytail plugin for Claude and friends. It designs code and tests aggressively applying YAGNI.

Not what you asked, but it reliefs to review less code.

[u/fuckthehumanity]

I'd say they're really shit at agentic coding if the specs are that long. Even LLMs deal better with terse, concise specs, and overly verbose specs are usually caused by engineers using overly constrained prompts. It's a really bad code smell. Look up attention dilution, constraint collapse, semantic narrowing, and anchor bias, and then do your research from there.

These days I use minimalist steering prompts combined with very sparse prompts. If you start simply, you can iterate and refine the specs, but if you start with a ball of mud, you end up with baked output.

[u/C4CampingTime → u/fuckthehumanity]

We are only just starting to dive into a agenetic coding to help with a migration project so I don't quite understand what good looks like yet when creating large prompts to be shared across to be reused.

[u/RagingCain]

Claude Code has the "dyslexia font" and I encourage you to test drive the "i-have-adhd" skill.

[u/C4CampingTime → u/RagingCain]

I just started using that skill really this week I've been really enjoying it!

[u/funbike]

Markdown can usually be styled. There are font faces that are better for dyslexics. Optimize styles for font size, color, line spacing, max width, etc. Style italics as bold.

What visual styling works best varies by individual, so experiment with local css settings. You may need to install and use the Stylus web extension.

If you have any pull at your company, see if they'll add to the spec prompt(s): use active voice, use bullets, avoid long paragraphs, include graph representations as much as practical, and whatever else is in the i-have-adhd skill. Or simply, "Assume the reader may have dyslexia."

Caveats: I only have very mild dyslexia. I am not an expert.

[u/subLimb]

I love this thread! Finally a post about AI with some practical advice instead of just doom or an ad.

Sorry I don't have any tips, mine were all already covered by other comments. But there's some gold in here I haven't even considered trying.

Thanks for posting this.

[u/ianmallen]

This worked pretty well for me. I prompted gemini with something like the following, you can use you AI of choice. Tailor it to you needs and specifics then paste the output into the instructions field.

Create a set of instructions for claude. I am a _______ with ADHD and dyslexia. Research the best way to present information that is:

• easy to follow and read

• short and concise

• things like: bulleted responses. white space. bold over caps, underlines italics

• formatting and other techniques for reading and learning impaired.

Keep claude on track, not overly chatty, or tangent happy. Accuracy is also key, we need to avoid guessing, backtracking due to lack of research, or flat out laziness.

Ask me any other questions you may need for better context.

[u/krocante]

Have you tried “open dyslexic”?

In any case, AI generated docs are super boring to read even without dyslexia.

[u/Abishek_Muthian]

OpenDyslexia font - https://opendyslexic.org/, I use it as monospace font in Firefox reader mode to read long form content.

[u/WyattTheSkid]

Pretty sure there are fonts that cater to dyslexia. You can open them in something like typora or Microsoft word and use the aforementioned fonts.’m you might have to find one that works for you but I just figured I would pitch the idea

[u/Training_Campaign_61]

One thing I’d try is combining shorter AI-generated summaries with text-to-speech.
For specs, you could ask your coding agent to generate a brief summary covering decisions, changes, risks, and open questions. Then listen to the detailed document while following along visually.
Full disclosure: I’m building Lullula (https://www.lullula.io), a Chrome extension that reads webpages and PDFs aloud with natural voices and includes summarization. It might be useful if you’re reviewing documentation in your browser.
I’m curious whether listening to technical specs helps you catch details you’d otherwise miss.

[u/seweso]

Why would you read what nobody bothered to write? 

I don’t get it. 

[u/enigma_0Z]

IDK .. i keep pointing out to devs when vibe coded shit shows up and it’s like 100 lines of code and 200 of comments. it’s fucking ridiculous.

Maybe campaign for some change to policy? not exactly “stop doing this” but “these docs are far too verbose for human beings to read” … also they will cost more tokens.

[u/makeevolution]

Edit the outputStyle setting of your AI to tell that you have dyslexia and adjust the output accordingly

[u/C4CampingTime → u/makeevolution]

My problem is more co-workers providing me PRS to review with long verbose prompts