🗂️ Organize prompts, briefs, and playbooks in one place
The library doesn’t need to be sophisticated to work. It needs to be flat and easy to find. Too much hierarchy kills adoption—no one remembers which subfolder inside another subfolder holds something. Three folders, one index.
/prompts
Tested inputs ready to reuse. One prompt per file. Name it with the scenario and version.
/playbooks
One-page processes with steps, a standard prompt, and metrics. The heart of the library.
/briefings
Reusable context: who the client is, what the voice style is, what the project constraints are.
🏷️ Naming and versioning (v1, v2, current champion)
The name is your library’s interface. If you can’t find something in 10 seconds, the naming convention has failed. The rule is simple: [what-it-does]-[situation]-v[number]. Optionally add "-campeao" to the version you use most.
✓ Names that work
- post-gancho-linkedin-v3
- email-cliente-bravo-v2
- playbook-onboarding-freelancer-v1
- resumo-reuniao-executiva-v4-campeao
✗ Names that don't work
- good prompt
- FINAL template (2)
- copy of a copy of the email
- use this one
Golden rule of versioning
Never delete — retire. The old version is a learning history. Moving it to /aposentados keeps the index clean without losing the evolution trail. Six months from now, you'll be glad you saved v1.
✅ Checklists based on repeated processes
A checklist isn’t bureaucracy—it’s externalized memory. When you carry out a process that depends on not forgetting critical steps, a checklist saves you from errors and rework. It comes from repetition, not theory.
✓ Processes that call for a checklist
- ✓ Content publishing (review, format, schedule)
- ✓ Delivery to the client (review, version, send)
- ✓ Project kickoff (briefing, access, folder)
- ✓ Any process with a step you’ve forgotten before
✗ When a checklist doesn't help
- ✗ Creative process with no fixed steps
- ✗ A unique, one-time task
- ✗ A checklist so long that no one reads it to the end
- ✗ Obvious steps with no risk of being forgotten
💡 The 3-run rule
If you’ve done the same process in a similar way 3 times, it’s time to create a checklist. Before 3, you’re still figuring out the steps. After 3 without a checklist, you’re memorizing what could be documented.
🧹 Curation: retiring what stopped working
A library that only grows becomes a dead archive. Quarterly curation is what keeps the system living and navigable. It's 15 minutes every 3 months—no ceremony, no meeting, no consulting.
Did I use this in the last quarter?
If the answer is no: move it to /aposentados. Don’t delete it—the history is valuable for seeing how far you’ve come and avoiding starting over with the same mistake.
Does it still work the way it’s written?
If the context has changed (new tool, new client, new format), update the prompt or playbook and bump the version. Never edit without versioning.
Is there anything better I’ve learned since the last version?
If yes: create a new version with the improvement and keep the previous one as history. The process evolves without losing the learning trail.
Should this process be shared?
If it worked consistently and someone else could use it: consider sharing it—with your team, a client, or as public content.
When to curate
Set a recurring reminder every 3 months. Duration: 15 minutes maximum. If it takes longer, the library has grown too quickly—a sign you need to be more selective about what you add.
🤝 Share with your team/clients
A shared library is authority asset. When you can deliver not just the result to your client, but also the process—you stop being a service provider and become a strategic partner. The same applies within the team.
Share with the team
- → Onboarding a new team member: link to the relevant playbooks
- → Standardizes practices without a meeting to get everyone aligned
- → Individual errors become collective learning
- → Someone improves a process and everyone benefits
Share with clients
- → Monthly report + the delivered process playbook
- → Show the method, not just the result—a differentiator that’s hard to copy
- → The client understands the value, making it easier to keep the contract
- → Opens a conversation about scaling the process
💡 Library as content
If you create public content, your playbooks are content material. "My process for X" is one of the formats that drives the most engagement—because it delivers a method along with the result.
⚡ Latecomer shortcut: the 3 prompts you use most
Don’t wait until you have 30 items in the library to start. The the minimum viable number is 3. Think of the 3 prompts you use most—the ones you open often or keep recreating from scratch because you can't find where you saved them.
Data: [____] Sessão: [tema ou tarefa]
O que tentei: [descreva em 1 linha o que você fez]
Funcionou? [sim / não / parcialmente]
Por quê: [o que explica o resultado]
Vira template? [sim → copiar estrutura / não → ajustar]
Vira regra? [sim → escrever como "sempre fazer X" / não]
Onde guardei: [/prompts / /playbooks / /briefings / nenhum]
---
Nota do dia (0–10): ___
O que repetir amanhã: ___How to identify the first 3
- → What prompt do you recreate from scratch every week?
- → What task takes you the longest because you “have to remember how to do it”?
- → What process have you already explained to someone more than once?
What to do with them
- 1. Write each one in 1 simple paragraph
- 2. Name it using the [what-it-does]-v1 convention
- 3. Save it in the right folder (/prompts or /playbooks)
💼 In your profession
The method is universal. The library is specific. See how each profile builds theirs—and use it as a reference to imagine what yours might look like after 1 year of consistent use.
Teacher
- ✓ Lesson plan bank by class and level
- ✓ Templates for personalized feedback by student profile
- ✓ Evaluation structures that worked
Lawyer
- ✓ Bank of arguments and document templates
- ✓ Prompts for case law summaries
- ✓ Contract review checklist
Seller
- ✓ Objection playbook with tested responses
- ✓ Follow-up templates by funnel stage
- ✓ Proposal structure that closes deals
Manager
- ✓ Decisions recorded with the criteria used
- ✓ Templates for 1:1 meetings and retrospectives
- ✓ Team onboarding playbook
Creator
- ✓ Winning structures by format and platform
- ✓ Hook prompts for LinkedIn, Instagram, and YouTube
- ✓ Bank of angles and hooks that performed well
Any profession
Start with the 3 prompts you use most. Document each one in 1 paragraph. It's the minimum viable approach—and enough to see the value before scaling up.
# Biblioteca Pessoal de IA — [Seu Nome]
## Última curadoria: [data]
---
### /prompts — ativos
| Nome | Versão | Status | Última vez usado |
|-------------------------------|--------|----------|-----------------|
| post-gancho-linkedin | v3 | campeão | 2026-06-10 |
| email-cliente-bravo | v2 | ativo | 2026-06-08 |
| resumo-reuniao-executiva | v4 | campeão | 2026-06-11 |
---
### /playbooks — ativos
| Nome | Versão | Processo cobre |
|-------------------------------|--------|---------------------------------|
| playbook-onboarding-freelancer| v1 | primeiros 3 dias com novo cliente |
| playbook-producao-conteudo | v2 | criação semanal de posts |
---
### /aposentados
- post-gancho-linkedin-v1 · aposentado em 2026-03-01
- email-cliente-bravo-v1 · aposentado em 2026-04-15
---
## Próxima curadoria: [data + 3 meses]Module 4.2 Summary
- ✓ Three-folder structure: flat, easy to navigate, with no hierarchy nobody maintains.
- ✓ Naming convention: [what-it-does]-[situation]-v[number]. Simple enough to last.
- ✓ Checklists come from repetition—the rule of 3 identical runs.
- ✓ A 15-minute quarterly review keeps the library alive, not a dead archive.
- ✓ A shared library is an authority asset — onboarding, differentiation, and content.
- ✓ Slow User Shortcut: start with 3. Complexity comes after proven value.
- ✓ Every profession has its own library — the method is the same, the content is specific.
📦 Module deliverable:
Create the index using the template in topic 7. Add at least 3 items (they can be things you already use today, even if they aren’t documented). Set the date for the next review. This is the start of your library.
Next Module:
You’ve completed Track 4. The method is documented. Now Track 5 — Architecture — teaches you to connect these methods into systems: where processes link together and intelligence multiplies.