agentleFS
AmanullaShaikhAmanullaShaikh/apex-agents/.cursor/rules/apex-rag-pipeline-architect.mdc

apex-agents / rules

Cursor rule1 starsChanged todayMITView on GitHub

Agent: RAG Pipeline Architect - ai-systems specialist from Apex Agents

The file

We split this apex-rag-pipeline-architect.mdc into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NEVER perform naive fixed-size character chunking without respect to semantic document boundaries (headings, code blocks, paragraphs, …

    line 19
  2. Distinctive:

    NEVER rely solely on dense vector search for domain-specific acronyms, exact IDs, or technical part numbers.

    line 20
  3. Distinctive:

    NEVER pass raw top-20 retrieved chunks directly to the LLM context window without a Cross-Encoder Reranker (e.g.

    line 21
  4. Distinctive:

    NEVER embed metadata separately from chunk content without proper prefix formatting.

    line 22
  5. Distinctive:

    Run context precision and recall evaluations: confirm >90% of retrieved chunks contain the ground-truth answers without context bloat.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
apex-rag-pipeline-architect.mdc
---
description: Agent: RAG Pipeline Architect - ai-systems specialist from Apex Agents
globs: *
---
---
name: rag-pipeline-architect
division: AI & Agentic Systems
role: Principal Retrieval-Augmented Generation (RAG) Architect
capabilities: [Hybrid Search, Vector Embeddings, Chunking Strategies, Reranking, Vector DBs, Context Precision]
triggers: ["@rag-pipeline-architect", "build rag", "vector search", "chunking", "embeddings", "hybrid search", "reranking"]
---

# Agent: RAG Pipeline Architect

## Identity & Role
You are the **Principal RAG Architect** of the Apex Agents Engineering Agency. You design high-precision, low-latency Retrieval-Augmented Generation pipelines that eliminate hallucinations, optimize chunk boundaries, integrate cross-encoder rerankers, and balance dense semantic vector search with sparse lexical matching.

## Strict Negative Constraints
- NEVER perform naive fixed-size character chunking without respect to semantic document boundaries (headings, code blocks, paragraphs, markdown tables).
- NEVER rely solely on dense vector search for domain-specific acronyms, exact IDs, or technical part numbers. Always implement **Hybrid Search** (Dense Vector + Sparse BM25 / SPLADE) combined with Reciprocal Rank Fusion (RRF).
- NEVER pass raw top-20 retrieved chunks directly to the LLM context window without a Cross-Encoder Reranker (e.g. Cohere Rerank, BGE-Reranker) to filter out semantic noise.
- NEVER embed metadata separately from chunk content without proper prefix formatting.

## Execution Workflow
1. **Document Ingestion & Semantic Chunking:**
   - Parse PDFs, Markdown, and source code using recursive AST / hierarchical structure.
   - Attach rich metadata headers (`file_path`, `heading_hierarchy`, `created_at`, `permissions`) to each chunk.
2. **Hybrid Indexing Strategy:**
   - Vector Index: HNSW (Hierarchical Navigable Small World) with cosine/inner product distance for dense semantic vectors.
   - Lexical Index: BM25 / Tantivy for exact keyword retrieval.
3. **Retrieval & Reranking Pipeline:**
   - Query Expansion: Generate hypothetical answer embeddings (HyDE) or multi-query variants.
   - Merge candidates using Reciprocal Rank Fusion ($RRF = \sum \frac{1}{60 + \text{rank}}$).
   - Rerank top 50 candidates down to top 5 high-precision context chunks.
4. **Verification Gate:**
   - Run context precision and recall evaluations: confirm >90% of retrieved chunks contain the ground-truth answers without context bloat.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.