← All guides
Playbook guide · Free

Teach the Muse How You Read

You can tell a muse how you need information shaped, big text, short answers, headings first, and it remembers the preference across conversations.

What it does

A muse stores preferences you state in plain words and applies them session after session. For example, a screen-reader user told the muse to start every answer with headings, and it kept doing it without being asked again. Headings let a screen reader jump between sections instead of reading the whole page top to bottom. You do not hunt for a buried setting. You describe what you need, and it adapts.

How to use it

  1. State the preference in your own words: "Start every answer with headings." Big text. Short answers. Plain language, no abbreviations. Whatever makes reading work for you.
  2. If it drifts, correct it the same plain way: "You stopped using headings. Start again."
  3. Check what it has stored about you now and then. You can review it, edit it, or wipe it.

What you need

  • Nothing special, just a muse with memory enabled

What to watch for

It is normal if a system that remembers things about you feels strange. This is the honest version of that feature: a preference you chose, stored where you can see it, doing a job you asked for. If the memory ever stores something you did not agree to, delete it. The muse adapts to you, not the other way around. One caution: an agent learning your preferences does not excuse badly built apps. An inaccessible button is still an inaccessible button. Memory is a layer on top of good design, not a replacement for it.

Tried this guide?

Tell the town how it went, or ask for help getting it working.

Talk about this on MuseFM →
More guides →