Specification

me.txt is a UTF-8 encoded markdown file at your site's root that provides AI systems with structured context about who you are.

Format

A me.txt file has a simple structure:

An H1 with your name as the first element
An optional blockquote with a one-line summary of who you are
An optional markdown image for a profile photo: ![Name](url)
Freeform markdown content (optional intro/about paragraph)
H2 sections organizing information by category
Content within sections can be lists, paragraphs, or link lists

Location

The file should be served at one of these locations (in order of preference):

https://yourdomain.com/me.txt
https://yourdomain.com/.well-known/me.txt

Serve with Content-Type: text/plain; charset=utf-8 or text/markdown; charset=utf-8.

Sections

The following H2 sections are recognized by convention. You can use any sections that make sense for you, but these are recommended for interoperability:

Section	Status	Description
`## Now`	Recommended	Current projects, focus areas, what you're working on
`## Skills`	Recommended	Core competencies and expertise areas
`## Stack`	Optional	Technologies, tools, and languages you work with
`## Work`	Optional	Notable projects, employment, or ventures
`## Writing`	Optional	Blog posts, articles, publications
`## Talks`	Optional	Presentations, podcasts, videos
`## Links`	Recommended	GitHub, Twitter, website, email, etc.
`## Preferences`	Recommended	Communication style, timezone, availability
`## Optional`	Optional	Secondary info, hobbies, personal details

The Preferences Section

The ## Preferences section tells AI systems (and humans) how to interact with you:

Communication style: Async-first? Sync-preferred? Email? Slack?
Timezone: When are you available?
Response expectations: How quickly do you typically respond?
Meeting preferences: Video on? Audio only? Written preferred?
Collaboration style: Pairing? Solo work? Code review preferences?

Profile Photo

To include a profile picture, add a standard markdown image after the summary (before the first H2 section):

![Your Name](https://example.com/avatar.jpg)

Tools that parse me.txt will extract this as the avatar field. When using --github with the CLI, your GitHub profile picture is automatically included.

Link List Format

For sections like Links, Work, or Writing, use markdown link lists:

## Links

- [GitHub](https://github.com/username): Open source projects
- [Twitter](https://twitter.com/username): Tech thoughts and threads
- [Blog](https://example.com/blog): Long-form writing

The text after the colon is an optional description that helps AI understand the context of each link.

Size Guidelines

Target: Under 500 lines, under 2,000 tokens
Ideal: 100-200 lines, 300-800 tokens
For more detail, link to a me-full.txt for extended information

Example

me.txt

# Jamie Chen

> Full-stack engineer building developer tools

![Jamie Chen](https://jamiechen.dev/avatar.jpg)

## Now

- Building an open-source SDK generator
- Contributing to the OpenAPI spec working group
- Writing a CLI design guide

## Skills

- Developer experience
- API design
- CLI tooling

## Stack

- TypeScript, Go, Rust
- Node.js, Deno
- PostgreSQL, Redis

## Links

- [GitHub](https://github.com/jamiechen)
- [Twitter](https://twitter.com/jamiechen)
- [Website](https://jamiechen.dev)
- [Email](mailto:hi@jamiechen.dev)

## Preferences

- Communication: Async-first (GitHub issues, email)
- Timezone: US Pacific (UTC-8)
- Response time: Within 24-48 hours
- Meetings: Only when async won't work