Write Your Operating Manual Once, Let Every AI Read It

Write down how an AI should work with you one time, in a file you keep, and never explain yourself to a chat again. That is the whole idea. Everything below is how to do it so it actually holds.

You may have seen the trend: a "user operating manual," a "how to work with me" note, a "digital passport." Good instinct. People can feel that AI keeps treating them like a stranger, and they want to fix it. The instinct is right. The usual format is weak.

A paragraph pasted into one conversation is not a manual. It is a sticky note that vanishes when the window closes. The upgrade is to make it structured, reusable, and yours.

Why the Paragraph Version Falls Short

The popular template is a few sentences: "I prefer direct feedback, I work best in the morning, I'm a visual thinker." It feels organized to write. It does almost nothing once an AI reads it.

Three reasons. It only describes a style, never the substance — no projects, no history, no real limits. It lives in a single chat, so the next conversation never sees it. And it has no structure, so even when an AI does read it, it can't tell which line matters for the task at hand. A manual is not a mood. It is information, arranged.

The Four Sections That Carry the Weight

The Advice That Quietly Wastes Your Time

A lot of guides tell you to make the manual short and punchy — one screen, a few bullet points, easy to skim. That advice optimizes for the wrong reader. You're not writing a profile for a human to glance at over coffee. You're writing context for software that can read a thousand words without blinking.

Brevity here costs you. The detail you trim is exactly the detail that would have made the answer specific. Write the full thing. An AI does not get bored, and it does not skim. The reader you're actually serving rewards completeness, not concision.

A manual short enough to impress a human is usually too thin to help a machine.

Make It Reusable, Not Disposable

The difference between a sticky note and a manual is where it lives. Keep yours as plain text or markdown — a file, not a message. Then it travels. ChatGPT can read it. Claude can read it. Gemini can read it. Whatever you switch to next can read it, because text is the one format every tool agrees on.

This is what "own it" means in practice. The manual isn't a setting buried in one platform's account. It's a document you hold. When a better AI shows up next year, you don't re-teach a new assistant from zero — you hand it the same file and keep going.

Writing It Without Starting From Blank

The honest obstacle is the blank page. Four sections of structured truth about yourself is real work to draft cold. The shortcut is to start from writing you already have. Your essays and notes hold your principles. Your project docs hold your history and your workflow. The manual is mostly hiding in things you've already written; assembling it is less invention than excavation.

Soul Alchemy does that excavation. You paste your existing writing and it produces a structured set of identity files — your canon, your work, your operations, your red lines, and more — as drafts you then correct. Instead of facing four empty headings, you're editing a manual that already sounds like you. The result is plain markdown you keep and reuse, readable by any AI you open next.

Start Today, Not Perfectly

Don't try to write the complete manual in one sitting. Draft the principles and the red lines first — what you believe, and what an AI must never do. Those two sections carry most of the value on their own. Add the rest as you go. A rough manual handed to an AI today beats a flawless one that never leaves your head.

Frequently Asked Questions

What is an AI operating manual for yourself?

It is a document that tells an AI how to work with you — your context, your standards, your hard limits — so you don't have to re-explain yourself every conversation. It is the same idea as the "how to work with me" notes teams write, but built to be read by software and reused across every tool you use.

How is this different from a digital passport or user manual?

A digital passport or user manual is usually one paragraph pasted into a single chat. It tells an AI a vibe and then disappears. An operating manual built for reuse is structured into clear sections, lives in files you keep, and travels to any AI you open next. The instinct is the same; the format is the upgrade.

What should go in it?

Four sections cover most of the value: what you believe and decide by, what you've already built, how you actually work, and what an AI must never do. Beliefs and rules change the answers most. History and workflow make those answers fit your real life instead of a generic one.

Do I have to maintain it forever?

Light upkeep beats constant rewriting. Update it when something real changes — a finished project, a new rule, a shift in direction. Most of it stays stable for months. A manual you revise four times a year is far more useful than a perfect one you write once and never touch again.

Can the same manual work across different AI tools?

Yes, if you keep it as plain text or markdown. ChatGPT, Claude, and Gemini can all read a file you paste or upload. Because the manual lives with you rather than inside one platform, switching tools means handing over the same file, not teaching a new assistant from scratch.