context-builderlisted

# Context Builder ## Overview Create a shared vocabulary between you and the agent. Once built, the agent speaks YOUR language — concise, precise, domain-native. ## The Problem This Solves Without shared context: - Agent uses 20 words where your domain has 1 term - Variables named generically ("data", "handler", "service") instead of domain terms - Every session starts from scratch explaining the same concepts - Conversations are verbose because the agent doesn't know your jargon With CONTEXT.md: - Agent speaks your domain language natively - "the materialization cascade" replaces "when a lesson inside a section of a course is made real" - Code uses domain terms for variables, functions, modules - Sessions start with shared understanding already loaded ## Process ### 1. Interview (grill the user) Ask these questions ONE AT A TIME: 1. "What is this project? One sentence." 2. "What are the 3-5 most important CONCEPTS in this domain?" 3. For each concept: "Define it in one sentence. What terms should I AVOID using for this?" 4. "Are there relationships between these concepts? (X contains many Y, Y belongs to one X)" 5. "Any terms that were previously confusing or ambiguous? What did you resolve them to?" 6. "What actions/verbs are specific to this domain?" (e.g., "materialize", "triage", "hydrate") ### 2. Generate CONTEXT.md Write to the project root: ```markdown # [Project Name] [One-sentence description] ## Language **[Term 1]**: [Definition in one sentence] _Av