A case study building a system with BALIA OS that automatically keeps a community reference site up to date, for anything with regular official updates — games, products, sports teams, and more. It automates everything from periodically checking official patch notes, reflecting the differences on the site, and notifying Discord when it updates.
"Information that's safe to auto-update" and "information that needs a human touch or community verification" are clearly separated during the initial interview stage. That's because for content that was just added, community strategy information itself may simply not exist yet.
| Tool | Role | Think of it as |
|---|---|---|
| Chat Claude (claude.ai) | Decides "what to build" through conversation. Handles the design/spec side | A planning session with your architect |
| Claude Code in VS Code | Takes the finalized design and actually creates the files and writes the code | The contractor on site |
Before you start building, sort information about your topic into these two categories. This sorting has a major effect on the design decisions that follow — what to automate versus what to fill in manually.
Always research existing wikis first. Check whether an established wiki or strategy site already exists for your topic — if it's sparse, there's room to add value; if it's already thorough, look for a different angle. This way you design your own structure instead of just cloning an existing site.
| Phase | Content | Tool Used | Deliverable |
|---|---|---|---|
| Phase 0 | Requirements interview (topic, information sources, update frequency, scope of automation) | Chat Claude | Requirements sheet |
| Phase 1 | Deciding the system architecture (retrieval method, storage, whether to notify, publishing method) | Chat Claude | Architecture plan |
| Phase 2 | Building the cassette (SKILL.md/WORKFLOW.md and a dedicated SPEC/soul.md are all required) | Chat Claude | SKILL.md, WORKFLOW.md, SPEC/soul.md |
| Phase 3 | Implementation (iterative) | Claude Code in VS Code | A working cassette |
| Phase 4 | Testing and verification | Both | A verified cassette |
| Phase 5 | Polish and documentation | Chat Claude | Finished product + usage guide |
Since how official information is published varies a lot by topic, there's no ready-made TASK.md that skips the interview. Always start with the Phase 0 requirements interview.
Just paste this prompt as-is into a new conversation with "Chat Claude" (claude.ai) to kick off the Phase 0 requirements interview.
The rest is available in the full guide after purchasing T1.
(Full text including details on telling your sources apart, how to research existing wikis, and the Claude Code prompt for starting from a template)
What this cassette builds is strictly an unofficial fan/community resource. It summarizes and organizes content from the official source — it's not a substitute for the official source itself. Every page it creates must clearly state that it's an unofficial reference and cite its data sources. For items where official information can't be confirmed, don't force it — design the system to honestly mark them "unconfirmed — community input welcome."
How to tell your sources apart, the specific process for researching existing wikis, the Claude Code prompt for starting from a template, and more — the full write-up is all laid out on the BALIA OS guide site.
See the Full Build Guide →Other case studies built the same way — reservation management systems, boat race prediction, crypto trading, and more — are live or in progress.
See All Case Studies →