| name | quic-rag |
| description | Use when answering QUIC protocol or RFC questions in this repository, especially section lookups, frames, transport parameters, ACK behavior, version negotiation, packet formats, error codes, or when grounded RFC citations are needed. |
QUIC RAG
Use the repo-local QUIC specification knowledge base before answering protocol
questions in coquic.
When to Use
- QUIC RFC or Internet-Draft questions grounded in the configured Qdrant RAG index
- Requests for exact section lookups or document citations
- Questions about frames, transport parameters, packet formats, recovery, congestion control, version negotiation, or error codes
Workflow
- Check readiness:
nix run .#qdrant-dev -- status
rag/scripts/query-rag doctor --state-dir .rag
- If the shared backend is unavailable, run
nix run .#qdrant-dev -- start and retry once.
- Use the smallest fitting query:
rag/scripts/query-rag get-section --doc rfc9000 --section-id 18.2
rag/scripts/query-rag get-section --doc draft-ietf-quic-qlog-main-schema-13 --section-id 1
rag/scripts/query-rag trace-term max_udp_payload_size
rag/scripts/query-rag lookup-term --term-type transport_parameter --name max_udp_payload_size
rag/scripts/query-rag related-sections --doc rfc9369 --section-id 5
rag/scripts/query-rag search-sections "ACK frame behavior" --top-k 5
- Cite the document IDs and section IDs from command output in the final answer.
- If the index is not ready, rebuild it with an explicit source directory:
rag/scripts/build-index --source <source-dir> --state-dir .rag.
Don't Use
- Source-code implementation questions that are not asking about QUIC protocol behavior
- Non-QUIC repo workflow questions