Why I Keep My Prompts in a Plain Text File
aipromptsworkflow

Why I Keep My Prompts in a Plain Text File

Marcus Webb
Marcus Webb
June 25, 2026·
3 min

For about a year I kept my best prompts inside chat windows,then lost them the moment I closed a tab. So now I keep my prompts in a plain text file, and that one boring decision fixed more problems than any fancy prompt manager ever did. The file lives in my project repo, sitting right next to the code it actually serves. When I need a prompt, I open the file, not a browser.

Why plain text wins

A text file opens in any editor, on any machine, with no account and no export step. Most prompt advice agrees that for simple cases a plain .txt or Markdown file is enough, and you only reach for YAML or JSON once you need real templating. I rarely do. The point is that nothing sits between me and the words I want to reuse, and nothing can hold those words hostage behind a login.

Plain text also survives. Tools come and go, but a file I can grep will outlive every shiny app I tried and abandoned. I have lost prompts to three different products that shut down. I have never lost one to a text file.

What I actually store

  • The prompt itself, with a short note on what it was for
  • The model I ran it against, since wording that works on one can flop on another
  • A line on what went wrong last time, so I do not repeat the same mistake twice

That third line matters more than it sounds. Half of prompting is remembering your own failures, and memory fades faster than I like to admit.

Treating prompts like code

Once a prompt lives in a file, it joins the rest of my project as a real artifact. I can diff it, review it, and roll it back when an edit makes things worse. The common guidance is to drop these files into a dedicated prompts directory and organize them by task, which is exactly what I did after the folder got messy. Some of these are extensions of the prompt habits that actually work for me day to day, and kepeing them in version control means I can see how each one evolved.

The small friction that helps

Opening a file is just enough friction to make me think before I paste. I scan the note, tweak one line, and run it deliberately. (I never get that pause from a saved chat that auto-suggests my last message.) Boring tools encourage careful work, and a plain text file is about as boring as it gets. That is the whole point.

This content was created with the help of AI. Contact TXTrepo if you find inaccuracies.