05 est. 20 min

Build a reusable prompt library (.md files)

Module 05 · est. 20 min · You’ll build: a folder of reusable prompt files you (and your team) grab instead of retyping.

TL;DR: Your best prompts are assets. Save each as a small .md file with a name, when to use it, and the prompt itself. Now you reuse instead of reinvent — and you can hand the file to a teammate and they get your results.

[Operator’s read] Every workflow I rely on started as a saved prompt. The library is the difference between “I got a good answer once” and “I get a good answer every time.” It’s the closest thing to coding you’ll do in this course — and it’s just text files.

The format of a good prompt file

Keep it dead simple — three sections:

markdown

# Daily brief

**When to use:** every morning, to plan the day.

**Prompt:**
You're my operations assistant. Using my calendar and inbox, write a
6-line morning brief: top 3 priorities, anything urgent, one thing I'm
likely forgetting. Plain language. No preamble.

That’s it. A title, a “when to use,” and the prompt. (See the real examples in the course folder: daily-brief.prompt.md, meeting-notes.prompt.md.)

Why .md files specifically

They’re plain text — open anywhere, no special tool.
You can keep them in a Cowork project, a notes app, or a shared drive.
You can paste one into Cowork and it just works.
When you improve a prompt, you update one file and everyone benefits.

Organize by job, not by tool

Name files after the job: weekly-recap, inbox-triage, proposal-review. Future-you scans the list and grabs the right one in seconds.

Lab

Create a prompts/ folder (in Cowork, Notes, or Drive). Turn your 3 corrected workflows from Module 04 into 3 .md files using the format above. You now have a personal prompt library — the thing that makes everything after this fast.