A RAG setup for Odin game dev shows a lean agent workflow
A firsthand Odin game development was built and maintained with inside Kilo Code. The setup combines repeatable Python scrapers, a curated local , and a subagent that reads only selected files instead of pulling in .
The scrapers collect material from a Skool membership area, odin-lang.org , awesome-odin, and Zylinski sources found through RSS, while keeping the content on the local disk. The subagent reads INDEX.md first, chooses 2 or 3 relevant files, and cites exact file paths and line numbers.
The .kilo/skills folder contains six task tools for search, code formatting, scraper control, Odin pattern finding, daily planning, and Pyright checks. The official folder stores 11 pages from odin-lang.org/docs with , and the planning folder follows a strict day-by-day template that is not manually edited.
Key points
- and Kilo Code were used to manage an Odin game development RAG .
- The subagent reads INDEX.md first and then uses only 2 or 3 relevant files.
- Answers are designed to cite exact file paths and line numbers.
- Scrapers gather official docs, community material, RSS-discovered sources, and local membership content.
- Separate skills handle search, formatting, scraper runs, planning, pattern finding, and Pyright checks.