Research & analysis
“Pros and cons of four-day work weeks.” Each finding becomes a card you can filter, instead of reading linearly.
Sources and confidence stay on every card, so trust doesn't cost extra scrolling.

PACE (Personalized Adaptive Cognitive Experience) turns long AI answers into something you can scan, follow or listen to, without losing the substance.
The insight is in there, buried in one long block. Most people skim it, abandon it, or re-prompt: “shorter,” “use bullets,” “explain simply.”
How might we keep the depth of AI answers, but make the point findable in seconds?
Between meetings. Needs the point first, detail on demand.
Walking, commuting, cooking. Needs to hear it, not read it.
Tired, neurodivergent, or reading in a second language. Needs one idea at a time.
Design ruleNever cut the substance, only change how it arrives. The full answer is always one tap away.
Same question, same model, two answers. No regenerating, nothing lost.


A summary, a research brief, a plan and a brainstorm are different shapes of thinking. So each gets its own layout instead of one chat bubble.
“Pros and cons of four-day work weeks.” Each finding becomes a card you can filter, instead of reading linearly.
Sources and confidence stay on every card, so trust doesn't cost extra scrolling.

A six-step plan, one step at a time, with a progress bar and a checklist.
The mini-map answers “where am I?”, the structure Graphologue's users asked for.

Eight campaign ideas as tagged cards on a grid: bold, safe, weird.
Continue with FigJam turns the cards into sticky notes, so ideas leave the chat ready to sort.

We can already choose how hard an AI thinks. Why not how it speaks? Reading Preferences reuse the effort-level pattern people already know, pointed at the output.



From concept to a working Claude plugin. PACE runs as an MCP server with an MCP Apps UI: the assistant writes the answer, PACE renders it in Standard or Cognitive mode. The same open standard lets it follow to ChatGPT.
Cognitive Mode in any chat interface.
Your depth, your format, your voice settings.
Shorter when you're skimming, audio when you're moving, visual when you're comparing.
People scan. NN/g found users read about 20% of the words on an average page, and only half of pages with 111 words or fewer.
Models over-answer. YapBench traces it to preference-based training that favors longer outputs, and links lower cognitive load to stronger intent to keep using a chatbot.
Users ask for structure. In the Graphologue study, people found long, unstructured answers hard to navigate and wanted to see how ideas connect.
I'm building it now, and I'd love your feedback or to show you a live demo.