Read carefully when migrating AI context to
@Muse
You are helping me migrate context from one AI assistant to another. Your job is to compile, from our past conversations, a portable memory snapshot of what you reliably know about me. The output is going verbatim into a new AI's memory, so quality matters more than completeness.
OUTPUT RULES
- Output a single Markdown block using the section headers below. Omit any section you have nothing solid for — do not invent placeholders.
- Refer to me in the third person ("the user", "they") inside each bullet.
- One factual sentence per bullet. No transitions, no narrative.
- Mark anything you are uncertain about with "(inferred)" at the end of the bullet.
- Skip one-off statements unless they were clearly important.
- Skip sensitive information (health conditions, financial details, mental health) unless I explicitly asked you to remember it.
- Hard cap: 2000 words.
SECTIONS
## Identity
Name, pronouns, age range, current city / country, time zone, languages spoken.
## Profession & work
Role, company or self-employed, industry, team or function, key responsibilities. Tech stack and tools used daily if known.
## Communication preferences
Tone they want (casual / formal, blunt / warm). Preferred response length. Output format preferences (Markdown, plain text, code blocks). Things they have asked you to avoid.
## Recurring people
Partner, children, close family, friends, colleagues they mention regularly. First name + relationship + any salient detail.
## Health & dietary
Allergies, dietary restrictions, accessibility needs. Only include things they have stated themselves.
## Interests & hobbies
Topics they keep returning to. Sports, music, games, reading taste.
## Ongoing projects
Active personal or professional projects they have asked you to help with. State, goal, constraints.
## Working style & values
How they make decisions, what motivates them, what frustrates them. Things they have explicitly asked you to do or not do.
## Tools & environment
Devices, operating systems, apps, services, languages, frameworks they use regularly.
## Anything else durable
Anything important that does not fit above and is unlikely to change in the next year.