DEV Community

Cover image for Your prompt library is a mess. Here's a local-first fix.
Deepsol
Deepsol

Posted on

Your prompt library is a mess. Here's a local-first fix.

#ai #productivity

Somewhere between your browser history, a Notion page, a Google Doc and the notes app you abandoned in March, there is a collection of prompts you spent real time crafting. You cannot find any of them when you need them, and you have rewritten the same system prompt at least eleven times.

I have been there. I write prompts for work, and until recently my "library" was a folder of .txt files with names like final_FINAL_v3.txt and one very embarrassing prompts_copy_THISONE.md.

The three things a prompt library actually needs

After rebuilding mine, I keep coming back to three requirements:

  1. Searchable. If I cannot type "legal" and instantly see every legal-related prompt I own, the library does not exist.
  2. Variables, not hardcoded details. A prompt that says "You are a lawyer for Acme Corp, HQ in Boston" is useless for every other client. A prompt with {{company}} and {{location}} placeholders is a template you can reuse forever.
  3. Local and private. Prompts are a small window into how I work. I do not want them in a cloud service that trains on them. I want them on my disk.

What I stopped using, and why

  • Notion — a great database, a terrible place for things you need in under three seconds. Loads slow, search is fuzzy.
  • Browser history — you cannot search your history for "that prompt with the JSON schema."
  • ChatGPT / Claude / Gemini saved prompts — they live in one vendor's ecosystem, and they do not move with you.

What I use now

I ended up building a small desktop app called Qrush Vault. It is a free, local-first prompt manager for Windows and Mac:

  • A searchable library of prompts, organized with folders and bookmarks.
  • {{variables}} saved as presets, so one prompt becomes a reusable template.
  • One-click copy into ChatGPT, Claude or Gemini.
  • Everything stays on your machine. No cloud, no account, no training-data risk.

I built it because the alternatives were either cloud-only, browser extensions, or subscription tools for something that should be a file on my disk.

The takeaway

You do not need a complex system to manage prompts well. You need a local file, a search bar, and variables. If you are still copy-pasting the same three paragraphs into ChatGPT every morning, fix that this week. Your future self will stop rewriting final_FINAL_v3.txt for good.

Top comments (0)