The Engineering of Intent, Chapter 23: Context Pack Recipes
This is Part 23 of a series walking through my book The Engineering of Intent. In the previous chapter, we watched a narrated session of a real day. Chapter 23 opens Part VIII of the book — the pattern catalog — starting with twelve ready-to-adapt Context Pack recipes.
Twelve Situations. Twelve Packs. Copy and Adapt.
Chapter 9 argued that context engineering is the highest-leverage activity in AI-native development. Chapter 23 makes the argument portable: twelve Context Pack recipes for the situations I actually build packs for, each with the target situation, the files to include, a size budget, and the most common failure mode.
The Twelve
- Greenfield — new project, first week. 3K–6K tokens. Biggest failure: over-specifying architecture before the first shippable increment tests the hypothesis.
- Legacy Monolith — 10K–15K tokens. Document the parts where work happens; accept that the dark corners stay dark. Agents stop-and-ask in unfamiliar territory.
- Migration (A to B, coexisting) — 8K–12K tokens. Explicit guardrails preventing “helpful” modernization of the old side. Agents have a bias toward modernization.
- Microservices — 5K–8K per service. Service-specific
agents.mdplus sharedconventions.md. Enforce shared with automation. - Library — 4K–8K tokens.
public-api.md+invariants.md+ correct/incorrect examples. Omit internals for API-design tasks. - Security-Sensitive — 6K–10K tokens.
threat-model.md+forbidden-patterns.md. “Be secure” is not actionable. - Frontend — 6K–10K tokens. Design-system docs + component naming + state-management rules + 3–5 reference components.
- Data Engineering — 6K–10K tokens. Schemas + pipeline map + SLAs. Omitting SLAs produces correct-but-operationally-broken pipelines.
- Debugging — 4K–8K tokens. Symptom + repro + recent changes + relevant source + pertinent traces. Exclude everything else.
- Refactor — 5K–10K tokens. Current code + concrete target (ideally an example already done elsewhere) + call-site list. “Make it cleaner” is not a target.
- Exploration — 3K–5K tokens. Problem + constraints + two or three existing solutions from other codebases. Do not ask the agent to decide.
- Onboarding — 3K–5K tokens. One-page overview + day-one tasks + core-module pointers + explicit “what to stop and ask about.”
The Pattern Underneath All Twelve
“Every recipe has a ‘what NOT to include’ section as important as the ‘what to include.’ The hardest part of Context Pack design is not what to put in. It’s what to leave out — and the recipes that perform best in practice are the ones with the most disciplined exclusions.”
Next up — Chapter 24: The Failure Mode Catalog. If Chapter 23 is the positive pattern language, Chapter 24 is the negative one — the named failure modes I’ve catalogued from advising distressed AI-native projects, and how to spot each one before it ships.
📖 Want the full picture?
The chapter gives each of the twelve recipes in full: target situation, files to include, size budget, common failure mode, and a copy-and-adapt template you can load into your repo this afternoon.
Sho Shimoda
I share and organize what I’ve learned and experienced.Categories
Tags
Search Logs
Development & Technical Consulting
Working on a new product or exploring a technical idea? We help teams with system design, architecture reviews, requirements definition, proof-of-concept development, and full implementation. Whether you need a quick technical assessment or end-to-end support, feel free to reach out.
Contact Us