Advanced · ~10h · 7 steps
From prompt to production RAG
Engineering-track. Assumes you can read code and deploy a Netlify function.
OutcomeA working retrieval-augmented chatbot deployed against your own docs.
Progress0/7
- Step 1
Pick a corpus + sanity-check it
60mUse Perplexity or Claude to spot-check 10 questions your corpus should answer. If they cannot answer them with the corpus pasted in, no RAG will save you.
🧠Claude - Step 2
Chunk + embed
120mCursor scaffold: a script that chunks markdown by heading, embeds with text-embedding-3-large, stores in Postgres pgvector.
⌨️Cursor - Step 3
Build the retrieval API
90mCursor: a Netlify function that takes a query, retrieves top-k chunks, and returns them as JSON. Test independently of the LLM.
⌨️Cursor - Step 4
Wire the LLM with citations
90mStream the answer with citation markers. Reject answers that have no retrieved context — fall back to "I do not know."
⌨️Cursor - Step 5
Eval set + regression test
60mUse ChatGPT to generate 50 question/answer pairs from the corpus. Score retrieval recall before you ship.
💬ChatGPT - Step 6
Ship the chat UI
90mCursor scaffold: a minimal chat UI on a /docs route. Source-of-truth citations as inline pills.
⌨️Cursor - Step 7
Instrument + iterate
90mLog every query, the retrieved chunks, and the final answer. Review weekly — most RAG bugs are retrieval bugs.
👨💻GitHub Copilot