PTENES
TRACK 3 · CONTEXT ENGINEERING

🗺️ Context Engineering

"Context is the map." What does AI need to know to understand better? Learn to provide the world it needs to see—and discover that poor answers are almost always due to poor context.

The case in this learning path—the generic campaign: "Create a campaign for my project" generates something that would work for any company on the planet. The AI wasn't weak: it was BLIND. Same prompt + context folder (audience, examples that worked, brand voice, limits) → a campaign that looks like it was made by someone who's worked there for years. Neither the prompt nor intent can fix blindness — only context can.

2
Modules
14
Topics
~1h45
Duration
Medium
Level
Prompt without context Generic answer 😐 Target audience Brand tone Good examples Rules/limits Prompt + Context complete map Personalized answer looks like it was made by someone on the inside ✓ 📁 CONTEXT FOLDER without context ↑ with context ↓

Learning path map

Detailed content

3.1 ~50 min

🗂️ What context is (beyond the prompt)

Bad responses almost always come from poor context. You’ll learn to identify every type of context AI can receive — and start building your first real context folder.

What is:

Context is everything you provide to AI beyond the immediate request: conversation history, files, examples, rules. Without context, AI navigates without a map — it gets somewhere, but rarely to the right place.

Why learn:

Shifting from “why did AI get it wrong?” to “what didn’t I tell it?” is the biggest mindset shift in the pyramid. It solves 80% of frustrations without changing the model or the prompt.

Key concepts:

Context as a map, information gaps, diagnosing poor responses, context mindset.

What is:

The complete inventory of what you can give AI: text files and spreadsheets, images and PDFs, previous conversation history, examples of what works and what doesn’t, internal rules, brand identity, and audience profile.

Why learn:

Most people use only free text. Knowing all the types opens up a menu of possibilities most people ignore—and each type solves a different problem.

Key concepts:

Types of context, files, images, history, positive/negative examples, rules, brand identity.

What is:

The practical guide to uploading files to ChatGPT, Claude, and Gemini: accepted formats, maximum size, the difference between pasting text and uploading it, and what AI actually sees after you send it.

Why learn:

Each tool behaves differently. If you don’t know that, you may think the AI “ignored” the file when it actually wasn’t processed correctly.

Key concepts:

File upload, supported formats, paste vs. upload, the file’s context window, differences between tools.

What is:

Showing AI an example of what you want (like this) and one of what you don’t want (not like this) is the most efficient way to calibrate the result. It works because AI learns patterns—examples are concrete patterns.

Why learn:

Three paragraphs of instructions are equivalent to two well-chosen examples. It saves time and improves accuracy — especially for tone and style, which are hard to describe in words.

Key concepts:

Positive examples, negative examples, few-shot with context, tone calibration.

What is:

A fixed block of text that describes how you (or your brand) communicate: tone, vocabulary, what to avoid, and how to address the customer. You write it once and paste it at the start of each conversation — the AI automatically maintains consistency.

Why learn:

Without voice context, every response sounds like it came from a different company. With it, even someone who just opened the tool can produce something in the right tone. It’s the highest return on investment in context.

Key concepts:

Brand identity, brand voice, consistency, reusable fixed context, identity block.

What is:

Not everything you know is useful for the AI to know. Irrelevant context dilutes what matters, increases cost, and sometimes worsens the response. The exercise is to separate signal (what guides) from noise (what distracts).

Why learn:

Advanced context skills aren’t about “including everything”—they’re about knowing what to leave out. People who learn this resolve conversations faster and get more precise responses.

Key concepts:

Noise × signal, context window, minimum sufficient context, information curation.

What is:

What never goes into context: identifiable customer data, passwords and tokens, confidential contracts, health data, real CPF/CNPJ numbers. How to anonymize before using: [NAME], [COMPANY], [CPF]. The golden rule: “Would I paste this into a public WhatsApp group?”

Why learn:

Each tool has a different data-use policy. Sensitive data pasted by accident may be used for training, exposed in breaches, or violate LGPD. One minute spent anonymizing it can prevent years of trouble.

Key concepts:

Sensitive data, anonymization, [NAME]/[COMPANY], LGPD, public group rule, tools’ data policies.

View Full
3.2 ~55 min

🛠️ Context engineering in practice

From theory to a working context folder: you build your project's permanent brief, learn the 5-line mini-brief, and discover how to apply it in your specific profession.

What is:

A living document — one to three pages — that summarizes everything the AI needs to know about your project: who you are, who the audience is, examples that work, tone, and constraints. You keep it updated and paste it at the start of every new conversation.

Why learn:

Most people explain the project all over again every time. A permanent briefing eliminates that waste: 30 seconds to paste versus 10 minutes to re-explain. It also ensures consistency across sessions.

Key concepts:

Standing brief, living document, quick reference, consistency across sessions, Kit T3.

What is:

A folder structure designed specifically for AI context: /briefing (who we are), /good-examples, /bad-examples, /constraints, /audience. Unlike a generic file folder, each subfolder has a clear context purpose.

Why learn:

When you need context quickly, you know exactly where to find it. Organizing this way also makes updates easier: when the audience changes, you only update /publico.

Key concepts:

Context folder, structure by type, /briefing /exemplos /restricoes, modular maintenance.

What is:

How to extract implicit context you’ve already provided from past conversations: decisions, approved examples, corrections the AI accepted. Summarize it in 3–5 bullet points and turn it into input for the next brief.

Why learn:

Every good conversation contains context you've built iteratively. Losing it when the session closes means throwing away work that took time. Extracting it is recycling intelligence.

Key concepts:

History as context, decision extraction, session recycling, manual memory.

What is:

A one-page document describing who will read or use the result: demographic profile, main pain points, language that resonates, and what turns them away. The AI uses this to automatically calibrate tone, examples, and depth.

Why learn:

AI writes for the audience you identify. Without a profile, it assumes a generic reader. With a profile, emails, posts, and other texts reach the right level without rework.

Key concepts:

Audience dossier, ICP, reader profile, automatic tone calibration, personas.

What is:

An explicit list of prohibitions and limits: "never mention competitors by name," "don’t use humor," "don’t promise a timeline without internal approval," "follow law X." These guardrails prevent problems before they happen.

Why learn:

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.

Key concepts:

Context constraints, guardrails, compliance, prohibited items list, operational security.

What is:

No time for the full brief? Use the 5 essential lines: (1) Who I am / who the company is, (2) Who this is for, (3) The goal of this specific result, (4) Desired tone, (5) One critical constraint. In 2 minutes, you’ll create context that multiplies the quality of the response.

Why learn:

The lengthy-briefing barrier makes people give up and paste prompts without context. The mini-briefing removes that barrier: anyone, no matter how rushed, can use it. It’s the minimum viable context.

Key concepts:

Mini-brief, 5 lines of context, context MVP, low friction, practical shortcut.

What is:

Profession-specific context: teacher (class profile + curriculum + level); lawyer (firm templates + usual case law + client); salesperson (ICP + frequent objections + sales cycle); manager (quarterly goals + budget constraints); creator (niche + 3 posts that performed well + tone).

Why learn:

The principle is universal, but the context is specific. Seeing your actual work turns an abstract concept into immediate action: you’ll leave knowing exactly what to put in your folder.

Key concepts:

Context by profession, teacher/lawyer/salesperson/manager/creator, specific application, professional folder.

View Full
← Back to Start Next Track: Leverage →