Menú
Route production RAG rollout work across serving, scaling, index versioning, and safe reindexing.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use this skill when building, debugging, or improving Retrieval-Augmented Generation systems, including chunking, vector database selection, hybrid search, reranking, multimodal RAG, code documentation RAG, retrieval latency, and production RAG architecture.
Chunk nested documents into parent-child levels so retrieval can move from broad sections to fine-grained passages.
Use semantic boundaries and embedding similarity to chunk text for higher-relevance retrieval.
Route RAG chunking decisions across semantic, hierarchical, sliding-window, contextual-header, and framework-selection strategies.
Use overlapping windows to preserve context across chunk boundaries while controlling retrieval size.
Reduce retrieval latency with caching, batching, and index-level optimization.
| name | deployment |
| title | Deployment |
| description | Route production RAG rollout work across serving, scaling, index versioning, and safe reindexing. |
| category | deployment |
| tags | ["deployment","production","reindexing","routing"] |
| allowed-tools | ["Read","Grep","Glob"] |
Use this parent skill when the RAG system works in development but must be made reliable in production. Route to the child skill that matches whether the problem is serving and scaling the pipeline or evolving the index without downtime.
RAG systems that pass local tests still fail in production from cold indexes, unbounded latency under load, and risky full reindexes that take the search layer offline. Prototype code rarely handles versioning, rollout, or drift, so quality quietly decays after launch.
Put retrieval and generation behind an API with health checks, timeouts, and observability before scaling anything.
Treat each index build as a named, immutable artifact so you can roll forward or back by swapping a pointer.
Design embedding-model migrations and reindexing as alias swaps with a fast rollback, not as in-place rebuilds.
