Drafts

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me a capture app that replaces Drafts: it opens to a blank page, I write, and I decide afterwards where the text goes.

STACK
- The app: native for the platform you live on, or a PWA with an offline-first store if it must be everywhere. Launch speed decides this — a capture app that takes a second to open has already failed
- Local storage first: SQLite on device, with everything working offline forever
- Optional sync server: Node 20+ with Fastify and SQLite, storing encrypted blobs
- Caddy in front

THE ONE RULE
- Opening the app puts the cursor in an empty document. Not a list, not yesterday's note, not a menu. Every launch, every time
- If the app was open thirty seconds ago, continue what was being written; after that, a new blank page
- The keyboard is up before the animation finishes. This single behaviour is the entire product — measure it, and treat any regression as a bug of the highest severity

THE DATA MODEL
- drafts: id, body, title_derived, created_at, updated_at, folder, is_flagged, is_archived, is_trashed, language
- tags and draft_tags
- versions: id, draft_id, body, at — every save keeps a version, so nothing typed is ever lost
- actions: id, name, icon, group, steps_json, keyboard_shortcut, is_enabled
- action_runs: id, action_id, draft_id, status, output, error, at
- workspaces: id, name, filter_json, sort, is_default — a saved query, not a folder

WRITING
- Plain text with Markdown niceties: syntax highlighting, list continuation, checkbox toggling, and a preview when asked for
- The line and word count, unobtrusively
- Undo across the whole session, and versions beyond it
- Find and replace within a draft
- A row of extra keys above the keyboard on a phone — tab, brackets, markdown marks — configurable

ACTIONS, WHICH IS WHAT MAKES IT MORE THAN A NOTEPAD
- An action is a named list of steps run against the current draft
- Steps: copy to clipboard, share, open a URL with the text substituted, append or prepend to a file, send an email, post an HTTP request, run a small script in a sandbox, insert text, set tags, archive or trash, and prompt for input
- Template substitution: the whole draft, the first line, the rest, the selection, the date in any format, a tag, a prompt's answer
- Actions are files that can be exported, imported and shared. That library is the reason the original has the following it does
- Every run recorded with its output and any error, so a failing action is debuggable rather than mysterious
- Actions bound to keyboard shortcuts, to a share sheet, and to a widget

FINDING THINGS AGAIN
- Full-text search over every draft, instant, including archived and trashed
- Workspaces as saved queries: tag, folder, flag, date range, text
- Sort by created, modified, or accessed
- A draft is never deleted by accident: trash keeps everything for a stated period and says so

GETTING TEXT IN AND OUT
- The system share sheet, so text from anywhere lands here in one tap
- A URL scheme and a shortcuts integration for automation from outside
- Dictation, and a capture that starts recording immediately if the platform allows
- Export everything as plain files in one command, in a directory of Markdown with the metadata in front matter. Nothing here should be trapped

SYNC, IF WANTED
- End-to-end encrypted: the server stores ciphertext, derived from a passphrase that never leaves the device
- Conflicts keep both versions rather than choosing, and say so
- Works entirely without it. Sync is a convenience, never a requirement

WHAT NOT TO BUILD
- No account required to use the app. Ever
- No analytics inside a text editor. Not one event — this app holds half-formed thoughts, and that is nobody's business
- No cloud-only feature that makes the offline case second class

OPERATIONS
- If there is a server: .env with DATABASE_PATH, BASE_URL, SESSION_SECRET; migrations on boot; nightly backup of ciphertext
- On device: the database backed up with the platform's own backup, and an export reachable in two taps

WHAT MATTERS MOST
Launch speed and the action system. Measure the time from tap to a cursor in an empty document, get it under a fifth of a second, and build three actions you will genuinely use before writing a fourth screen. Everything else here is a text editor, and text editors are easy.

Give me the app, the sync server if you want one, an example action library, and a README with build steps and the export format documented.