rag retrieval patterns
7 articles · 15 co-occurring · 0 contradictions · 0 briefs
Retrieval is explicitly identified as a distinct layer of context engineering infrastructure
Retrieval is explicitly identified as a distinct layer of context engineering infrastructure
Article identifies MCP as evolution beyond brittle RAG pipelines—moving from ad-hoc retrieval to standardized, reusable context connectors.
Mentions RAG as context source alongside prompt/conversation history. MCP servers can implement RAG endpoints, making retrieval a composable capability.
DESIGN.md is a structured retrieval format: tokens + prose can be indexed and retrieved selectively. The export to Tailwind/W3C DTCG is a form of context adaptation for different downstream systems.
Example of 'what did I quote to X customer' directly describes need for intelligent search+parse+LLM pipeline—classic RAG architecture decision point.
Shows RAG as a step within an agent workflow rather than standalone system, demonstrating how retrieval context integrates with agentic decision-making
The monitoring approach ('Claude monitor feature usage and brainstorm improvements') suggests using past behavior as retrievable context to improve future performance
Get daily briefs + MCP graph access.
Subscribe free →