A local-first prompt library beats another cloud notes app

Most prompt tools ask for an account before you save a single string. That made sense when companies wanted retention metrics. It makes less sense when the job is copy this paragraph into the tool you already use.

I built Draft for that job: titled prompts, tags, collections, filters, and a palette you open from anywhere on macOS or Windows. Data lives in open JSON on your drive. You can open the folder, diff files in git, or wipe the app without begging support to export.

What broke with cloud prompt managers

Teams I talked to while shipping other products kept the same workaround—prompts scattered in Notion, Slack saves, and scratch files. Cloud managers added sync and sharing nobody asked for while making retrieval slow. Signing in to paste a commit message template is a category error.

The product boundary is narrow on purpose: store, find, copy. No model calls inside the app, no collaborative editing, no feed. Narrow scope is what keeps latency low and the security story honest.

File layout as a feature

Transparency beats black-box databases for this category. When users know which file holds their prompts, they trust backups. Import and export are not premium gates—they are how you migrate laptops or share a team baseline without granting a vendor admin access to your text.

Electron plus React was the right trade for cross-platform desktop with a small team. Security still matters: disable Node integration in renderers you do not need, keep auto-updaters signed, and treat imported JSON as untrusted input with schema validation.

Designing for the interrupt

Draft’s primary surface is the palette, not a settings-heavy shell. Search filters by tag or collection; stars mark the ten prompts you use every day; copy puts text on the clipboard and dismisses the window. Themes (light, dark, system) are table stakes for a utility that appears over other apps—they are not the thesis.

Response time targets follow familiar HCI guidance: under 100ms for palette open on a warm machine, under 400ms on a cold start after sleep. Those numbers are release criteria, not slogans.

Who this is for

Operators who live in IDEs, support tools, and browser tabs—founders, senior ICs, support leads—gain the most. If you write one prompt a month, keep using notes. If you reuse the same blocks hourly, a dedicated local library pays back in a week.

Brent Haskins — why this shipped

I ship SaaS and native apps for a living; Draft is the utility I wanted while building them. The lesson generalizes: when the workflow is copy-out, not collaborate-in, remove the network from the critical path. That is how you stay out of the way and out of the crosshairs for data requests you cannot answer on a free tier.

If you are evaluating tools, ask where files live and what happens when the company changes pricing. If the answer is vague, build local or buy local.

Windows and macOS parity

Cross-platform desktop means two sets of keyboard shortcuts, two installers, and two code-signing pipelines. Users do not care—they care that Win+Shift+P feels as natural as Cmd+Shift+P. Test on clean VMs, not only developer laptops with forty menu bar apps.

Import paths from other tools

Ship JSON import with a mapping guide for exports from Notion, CSV, or competitor apps. One-time migration hooks beat “start from scratch” for adoption. Validate schema strictly so a malicious import cannot execute scripts.

SEO and discovery for niche utilities

People search “prompt manager mac,” “save ChatGPT prompts,” “local prompt library.” A clear landing page with real screenshots beats keyword stuffing. Link from your main portfolio so authority flows to the product domain.

Draft is part of the same product family as Shelf and Drawer: software that respects files on disk. Brent Haskins publishes notes on how these utilities are built at brenthaskins.com—useful if you are comparing build-vs-buy for internal prompt libraries.