A context seed file is written for AI, not humans. It provides everything an AI needs to understand a topic, person, product, or process — and know where to find more when needed.
Whether the seed describes a person, a software product, a cooking technique, or a company, the structure remains the same: three sections, each with a distinct purpose.
Universal Structure, Flexible Content
The same three-section structure works across all use cases:
- People & entities — background, expertise, current focus
- Topics & standards — concepts, principles, terminology
- Products & services — workflows, features, support context
- How-to guides — steps, decision points, troubleshooting
1. Attribution
The opening lines establish identity and provenance. The AI needs to know what it's looking at and how current it is.
- What — Name and purpose of this seed
- When — Creation date, last updated
- Source — Who maintains this context, authority level if relevant
Keep this minimal. A few lines, not paragraphs.
# Acme Product Support
Created: January 2025 | Updated: January 2026
Maintained by: Acme Corp Documentation Team
2. Narrative Context
This is the core. Everything the AI needs to understand the subject and handle common interactions.
Write for density and scannability:
- Structured formats (headers, bullets, labeled sections) over flowing prose
- Key concepts, terminology, boundaries
- What this covers — and explicitly what it does not
- Decision points, common patterns, known limitations
Length depends on the topic. A personal context seed may be a few hundred words. A product support seed may be longer. But every word costs tokens, so earn your space.
The narrative should handle most conversations without the AI needing to fetch additional resources.
3. Context Web
Links to related files the AI can access during the conversation, with guidance on when to use each.
Each entry includes:
- Name — What the linked resource covers
- Link — URL or file path
- When to access — The trigger condition
## Context Web
- API Reference — api.acme.com/docs — When user asks about integration or endpoints
- Troubleshooting Guide — acme.com/support/common-issues — When user reports errors or unexpected behavior
- Pricing & Plans — acme.com/pricing — When user asks about costs, limits, or plan differences
The AI reads these at conversation start and follows links as the conversation requires. This keeps the seed lean while enabling depth on demand.
Format
Markdown. Simple, universally parsed, token-efficient.
Structure it for single-shot comprehension — the AI reads it once when the conversation begins.