Building a Maintainable Template and Prompt Library

[Video placeholder. Recording pending. The lesson walks through organizing a real, messy snippet library into something that survives the next quarter.]

The library starts at twenty

Below twenty snippets, your brain is the index. You remember every trigger. Above twenty, you forget. The library stops being a tool and starts being a search problem.

If you have skipped ahead and already have thirty or forty snippets, you have probably noticed the effect: triggers you cannot remember, snippets you wrote and forgot about, and a growing suspicion that the tool is making your life harder, not easier.

The fix is not to write fewer snippets. The fix is to organize the ones you have.

Three rules that hold up

Rule one: groups by purpose, not by source. A snippet that closes an email goes in the "Email" group whether you wrote it from scratch or imported it. A prompt that summarises a meeting goes in "Meetings" whether it lives in your AI Companion or your custom group. Mixing "things I made" with "things I imported" creates a folder structure nobody can navigate.

Rule two: triggers follow a prefix system. Pick a punctuation mark you never type at the start of a normal word. Use it as the prefix for all your custom triggers. Reserve that prefix for your own snippets so you never collide with built-in ones. Then use a sub-prefix per group: ;e: for email, ;s: for sales, ;m: for meetings.

Rule three: every snippet has a one-line description. When you search, you search descriptions, not bodies. A snippet whose description is blank is a snippet you will rewrite in six months because you cannot remember why it exists.

Backup as a habit, not a project

Snipset supports JSON export and import. Make this a quarterly habit, not a "I will do it when I have time" task. Set a calendar reminder. The library that survives a hardware failure is the library that survives.

If you keep your library in a version-controlled folder, even better. The diff between "last quarter's library" and "this quarter's library" tells you what you actually changed. That is useful information when you wonder why a snippet no longer feels right.

The Prompt Manager sidebar

Once you have ten or more prompt snippets, the Prompt Manager sidebar becomes your primary surface. Three habits make it work:

• Group your prompts by task ("summarise", "draft", "rewrite"), not by source.
• Drop prompts you have not used in a quarter into a "maybe later" group, not the trash. Some prompts go unused for a season and become useful again.
• If a prompt is bad, rewrite it the same day. A bad prompt in your library is worse than no prompt, because it trains your muscle memory to reach for the wrong thing.

Exercise: organize what you have

Pick the day after this module to spend ninety minutes on your library. Do four things:

1. Move every snippet into a group that matches its purpose.
2. Apply the prefix rule to your custom triggers.
3. Write a one-line description for every snippet that lacks one.
4. Export a backup.

You will not regret the time.

How this connects to Snipset

Snipset groups live in the sidebar. The Prompt Manager is the AI-flavored subset of your groups. JSON export covers the full library, including groups, descriptions, and triggers. Module 09 covers the AI layer that sits on top of this organized library.

What is next

Module 09 covers the AI features themselves: chat, snippet generation, and the local Ollama setup. By that point, your library will be organized enough that adding AI snippets feels like the natural next step.