voice.md: A Writing Style Template File for AI

AI writing has a memory problem.

You can spend twenty minutes telling a model how you write, get one decent answer, and then start over the next time you open a new chat, switch tools, or move from email to a document.

That should not be normal. Your writing style should be portable. It should live in a small, readable file you own. It should work across ChatGPT, Claude, Gemini, Cursor, agents, email tools, document tools, and whatever comes next.

Voiceport calls that file voice.md.

The Claim

voice.md should become the standard file name for personal AI writing style.

Just as software projects have a README.md, serious AI-assisted writing should have a voice.md: a durable style file that can travel across tools, chats, agents, editors, and workflows.

The point is not to create another prompt hack. The point is to give your writing voice a home.

What Is voice.md?

voice.md is a writing style template file for AI. It is plain Markdown, written for both humans and language models.

It is a plain Markdown file that describes how you sound, how you explain things, what you avoid, what kinds of examples you use, and how AI should adapt your voice across common writing situations.

It is not a brand book. It is not a prompt trick. It is not a permanent subscription to one AI platform. It is a portable instruction file you can keep, edit, copy, paste, version, and hand to an agent.

A Minimal voice.md

The simplest version looks like this:

# voice.md

## Voice Summary
Write in my voice: direct, specific, warm without being soft, and skeptical of vague claims.

## Rules
- Use concrete nouns and active verbs.
- Keep paragraphs short.
- Avoid corporate filler.
- Preserve my point of view instead of smoothing it into generic advice.

## Modes
- Email: clear, friendly, and practical.
- Essay: more opinionated, with a sharper thesis.
- Reply: concise, useful, and human.

That file can become much richer, but the point is simple: AI should not have to guess who you are every time.

Why a File?

A file is boring in the best way.

Files are portable. Files can be backed up. Files can be shared with a trusted assistant, committed to a private repo, dropped into a project, attached to a chat, or stored in a notes app. A Markdown file is readable by humans and easy for AI systems to consume.

That matters because your voice should not be trapped inside one vendor’s memory feature. Platform memory is useful, but it is not enough. You still need an artifact you control.

If an AI tool asks, “How should I write this?”, the answer should not be another improvised paragraph of prompt instructions. The answer should be: use my voice.md.

Why Not Just Prompt Better?

Better prompting helps, but prompting is a bad place to store identity.

Prompts are usually temporary. They get copied badly, edited accidentally, forgotten in old chats, and flattened into generic language. Most people do not want to maintain a library of voice prompts for every situation.

voice.md gives the prompt somewhere to point.

Instead of writing “make this sound like me” and hoping the model understands, you can say:

Use the attached voice.md as the writing style guide. Preserve the argument, but rewrite the draft in my voice.

The prompt stays short because the style intelligence lives in the file.

What Belongs in voice.md?

A useful voice.md should include more than adjectives. Most weak style guides say things like “clear, concise, friendly, professional.” That is not enough. Almost everyone wants those things.

A stronger voice.md includes evidence-backed instructions:

1. A short voice summary.
2. Specific do and do not rules.
3. Examples of phrasing that sounds like you.
4. Words, rhythms, and sentence shapes you tend to use.
5. Things AI tools should avoid when writing for you.
6. Different modes for email, essays, social posts, replies, sales copy, or internal docs.
7. A paste-ready starter prompt for new AI chats.

The file should tell an AI what to preserve, not just what to imitate.

What Does Not Belong in voice.md?

Do not turn voice.md into a diary, a raw data dump, or a folder full of private source material.

Keep the durable style rules. Keep selected examples if they are safe. Remove secrets, names, private client details, medical information, payment information, and anything you would not want reused in generated text.

The artifact should be useful enough for AI and safe enough to carry around.

Where Does voice.md Come From?

You can write one manually. Start with your best emails, notes, posts, essays, memos, texts, and transcripts. Look for patterns. Write down what repeats. Add examples. Remove anything private.

That works, but it is hard to do objectively because your own style is familiar to you. You may not notice the phrases, structures, and instincts that make your writing recognizable.

Voiceport builds voice.md from real signal: writing samples, source material, dictated language, and an optional voice conversation about how you naturally explain, react, and phrase things. The goal is not to clone you. The goal is to give AI tools enough instruction to stop sanding your voice down into default internet prose.

How to Use voice.md

Use it anywhere AI writes with you or for you.

1. Keep voice.md somewhere you control.
2. Attach it, paste it, or reference it before a writing task.
3. Ask the AI to preserve your argument and apply the style rules.
4. Update the file when your voice changes or when AI gets something wrong.

That last point matters. voice.md should not be frozen forever. It should get better as you notice what AI still misses.

The Standard We Want

We want voice.md to become the obvious file name for personal AI writing style.

Put it in your notes. Attach it to a chat. Give it to an agent. Keep it beside the drafts that matter. Update it when your style changes. Use it when you want AI to help without making you sound like someone who has never had a real opinion.

This does not need to be complicated. It needs to be portable, readable, and yours.

Get Your voice.md

Voiceport creates a Voice Profile from your real writing and turns it into a portable voice.md file. You can use it with the AI tools you already have.

Get your Voice Profile

Quick Answers

What is voice.md?

voice.md is a Markdown writing style template file for AI tools. It describes your writing voice, rules, examples, and preferred modes so AI can write closer to your natural style.

Is voice.md tied to Voiceport?

No. Voiceport creates a voice.md file, but the format is plain Markdown. You can keep it, edit it, and use it across AI tools.

Why use Markdown?

Markdown is readable by humans, easy to edit, and easy for AI systems to process. That makes it a good format for a portable writing style file.

Where should I keep voice.md?

Keep voice.md wherever you already keep durable working context: a notes app, private repo, project folder, or AI workspace. The point is that it belongs to you, not one platform.