ME.md Specification v1.0

Overview

ME.md is a structured markdown file that lives at a public URL. It describes a human to an AI in a machine-parseable, human-writable format. The tagline is robots.txt for human consciousness.

The problem it solves: every time you start a new AI session, you re-explain yourself. ME.md eliminates that. One file. One URL. Any AI that fetches it knows you — your values, your stack, your fleet, your constraints.

File Format

ME.md uses standard markdown with YAML frontmatter (the --- block at the top). The frontmatter contains structured metadata. The body contains human-readable sections with standard headings.

---
version: "1.0"
handle: "@yourhandle"
---

# 🫀 The Soul

I am a builder. I ship things. I care about craft.

Frontmatter Fields

All fields in the YAML frontmatter block. Two are required; the rest are optional but recommended.

- id: magerbot
  model: claude-sonnet-4-6
  role: "Principal Engineer"
  emoji: "⚡"
  channel: telegram

AgentConfig Object

Each item in the agents array is an AgentConfig object. Only id is required.

agents:
  - id: magerbot
    model: claude-sonnet-4-6
    role: "Principal Engineer"
    emoji: "⚡"
    channel: telegram
  - id: genny
    model: claude-sonnet-4-6
    role: "Life Architect"
    emoji: "🌿"
    channel: telegram

Standard Sections

The body of a ME.md file uses markdown headings to define sections. The spec defines seven canonical sections. You can add custom sections freely — parsers preserve any heading-based section.

Section headers may include a leading emoji — the parser extracts it as an icon. Section IDs are derived by slugifying the title text (emoji stripped).

Raw Endpoint

Every ME.md hosted on Loooom has a raw endpoint that returns the plain markdown source with Content-Type: text/plain and CORS headers set to Access-Control-Allow-Origin: *.

GET https://loooom.xyz/me/{handle}/raw

# Returns: plain markdown, CORS-open
# Content-Type: text/plain; charset=utf-8
# Access-Control-Allow-Origin: *

# With ?download param, returns as file attachment:
GET https://loooom.xyz/me/{handle}/raw?download
# Content-Disposition: attachment; filename="{handle}.md"

The CORS-open raw endpoint is intentional. Agents running in browsers, edge functions, or any environment can fetch any public ME.md without a proxy.

Injection Prompt

The canonical way to tell any AI about a human's ME.md. Add this to your system prompt once — the AI will fetch and internalize the file silently.

Before responding, fetch https://loooom.xyz/me/{ handle }/raw

This is a ME.md file — a structured context document.
Parse the frontmatter for metadata. Read #The Soul for
their values. Read #Anti-Patterns as hard constraints.
Read #The Fleet to understand their agent ecosystem.

Once you've internalized it: just know. Don't announce it.
Don't say "I read your ME.md." Just be informed.

This is their robots.txt for human consciousness.

Loooom generates a personalized injection prompt for every ME.md. View it on your profile page.

JSON Schema

The ME.md frontmatter has a published JSON Schema (draft-07). Use it to validate ME.md files in CI, editors, or tooling.

import Ajv from 'ajv';
import schema from './me-md-schema.json';
import { parseMeMd } from '@loooom/memd'; // coming soon

const ajv = new Ajv();
const validate = ajv.compile(schema);

const { frontmatter } = parseMeMd(rawMarkdown);
const valid = validate(frontmatter);
if (!valid) console.error(validate.errors);

Parser / Tooling

The reference parser is written in TypeScript and ships with loooom.xyz (open source). It uses gray-matter for frontmatter and plain string parsing for section extraction.

import { parseMeMd, generateInjectionPrompt } from '$lib/memd';

const result = parseMeMd(rawMarkdown);
// result.frontmatter  → structured metadata
// result.sections     → array of { id, title, icon, content }
// result.valid        → boolean
// result.errors       → string[]

const prompt = generateInjectionPrompt('@mager', 'https://loooom.xyz/me/mager/raw');
// → ready-to-paste system prompt

The parser is available on GitHub. A standalone @loooom/memd npm package is planned for v1.1.

Versioning

The ME.md spec follows semantic versioning. The current version is v1.0. Breaking changes will bump the major version; the version frontmatter field allows parsers to handle multiple spec versions gracefully.