🗣️ Communication and learning
The communication commands in family 10: compress without losing the essentials, explain at the right level, teach progressively, translate and rewrite while preserving intent, change formats, and adapt to the audience.
📰 /brief — executive summary on one screen
Delivery only the essential context, the decision, the evidence, the risks, and the next action. A brief isn't a summary — a summary shortens everything equally; a brief cuts what won't change the decision and preserves what will.
🗜️ The 5 parts of the brief, in this order
- •Decision requested or made: first line. Anyone who reads only that already knows what it’s about.
- •Essential context: 2-3 sentences. If the decision still makes sense without the sentence, cut it.
- •Evidence: the 2-3 facts that support it — with sources.
- •Risks: what can go wrong and what to do if it does.
- •Next action: who does what by when.
🎯 Copy and run
/brief sobre <documento, análise ou situação>; decisão na primeira linha, contexto em até 3 frases, 3 evidências com fonte, 2 riscos com mitigação e próxima ação com dono e data; máximo de 200 palavras
How to verify: fits on a phone screen without scrolling — and the first line alone tells you what's at stake.
✓ Decision-making brief
- ✓"I recommend migrating to gateway B in October. Cost drops 18% (proposal attached); risk: 1 week of integration — Ana leads, plan B: keep A until December."
- ✓Someone who reads it in 40 seconds can say yes, no, or “I need to know X.”
✗ Informative summary
- ✗"This document analyzes payment gateway options considering several factors relevant to the company’s current context..."
- ✗Three paragraphs later, the recommendation still hasn’t appeared.
💬 /explain — explain at the right level
Adapts depth and vocabulary suited to the audience and uses examples when they improve understanding. The parameter that makes the command work is the level — without it, the model guesses an average audience that doesn't exist.
| Level | What changes | Example for "API" |
|---|---|---|
| Nontechnical | Everyday analogy, zero jargon | “It’s the waiter between you and the kitchen: you order, they bring it.” |
| Technical beginner | Concept + one concrete example | "An address that accepts requests in a defined format and returns data." |
| Professional | Precision, trade-offs, no analogy | "Versioned REST or gRPC contract, with authentication and rate limits." |
The same concept, three correct explanations — the difference is who they’re for.
🎯 Copy and run
/explain <conceito> para <nível: leigo | iniciante técnico | profissional | especialista>; ajuste vocabulário e profundidade, use no máximo um exemplo e diga o que deixou de fora por causa do nível
How to verify: the final part (“I left out X”) is there — it’s what keeps a simple explanation from becoming a wrong explanation.
💡 Practical tip
Ask "explain to
🎓 /teach — teach progressively
Organizes concept, intuition, example, practice, common mistake, and learning check. Six stages in a fixed order—because skipping intuition produces rote memorization, and skipping verification produces false confidence.
Concept and intuition
Name it and define it in one sentence, then give a mental image: “think of it as...” Intuition comes before rigor.
Example and practice
One worked example, then a similar problem for the person to solve. Without practice, the example is entertainment.
Common mistake and verification
Name the mistake every beginner has made; then ask a question only someone who understood can answer correctly.
New here? Learning check is a short question or task that distinguishes someone who understood from someone who memorized. "What is X?" tests memory; "What would happen to X if Y changed?" tests understanding. The second one is worth asking.
🎯 Copy and run
/teach <conceito> para <perfil do aprendiz>; conceito em uma frase, intuição com imagem mental, exemplo resolvido, exercício para praticar, o erro mais comum e uma pergunta de verificação que exige compreensão (não memória)
How to verify: the final question can’t be answered by copying the definition — if it can, it’s recall, not verification.
🔤 /translate + /rewrite — preserve intent
/translate preserves meaning, tone, and technical terms, adapting only what’s necessary. /rewrite preserves the essentials and optimizes for a stated objective: clarity, tone, persuasion, or concision. Neither invents content—both protect the intent.
✓ Goal-oriented rewrite
- ✓"/rewrite objective=conciseness: cut 40% while keeping all numbers and the call to action."
- ✓"/translate to en-US, keeping the technical terms already used in English and the informal tone."
✗ Drifting rewrite
- ✗"Improve this text" — improve it for what? The model picks a random goal, and you don’t know which one.
- ✗A translation that "adapts" the joke, example, and order of the arguments—and returns a different text.
🎯 Copy and run
/rewrite <texto> com objetivo=<clareza | tom X | persuasão | concisão N%>; preserve todos os fatos, números e a CTA; liste ao final o que mudou e por quê
How to verify: the list of changes contains no new or removed facts — only changes in form.
💡 Practical tip
When translating technical material, provide a glossary: "keep in English: deploy, endpoint, webhook". This prevents "deploy" from becoming "implementation" midway through a tutorial that uses the English term.
🧾 /format — transform format, not content
Converts the same information for a table, JSON, checklist, memo, script, or another format. The golden rule: nothing goes in, nothing comes out — only the form changes. If the new format "needed" an extra piece of data, you used the wrong command.
| Usage | Format | Why |
|---|---|---|
| Compare options | Table | The eye scans columns; differences stand out |
| Execute without forgetting | Checklist | Each line is binary and checkable |
| Feed a system or agent | JSON | Machine-readable without interpretation |
| Convince someone who’s busy | One-page memo | Decision up top, reasoning below |
| Record a video or present | Timed script | Speech has rhythm; continuous text doesn’t |
Choose the format based on what the person will DO with the information, not what looks nice.
🎯 Copy and run
/format <conteúdo> para <tabela | checklist | JSON com schema X | memo | roteiro>; não adicione nem remova informação; ao final, confirme que todos os itens do original estão presentes
How to verify: the final confirmation lists the items from the original and marks each one as present — none are “adapted” or “summarized.”
New here? Schema is the definition of a JSON structure: which fields exist, what types they are, and which are required. Asking "/format for JSON" without a schema returns an invented structure; with a schema, it returns exactly what your system expects.
👥 /audience — adapt to your audience
Adjusts language, examples, depth, objections, and call to action for the defined audience. It’s /explain with two extra ingredients: the objections that audience will raise and what you want them to do after reading.
🎯 What changes by audience
- •Examples: finance understands "R$ 40 mil/ano"; the technical team understands "3 sprints"; the customer understands "one less afternoon of work per week."
- •Objections: each audience has its own — cost, technical risk, adaptation time. Anticipate the right one.
- •CTA: "approve the budget", "review the architecture", "try it free for 14 days" — three audiences, three verbs.
🎯 Copy and run
/audience <mensagem> para <público: cargo, nível técnico, o que ele ganha e o que ele teme>; ajuste exemplos e profundidade, antecipe as 2 objeções mais prováveis desse público e termine com a chamada à ação certa para ele
How to verify: the anticipated objections are the ones THIS audience would raise — not generic objections. And the CTA is a verb this audience can act on.
⚠️ Adapting isn’t flattery
Adapting to the audience changes examples, order, and emphasis—it doesn’t change facts, risks, or the recommendation. If the version for the director hides the risk shown in the version for the team, that isn’t /audience; it’s omission.
🔗 Pipeline /brief → /explain → /audience
Communication commands become more powerful in a sequence. The order compress → calibrate → adapt isn’t arbitrary: each stage works on the previous one’s output, and reversing any pair wastes work.
Illustrative: three questions in sequence—what’s essential, how deep, and for whom.
🎯 Copy and run
/chain(/brief -> /explain nível=<nível> -> /audience público=<público>) sobre <documento>; mostre a saída de cada etapa separadamente antes da versão final
How to verify: the /brief output is already contained in the /explain output, which is contained in the final output — nothing was reintroduced after being cut.
💡 Composite recipe
Run the chain once for each audience: /chain(/brief -> /audience público=diretoria), then ... público=time técnico. The /brief stays the same; only the final stage changes. That’s how one analysis becomes three messages without turning into three analyses.
New here? Handoff is the mechanism behind /chain (detailed in module 6.2): the result of one command becomes input for the next, without you copying and pasting. It ensures that /audience works on the brief — and doesn’t process the original document again.
🛠️ Workshop: one email in 4 formats
Time to run it all together. Grab an email real — preferably one you needed to send to more than one person and sent the same way to everyone. It will become four pieces with the same content for different readers.
Version 1 — approver
/brief /audience público=diretoria. Decision in the first line, cost and risk, CTA "approve by Friday".
Version 2 — executor
/explain nível=profissional /audience público=time técnico. Explicit trade-offs, objection anticipated: “will this delay delivery of X?”
Version 3 — operator
/format checklist. Each step is binary, with execution order and what to check.
Version 4 — external partner
/translate en-US /rewrite objetivo=tom formal. Technical terms preserved, internal information removed—and declared as removed.
🎯 Copy and run
/chain(/brief -> /audience público=diretoria) sobre <cole o e-mail>; depois /explain nível=profissional /audience público=time técnico; depois /format checklist; depois /translate en-US /rewrite objetivo=formal. Ao final, tabela: cada fato do original × presente em qual versão
How to verify: the final table shows all the original facts present in versions 1–3; in version 4, every omission is stated and justified (“internal information”).
✓ Well-run workshop
- ✓Four texts of very different lengths with the same set of facts.
- ✓You can point out, for each version, which command produced which change.
✗ Workshop that turned into a rewrite
- ✗Four similar texts with synonyms swapped in.
- ✗The version for executives has 3 paragraphs of context—the /brief didn’t run; it was only mentioned.
Quick self-check (optional): what's the difference between /brief and an ordinary summary?
🎓 Module Summary
Next Module:
6.2 - Meta-commands and mastery — /mode, /chain, and /preset: the three commands that operate on the other 97 and bring the course to a close.