Combining Multiple Contexts
Integrating diverse sources
Context Sources
📄 Documents
Manuals, policies, specifications
💬 History
Previous Conversations, Preferences
🔧 Tools Output
API and database results
👤 User Profile
User data, permissions
Pattern: Context Merging
=== MERGED CONTEXT ===
[SOURCE: system_prompt] Priority: 1
You are a support assistant...
[SOURCE: knowledge_base] Priority: 2
Refund policy: up to 30 days...
[SOURCE: user_profile] Priority: 3
Customer: Premium | History: 5 purchases...
[SOURCE: conversation] Priority: 4
Last message: "I want to return..."
Task-Based Skills Orchestration
Smart selection and combination
Skill Router Pattern
Context-Based, Not Code-Based Flows
Declarative vs. imperative
❌ Imperative (Code)
check_policy()
validate_user()
process_refund()
✅ Declarative (Context)
Skills: policy_checker, validator
Rules: premium_gets_priority
Output: decision + reasoning
Instruction Conflicts and Resolution
When skills disagree
Resolution Strategies
The highest-priority skill wins
More specific instruction takes precedence
Explicit marking: [OVERRIDE: skill_x]
Context-Based Chains
No-code pipelines
Context Chain Pattern
Real-World Technical Cases
Production implementations
🛒 E-commerce Bot
Skills: product_search, order_tracker, refund_processor, upseller
💻 Code Assistant
Skills: code_generator, reviewer, debugger, documenter, test_writer
📚 Research Agent
Skills: web_searcher, summarizer, fact_checker, citation_generator
📊 Data Analyst
Skills: sql_generator, visualizer, insight_extractor, report_builder