All paths
⚙️

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

  1. Step 1

    Pick a corpus + sanity-check it

    60m

    Use 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
  2. Step 2

    Chunk + embed

    120m

    Cursor scaffold: a script that chunks markdown by heading, embeds with text-embedding-3-large, stores in Postgres pgvector.

    ⌨️Cursor
  3. Step 3

    Build the retrieval API

    90m

    Cursor: a Netlify function that takes a query, retrieves top-k chunks, and returns them as JSON. Test independently of the LLM.

    ⌨️Cursor
  4. Step 4

    Wire the LLM with citations

    90m

    Stream the answer with citation markers. Reject answers that have no retrieved context — fall back to "I do not know."

    ⌨️Cursor
  5. Step 5

    Eval set + regression test

    60m

    Use ChatGPT to generate 50 question/answer pairs from the corpus. Score retrieval recall before you ship.

    💬ChatGPT
  6. Step 6

    Ship the chat UI

    90m

    Cursor scaffold: a minimal chat UI on a /docs route. Source-of-truth citations as inline pills.

    ⌨️Cursor
  7. Step 7

    Instrument + iterate

    90m

    Log every query, the retrieved chunks, and the final answer. Review weekly — most RAG bugs are retrieval bugs.

    👨‍💻GitHub Copilot

More paths

GDPR · Privacy & cookies

Your data, your rules.

We use strictly necessary cookies to run this site and, with your consent, anonymous analytics to improve it. You can change your mind at any time. Read more in our Privacy notice and Cookie policy.