# The Context Engineering Playbook: 15 Copy-Paste Templates That Make Any AI 10x Smarter
**作者**: Nav Toor
**日期**: 2026-04-07T17:44:26.000Z
**来源**: [https://x.com/heynavtoor/status/2041572825698615583](https://x.com/heynavtoor/status/2041572825698615583)
---
(Last time I explained why context engineering killed prompt engineering. This time I am giving you the actual system. Copy these. Paste these. Watch the output change immediately.)
My last article on context engineering went viral. Millions of people read it. Thousands sent me the same message: “I understand the concept now. But what do I actually type?”
Fair enough.
Context engineering is the discipline of designing everything an AI model sees before it generates a response. Not just your prompt. The system instructions. The memory. The tools. The retrieved knowledge. The dynamic assembly. Everything.
Andrej Karpathy said it best: the LLM is a CPU, the context window is RAM, and you are the operating system. You decide what gets loaded into memory for each task.
That article explained the theory. This one gives you the system. Fifteen templates you can copy, paste into ChatGPT, Claude, or Gemini, and start getting dramatically better results in the next five minutes.
No code. No API. No technical skills required. Just copy, paste, and customize the brackets.
## PART 1: IDENTITY TEMPLATES (Who the AI thinks it is)
These templates replace the first ten minutes of every AI session. Set them once. They apply to every conversation after.
Template 1: The Personal Context File
This is the single highest-impact thing you can do. It eliminates the cold start problem permanently.
Copy this into Claude’s Custom Instructions, ChatGPT’s Memory, or Gemini’s Gems:
I am [your name], [your role] at [company/context].
My audience: [who you create for — clients, readers, team, executives].
Current priorities: [list your top 2-3 active projects or goals].
Communication style: [direct/formal/casual/technical]. I value [brevity/thoroughness/data-driven reasoning].
When I say “draft,” I want a rough version I will edit. When I say “write,” I want something close to final.
Default format: [bullet points / short paragraphs / numbered lists].
If you are unsure about something, ask me before guessing. Never fabricate data.
Why it works: Every session now starts with the AI already knowing who you are, what you care about, and how you communicate. Anthropic’s own engineering team calls system instructions “the most important lever for controlling Claude’s behavior.” This is that lever.
Template 2: The Brand Voice File
This prevents the AI from sounding like a generic chatbot and makes it sound like you.
My writing voice rules:
Tone: [e.g., direct and confident, no hedging or filler phrases] Sentence length: [e.g., short. Two to four sentences per paragraph maximum] Words I use: [list 5-10 words or phrases that define your style] Words I never use: [list words you hate — e.g., “leverage,” “utilize,” “delve,” “I’d be happy to”] Formatting: [e.g., bold for emphasis, no italic, no emojis unless specified] Structure: [e.g., lead with the conclusion, then support with evidence]
Here are two examples of my actual writing for reference:
[Paste a real paragraph you wrote]
[Paste another real paragraph you wrote]
Match this voice in everything you write for me.
Why it works: Two examples of your real writing do more than a thousand words of instruction. The AI pattern-matches your actual voice instead of guessing.
Template 3: The Working Rules File
This stops the AI from doing things you hate.
Rules for every task:
Ask clarifying questions before starting complex tasks. Do not assume.
When presenting options, give me your recommendation first, then alternatives.
Never use placeholder text. Every example must be specific and real.
If a task requires current data, tell me you cannot verify it rather than fabricating numbers.
Default output length: [e.g., 300-500 words unless I specify otherwise].
When I say “shorter,” cut by 40%. When I say “longer,” expand by 50%.
[Add your own rule: something the AI keeps doing wrong that you want stopped permanently].
Why it works: Every complaint you have about AI output is a rule you have not written yet. This file turns complaints into constraints. Write the rule once and the mistake never happens again.
## PART 2: TASK TEMPLATES (How you ask)
These templates replace vague prompts with structured requests that produce first-draft quality output.
Template 4: The Research Brief
Use this before any research task to prevent surface-level summaries.
Research [topic].
Scope: [what specifically I need to know — not “everything about X”] Depth: [surface overview / detailed analysis / comprehensive deep-dive] Sources: [prioritize primary sources / academic papers / industry reports / recent news] Time frame: [only information from the last 6 months / last 2 years / all time] Output format: [bullet summary / structured report with sections / comparison table]
For each claim, include the source name and date. Flag anything you are uncertain about.
Do not include general background I already know. I know [state what you already know so the AI skips it].
Why it works: The line “Do not include general background I already know” eliminates the filler paragraphs that waste the first third of every AI research response. You are engineering the context of what should not appear.
Template 5: The Writing Brief
Use this for any content creation task.
Write [type of content: email / article / report / social post].
Audience: [who will read this and what do they care about] Goal: [what should the reader think, feel, or do after reading] Key points to include: [list the 3-5 things that must appear] Key points to exclude: [what should NOT be mentioned] Tone: [reference my brand voice file / or specify: formal, casual, provocative, empathetic] Length: [specific word count or range] Structure: [how it should be organized — sections, numbered list, narrative] Reference: [paste or describe an example of what “good” looks like for this task]
Why it works: The “Key points to exclude” field is the most underrated line. Most people tell AI what to write. Context engineers also tell it what NOT to write. Constraints produce focus. Focus produces quality.
Template 6: The Decision Framework
Use this when you need the AI to help you think, not just answer.
I need to decide between [Option A] and [Option B] (and [Option C] if applicable).
Context: [describe the situation and why this decision matters] Constraints: [budget, timeline, team size, technical limitations] My priorities: [what matters most — speed, cost, quality, risk reduction] What I am leaning toward: [your current instinct and why]
Give me: 1. A comparison table with the most important criteria 2. The strongest argument FOR each option 3. The strongest argument AGAINST each option 4. Your recommendation with specific reasoning 5. What I might be overlooking
Do not be neutral. Take a position.
Why it works: “Do not be neutral. Take a position.” is the single most powerful instruction for decision support. Without it, AI defaults to “it depends” hedging. With it, you get a clear recommendation you can argue against, which is far more useful than a balanced summary that helps no one decide anything.
## PART 3: CONTEXT CONTROL TEMPLATES (Managing what the AI knows)
These templates solve the biggest problem in AI: the model forgets, hallucinates, or loses track of your goals mid-conversation.
Template 7: The Session Kickoff
Use this at the start of any complex, multi-step session.
Before we begin, here is the context for this session:
Project: [name and one-line description] Current status: [where things stand right now] What we accomplished last session: [summary of prior work if applicable] Goal for this session: [specific deliverable or outcome] Files to reference: [list any documents, links, or prior outputs to use] Constraints: [time, word count, format, scope limitations]
Confirm you understand the full context before starting.
Why it works: This is context loading — the practice of frontloading everything the model needs before it generates a single token. LangChain’s context engineering framework calls this “selecting context.” You are pulling exactly the right information into the window at exactly the right time.
Template 8: The Anti-Hallucination Guard
Use this for any task involving facts, data, or claims.
Important rules for this task:
Only include information you can directly verify from the sources I provide or from your training data.
If you are uncertain about a specific fact, number, or date, flag it with [UNVERIFIED] next to it.
Do not invent statistics. Do not fabricate quotes. Do not create fake citations.
If I ask about something beyond your knowledge cutoff, say so explicitly instead of guessing.
Distinguish clearly between “this is a fact” and “this is my analysis.”
Why it works: The [UNVERIFIED] tag system is the simplest anti-hallucination technique that exists. Instead of hoping the AI does not make things up, you give it an explicit escape valve. The model is far less likely to fabricate when it has permission to flag uncertainty. Anthropic’s own documentation recommends this approach for high-stakes factual tasks.
Template 9: The Context Reset
Use this when a conversation has gone off track.
Stop. Let us reset this conversation.
Here is what we are actually trying to accomplish: [restate the original goal] Here is what has gone wrong: [describe what went off track] Here is what I want you to do differently now: [specific instruction]
Ignore everything above this message that contradicts these new instructions. Start fresh from this point.
Why it works: Long conversations suffer from what researchers call “context rot” — the model’s attention drifts to recent messages and loses the original instructions. Claude Code triggers an automatic “compaction” when you hit 95% of the context window, summarizing everything to stay focused. This template lets you do the same thing manually in any AI tool. A clean reset is better than ten correction messages.
## PART 4: ADVANCED TEMPLATES (Building systems, not conversations)
These templates move you from using AI as a chat tool to building AI-powered workflows.
Template 10: The CLAUDE.md / Project Rules File
For Claude Code, Cursor, or any AI coding tool. This is the context file that governs every interaction.
Project: [Name]
## Architecture
- Language: [e.g., TypeScript]
- Framework: [e.g., Next.js 15]
- Database: [e.g., PostgreSQL with Prisma ORM]
- Testing: [e.g., Vitest for unit tests, Playwright for E2E]
## Code Standards
- Use functional components. No classes.
- All functions must have explicit return types.
- Error handling: use Result types, not try-catch.
- File naming: kebab-case. One component per file.
## Workflow Rules
- Write tests before writing implementation code.
- Run all tests before marking any task as complete.
- Never modify files outside the scope of the current task.
- When uncertain about architecture decisions, ask before implementing.
## Common Mistakes to Avoid
- Do not add console.log statements in production code.
- Do not install new dependencies without explicit approval.
- Do not refactor existing code unless the task specifically requires it.
Why it works: This file loads at the start of every Claude Code session. Every instruction applies automatically to every task. Context engineering for developers means never repeating the same correction twice — you encode the correction into the rules file and it becomes permanent.
Template 11: The Multi-Step Task Planner
Use this to prevent the AI from rushing through complex tasks.
I need you to complete a complex task. Do NOT start executing immediately.
First, create a numbered plan with every step required to complete this task: - What information you need - What order to work in - What the deliverable for each step looks like - What could go wrong at each step
Present the plan for my approval before executing any step. After I approve, work through each step one at a time, confirming completion before moving to the next.
Task: [describe what you need]
Why it works: This is the Plan-Execute-Verify loop applied to any AI tool. The AI’s biggest failure mode is rushing to output without thinking. Forcing it to plan first, then wait for approval, dramatically improves the quality of complex multi-step work. This mirrors how agentic engineering workflows are designed — plan first, execute second, verify third.
Template 12: The Self-Evaluation Loop
Use this to make the AI check its own work before showing you.
After completing this task, evaluate your own output before presenting it to me.
Check against these criteria: 1. Does it fully address every requirement I listed? 2. Is anything factually questionable or unverified? 3. Is the length within the specified range? 4. Does the tone match my brand voice? 5. Are there any filler sentences that add no value? Remove them. 6. Would I be comfortable putting my name on this? If not, what needs to change?
If the output fails any check, revise it before showing me. Show me only your best version.
Why it works: This single template can cut your editing time in half. Instead of being your first draft generator and reviewer, the AI becomes its own first reviewer and shows you its second draft. Anthropic calls this pattern “chain-of-thought self-verification.” You are engineering the context to include an evaluation step before delivery.
## PART 5: WORKFLOW AUTOMATION TEMPLATES
These templates turn one-time conversations into reusable systems.
Template 13: The Weekly Briefing System
Set this as a recurring scheduled task or run it every Monday.
Generate my weekly briefing using this structure:
PRIORITY ACTIONS: What are the 3 most important things I need to act on this week? Base this on [my calendar / email / project status].
MEETINGS PREP: List my meetings for the week. For each, include: who is attending, what the meeting is about, and one thing I should prepare.
FOLLOW-UPS: List anything from last week that I said I would follow up on but has not been completed yet.
READING LIST: Summarize the 3 most relevant articles or updates in [my industry / topic area] from the past 7 days.
Keep each section concise. No longer than 5 bullet points per section. Lead with the most urgent item.
Why it works: This is context engineering applied to workflow automation. You are not writing a prompt — you are designing an information system that runs repeatedly and improves as your context files get better. The AI pulls from your connected tools (calendar, email, web) and assembles a briefing that would take you 30 minutes to compile manually.
Template 14: The Meeting Notes Processor
Use this after every meeting to extract structured value from raw notes.
Here are my raw meeting notes: [paste or upload notes]
Process these into the following structure:
DECISIONS MADE: What was decided? List each decision as a clear statement.
ACTION ITEMS: Who needs to do what, by when? Format: [Person] — [Action] — [Deadline]
OPEN QUESTIONS: What was raised but not resolved?
KEY QUOTES: Any important statements worth preserving verbatim.
NEXT STEPS: What happens next and when is the next meeting?
If any information is unclear from the notes, flag it with [UNCLEAR] rather than guessing.
Why it works: Raw meeting notes are chaos. This template applies LangChain’s “compress context” strategy — it takes a large, unstructured input and compresses it into only the tokens that matter. The [UNCLEAR] tag applies the same anti-hallucination logic from Template 8 — better to flag uncertainty than fabricate details.
Template 15: The Skill Builder
Use this to turn any repeatable task into a permanent context template.
I just completed a task that I will need to do again in the future. Help me turn it into a reusable template.
The task: [describe what you just did] What worked well: [what aspects of the output were good] What I had to fix manually: [what the AI got wrong that I corrected] What I want different next time: [improvements for the next iteration]
Create a detailed instruction template that I can save and reuse. Include: - The exact context the AI needs to know before starting - Step-by-step instructions for completing the task - Quality standards and constraints - Common mistakes to avoid (based on what I had to fix this time) - The output format and structure
Write it so that I can paste this template into any AI tool and get consistent results every time.
Why it works: This is meta context engineering — using the AI to build your own context templates. Every task you repeat becomes a template. Every template eliminates one prompt you never have to write again. LangChain calls this the “write” strategy — saving context externally so it can be loaded later. After a few weeks of building templates, your entire workflow is encoded in reusable files. The system gets smarter without the model getting smarter. That is the whole point.
The system behind the templates
Here is the mental model that ties all fifteen together.
Templates 1-3 are your identity layer. They answer: “Who am I talking to?” Set these once and the AI knows you permanently.
Templates 4-6 are your task layer. They answer: “What exactly do you need right now?” Use these for every new request.
Templates 7-9 are your control layer. They answer: “How do I keep the AI on track?” Use these when things go wrong or get complex.
Templates 10-12 are your systems layer. They answer: “How do I build workflows, not conversations?” Use these for professional and development work.
Templates 13-15 are your automation layer. They answer: “How do I make this run without me?” Use these to turn one-time work into repeatable systems.
Stack the layers. Template 1 plus Template 5 plus Template 12 means the AI knows who you are, understands exactly what you need, and checks its own work before showing you. Three templates. Ten seconds to load. Output that takes two minutes to review instead of twenty.
The people who copy one template will get better results tomorrow. The people who build the full five-layer system will get compounding results for the rest of the year.
Context engineering is not about writing better prompts. It is about building better systems.
The templates are here. The system is explained. The only thing left is to start.
## 相关链接
- [Nav Toor](https://x.com/heynavtoor)
- [@heynavtoor](https://x.com/heynavtoor)
- [25K](https://x.com/heynavtoor/status/2041572825698615583/analytics)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [1:44 AM · Apr 8, 2026](https://x.com/heynavtoor/status/2041572825698615583)
- [25.5K Views](https://x.com/heynavtoor/status/2041572825698615583/analytics)
- [View quotes](https://x.com/heynavtoor/status/2041572825698615583/quotes)
---
*导出时间: 2026/4/8 22:58:39*