📋 The permanent brief
The doc you paste or attach every time
# Project: [project or company name] Who we are / voice: [describe the tone in 2-3 adjectives + 1 example sentence in the right tone] Audience: [who will read/use the result — profile, level, main pain points] Good examples: [paste 1-2 text excerpts you approve as tone references] Examples to avoid: [paste 1 excerpt or describe what you don’t want] Rules/limits: [list what must never appear — competitors, promises, jargon] Expected result in this session: [what you want to generate now] ⚠ Sensitive data: anonymized (checklist ok)
Save it where you already go every day: Google Docs, Notion, Apple Notes, or a pinned Word doc. The deciding factor isn’t the most sophisticated app—it’s the one with zero friction to open and copy from.
📁 Folder structure the AI understands
Organize for reuse, not for archiving
A context folder isn’t an archive—it’s a living asset. The right structure makes modular updates possible: when the audience changes, you update only /audience. When a new example comes in, it goes in /good-examples.
📁 contexto-[nome-do-projeto]/ ├── 📄 briefing.md ← quem somos, voz, objetivo geral ├── 📄 publico.md ← perfil, dores, linguagem que ressoa ├── 📄 restricoes.md ← o que nunca pode aparecer ├── 📁 exemplos-bons/ ← textos aprovados como referência │ ├── email-exemplo-1.txt │ └── post-exemplo-2.txt ├── 📁 exemplos-ruins/ ← estilos a evitar │ └── contra-exemplo.txt └── 📄 checklist-privacidade.md ← confirmação que dados são seguros
- →One file per type of context (briefing separate from audience)
- →Descriptive file names without accents
- →Last updated date at the top of each file
- →Real examples, not imagined ones
- →Everything in one giant document that’s impossible to update
- →Outdated files without a review date
- →Mixing different projects in the same folder
- →Save to the "Downloads" folder without any structure
♻️ Turn history into reusable context
Your past conversations are worth their weight in gold
Every good conversation where you corrected the AI, approved a passage, or made a decision contains implicit context. That context disappears when the session closes — but you can save it beforehand.
"List the 5 main decisions we made in this conversation, the tone preferences you identified, and the examples I approved."
Add a section called "Accumulated Decisions" or "Confirmed Preferences." Each good conversation adds another layer of precision.
The AI "remembers" everything you pasted — even in a new conversation. It's manual memory, but it works.
🎯 Target audience profile
1 page that improves everything
AI writes for the audience you identify. Without a profile, it assumes a generic, educated adult reader. With a profile, emails, posts, and other texts automatically match the right tone, language, and depth.
# Target audience: [name/description] Profile: [age range, profession, relevant education level] Main pain points: - [pain point 1 — what keeps them up at night] - [pain point 2 — recurring frustration] - [pain point 3 — what they can’t do on their own] Language that resonates: [terms they use, preferred tone, examples] What puts them off: [jargon that annoys them, tone they reject, what sounds fake] Knowledge level about [topic]: [beginner / intermediate / advanced] How they find me: [channel, context, emotional state when they arrive]
"Dear professional, we are pleased to present our innovative solution, which will certainly bring excellent results to your business..."
Generic corporate tone. No one feels spoken to.
"If you’ve spent the last two weeks rewriting proposals and still haven’t heard back, this template will change that..."
Speak directly to the real pain point.
🚧 Internal constraints and rules as guardrails
What AI should never suggest
Without explicit constraints, AI improvises within what it considers reasonable—which may not be what your company, client, or compliance team considers reasonable. Writing down the limits creates operational safeguards before a problem occurs.
- "Never mention competitors by name"
- "Don't mention prices without commercial approval"
- "Avoid specific financial projections"
- "Don't promise a timeline without internal validation"
- "Follow CONAR’s rules for advertising"
- "Don't make unsupported health claims"
- "Include the disclaimers required by law"
- "Avoid language that could be interpreted as a guarantee"
- "Don't use slang"
- "Avoid humor in crisis communications"
- "Never use the passive voice"
- "Forbidden: 'synergy,' 'disruptive,' 'ecosystem'"
⚡ Latecomer shortcut: the 5-line mini-brief
The minimum context that already works
The full brief is ideal—but perfect is the enemy of done. The 5-line mini-brief is the minimum viable context: in 2 minutes, you improve the response quality without having to build the complete folder.
E.g.: "I'm a digital marketing consultant serving small and midsize retail businesses."
E.g.: "For my client, a clothing store owner, 45 years old, nontechnical."
E.g.: "Generate 3 caption options for the store's Instagram for Mother's Day."
E.g.: "Warm tone, no slang, for women ages 35-55."
E.g.: "Don't mention a price promotion — we don't have a discount this time."
Quick context: 1. Who I am: [your role / company in 1 line] 2. For whom: [profile of the reader/user of the result] 3. Goal right now: [what you want to generate in this session] 4. Tone: [3 adjectives or 1 sentence describing the tone] 5. Critical constraint: [what must not appear] [Put the actual request here]
👤 In your profession
5 profiles: teacher, lawyer, salesperson, manager, creator
The principle is universal—the context is specific. Every profession has its standard set of context. Below, what to put in the folder depending on your work.
- 📌 Class profile (age range, level)
- 📌 Course curriculum/syllabus
- 📌 Examples of lessons that worked
- 📌 Recurring student difficulties
- 📌 Constraints in the current lesson plan
- 📌 Sample submissions from the review panel (anonymized)
- 📌 The court’s usual case law
- 📌 Client profile (business/individual, sector)
- 📌 Committee tone (formal, objective)
- 📌 Legislation applicable to the case
- 📌 ICP (ideal customer profile)
- 📌 Most common objections
- 📌 Unique value proposition
- 📌 Sales cycle and stage
- 📌 Anonymized success stories
- 📌 Quarterly/semiannual goals
- 📌 Current budget constraints
- 📌 Team profile (seniority, gaps)
- 📌 Decisions already made (don't reopen)
- 📌 Stakeholders and their interests
- 📌 Niche and positioning
- 📌 3 posts that performed best
- 📌 Audience profile (channel, age)
- 📌 Voice: informal, inspirational, technical?
- 📌 What the audience hates (real criticism)
Use this framework: (1) What information about my work would the AI need to get the tone right? (2) What examples of good results do I have saved? (3) What must never appear in my work context? These 3 questions work for any profession.
📋 Module 3.2 Summary
What you learned
- ✓Standing brief and Kit T3 ready to use
- ✓Folder structure AI understands
- ✓How to reuse conversation history
- ✓One-page target audience dossier
- ✓Constraints as operational guardrails
- ✓5-line mini-brief (shortcut)
- ✓Profession-specific context
What comes next
T4 Leverage — you have prompts and context. Now comes the layer that helps these assets scale: reusable patterns, playbooks, and a living library of operational intelligence.
The context folder you build here is the main input for T4. Context without use is raw material; with use, it becomes a system.
Project brief ready to attach again
Use the T3 Kit (base briefing) for a real project. Create the folder structure. Fill out the audience dossier. Put together the mini-briefing to use when you’re in a hurry. This set is your operational context—it grows with every session.