verso.md
Sign in
The markdown editor for your codebase

Your docs live in the repo.
Your editor doesn't.

Until now.

architecture.md
Draft
1# Architecture Overview
2
3## System Design
4
5The application uses a **microservices** architecture with
6event-driven communication via `Redis Streams`.
7
8### Key Components
9
10- API Gateway - routes and rate-limits incoming requests
11- Auth Service - handles OAuth and session management
12- Worker Pool - processes async jobs from the queue
13
Get started

Your .md files are the best
prompts you'll ever write.

Cursor, Claude Code, Copilot. They all read your repo for context. The question isn't whether AI will read your repo. It's whether it'll find specs, or nothing.

Repo without .md specs
✕AI guesses your intent from raw code
✕Generated code doesn't match your patterns
✕Every prompt needs 3 paragraphs of context
Repo with .md specs
✓AI reads your specs and knows the plan
✓Generated code follows your architecture
✓"Build what's in docs/auth-prd.md" just works
Learn how markdown superpowers AI

You've been here before.

Edit markdown in GitHub's textarea. Pray nobody else is editing the same file.

<<<< HEAD ## Setup Install deps... ==== ## Setup Run npm install... >>>> feature-branch

Write docs in Google Docs. Copy-paste into a PR. Lose all formatting.

**bold text** renders as \*\*bold text\*\* `code` renders as \`code\`

Ask the new engineer to write the spec. They've never seen the codebase.

# API Reference | (blinking cursor, empty page)

The only .md editor with full context of your code.

It understands your repo, your team, and your workflow.

verso.md / architecture.md
1# Architecture Overview
2
3## System Design
4
5The application uses a **microservices** architecture
6with event-driven communication via `Redis Streams`.
7
8### Key Components
9
10- API Gateway - routes requests
11- Auth Service - OAuth + sessions
12- Worker Pool - async job processing
Edit
Live
Split
Preview

Edit the doc.
Open the PR.
Skip the engineer.

No codebase download. No copy-paste from Google Docs. No Jira ticket asking someone else to do it.

Publish to GitHub
✕
Branch
md-editor/auth-prd-update
Commit message
Update auth PRD with OAuth flow
PR title
docs: update auth PRD with OAuth flow
Create Pull Request
✓PR #142 openedgithub.com/acme/app/pull/142

Write together.
Not after each other.

getting-started.md
Y
S
A
1# Getting Started
2
3## Prerequisites
4
5- Node.js 22 or later
You
6- A GitHub account
7
8## Installation
Sarah
9
10Clone the repository and install:
11```bash
Alex
12npm install
13```
Comments3 threads
S
Sarah
2m ago

Should we mention the rate limiting here?

A
Alex
5m ago

Added the deployment section you requested.

Y
You
just now

Looks great! Let's move this to review.

Live cursors & presence. See who's editing, where, in real-time.

Conflict-free editing. Built on Yjs CRDTs. No merge conflicts. Ever.

Threaded comments. Pin feedback to specific lines. Resolve when addressed.

Editor & viewer roles. Share drafts with the right level of access.

AI that doesn't hallucinate your API.
Because it actually read the code.

AI Terminal⌘J
>

Codebase-aware context. AI reads your actual source files.

Slash commands: /outline, /summarize, /fix, /translate, /tone, /expand

Ghost text autocomplete. Copilot-style suggestions as you type.

Edit-in-place. AI proposes diffs. Accept or revert with one click.

Your keys, your models. Bring Claude or OpenAI. Keys never leave the server.

Specs become prompts. .md files in your repo are context for every AI tool.

Start with structure.
Not a blank page.

# API Reference

## Endpoints

### GET /api/users

Returns a list of users...
API Reference
# ADR-001: Use Event Sourcing

## Context

The system needs to track all state changes...
Architecture Decision Record
# Welcome to the Team

## First Day Setup

1. Clone the repository
2. Install dependencies...
Onboarding Guide
# v2.1.0 Release Notes

## What's New

- Real-time collaboration
- AI-powered editing...
Release Notes

Your repo deserves a real editor.

Get started
zz