← All essays

    Excerpted from 55 and Out, AI Automation

    The Prompt Library That Lives in a Single Markdown File

    ·3 min read

    I have one file. It's called prompts.md. It lives in a notes folder synced across my devices. It is currently 47 prompts long and has saved me, conservatively, hundreds of hours.

    The format is dead simple:

    ## Name of the prompt
    Brief note about when to use it.
    
    The actual prompt text, ready to copy-paste, with [[BRACKETS]]
    around the parts you fill in.
    

    That's it. No tags, no app, no UI, no syncing software beyond the notes app I already use. Cmd-F finds anything in under a second.

    A few of the prompts that earn their keep:

    • "Steelman this." Pastes in an argument I disagree with, asks for the strongest version. Great before responding to anyone in writing.
    • "Cut this in half." Paste any draft, get back a version with half the words and the same meaning. Brutal and useful.
    • "What am I missing?" Paste a plan or decision, ask for the three things I haven't considered. Cheap second opinion.
    • "Explain this code." Paste any unfamiliar function, get a plain-English walkthrough.
    • "Draft a polite no." Paste the request, get three versions of a polite decline at different formality levels.
    • "Compare these three options." Paste three of anything, get a structured comparison.

    The library grew organically. Every time I found myself writing the same kind of prompt twice, I added it to the file. Every quarter or so I prune the ones I haven't used in months.

    What surprised me: how rarely I use the "fancy" features of the AI tools. Memory, custom GPTs, vector stores, tool calling — interesting, but for 90% of my actual work, I just paste a prompt and some text and get a useful answer.

    What broke: I lost an earlier version of the file in a sync conflict. Now it's in version control. Every change committed. Lesson — if a thing is doing real work, version it.

    What I'd do again: keep it boring, keep it portable, keep it local. What I wouldn't: lock my prompts inside any one product. The model will keep changing. The file shouldn't have to.

    The deeper point: most of what people call "AI workflow" is really just knowing what to ask, having it written down, and being able to find it. You don't need infrastructure for that. You need a markdown file.

    Share

    This essay is excerpted from the book.