mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
Renn F
f1b197def0
The conventions standard is dev-first by design — the developer receives the architecture map + per-task constraints at spawn and owns conforming code from the start; QA and the PR reviewer are the downstream net. Make that explicit in the developer prompt and add a dedicated conventions section to the RAG developer doc (it previously only mentioned the gate, reactively). Also reconcile the docs with the hardened behavior: env-reference now shows the flag is off by config default but on in the compose orchestrator block (left off in the registry), mirroring toolchain matching; and the RAG standard's example comment no longer implies a misplaced helper blocks (it warns).
RAG Knowledge Base Documentation
Optimized documentation for the RoboCo AI agent knowledge base. Each file is sized for effective RAG chunking.
Structure
docs/rag/
├── roles/ # Agent role responsibilities
├── workflows/ # Step-by-step task flows
├── standards/ # Coding, security, testing rules
├── architecture/ # System components
├── tools/ # MCP tools reference
└── troubleshooting/ # Common issues and fixes
Organization Principles
- One topic per file - Each file covers a single concept
- Chunk-friendly - Content fits in 512-1536 token chunks
- Self-contained - Each file provides complete context
- Actionable - Focus on what agents need to DO
For Agents
When searching the knowledge base:
- Use
roboco_kb_search()for semantic search - Use
roboco_rag_query()for AI-synthesized answers - Use
roboco_ask_mentor()for conversational help
See docs/rag/tools/kb-tools.md for the full KB tool reference.