Built with AI4 min readBy DanManREALPublished Updated
How I built a 204-hero fan database with Claude Code
In this guide
The short version
- Godforge is made by a game studio; my hero database is an independent fan project.
- Rules beat vague requests: a fast assistant needs to know what it must not touch.
- Keep one master copy of your facts and let every page read from it.
- A check that refuses bad data is what makes speed safe.
- Write your notes down outside the assistant, so the next session can find them.
Guide

Godforge is a mythology game made by a game studio. I did not make it. I am a fan, and I built an independent, fan-made hero database for it: a place to look up every hero, compare them and plan a team.
Most of the building was done with Claude Code, an AI assistant that writes software from plain-language instructions. This is the story of how that went, including the parts that could have gone badly.
It started as a Discord bot and an experiment
The project did not begin as a tidy website. It began as a Discord bot and a playable experiment, with dozens of heroes, fast-moving ideas and very little structure. That was fine while it was a toy.
The AI assistant became truly useful when the project stopped being a toy. Once I wanted a real site that people could search and trust, I needed the same things every time: clear rules, one place for the facts and a way to check my work.
The result was a searchable hero database and a tier list, which ranked heroes by how strong they were. Both covered the first beta of Godforge, so I retired them once the game moved on, and I plan to rebuild them when Godforge launches. I also built a question-answering helper on the same hero information, which I cover in another story.
The hard part: keeping 204 heroes correct
A hero is not just a name. Each one has a faction (the group or realm they belong to), a rarity, a role, a set of stats, several abilities and a note on whether they can lead a team. Multiply that by 204 heroes across 9 factions and you have thousands of small facts that all have to agree.
Weak organization stops working at that size. So I kept one master copy of the hero information. The hero pages, the tier list and the question-answering helper all read from it. When a fact changes, I fix it once, in one place, and everything else follows.
Some ability descriptions had leftover placeholder text in them. Those needed careful cleanup, not a guess about what the text was supposed to say.
What the assistant did well
It was fast. It helped me build the pages, the search and the tier list quickly.
It worked best when it had context. With written rules and a clear job, it behaved less like a random helper and more like a careful team member who knows how this particular project works. Once that was in place, each new feature felt like a controlled job instead of a one-off request.
Where it went wrong
Speed is not the same as being correct. Left without rules, a fast assistant makes the same mistakes a rushed person would, only more quickly and with more confidence.
- It could change the wrong copy of a fact and leave the real one untouched.
- It could work from out-of-date notes without realizing they were stale.
- It could give a game fan site a generic business-dashboard look.
- It could edit the live site directly, skipping the normal safe route.
One real example came from hero health. The way health grew did not match the game's real formula. The easy fix was to make the screen look right. The correct fix was to work out the real formula and repair the data behind the screen. The assistant was quick, but the fix only counted once the data agreed with the game.
How I kept it honest
I used three habits together. None of them is clever, and that is why they work.
- Written house rules. A short page the assistant reads at the start of every session: what the project is, which information is the real one, what must not be touched and how to check work. I explain this in Keep your AI coding assistant on track.
- Checking every change. A page that looks fine in one browser tab is not proof. I check that the change did what I asked and nothing else.
- A check that refuses bad hero data. It counts the heroes, makes sure every required detail is filled in, checks that each hero's unique label is written in the right form and confirms the copy the pages show still matches the master copy.
That last check is a hard stop, not a formality. The order never changes:
- Change the master hero information.
- Run the check and read every failure it reports.
- Only when it passes do I put the site together and publish it.
What I would tell you to do
You do not need 204 heroes to use these lessons. They apply to any project where facts must stay correct, such as a recipe collection, a price list or a set of lesson notes.
- Keep one master copy of your facts and let everything else read from it.
- Write the rules down before the project gets large, while they are still easy to write.
- Give the assistant a way to be told no, with an automatic check that refuses bad data.
- Keep your notes outside the assistant, so a new session can find the decisions it needs.
Common questions
Did DanManREAL make Godforge?
No. Godforge is a mythology game made by a game studio. My hero database is an independent, fan-made project.
How did you keep 204 heroes correct?
I kept one master copy of the hero information, and the hero pages, the tier list and the question-answering helper all read from it. When a fact changes, I fix it once, in one place, and everything else follows.
Where did the AI assistant go wrong?
Left without rules, it could change the wrong copy of a fact, work from out-of-date notes, give a game fan site a generic business-dashboard look, or edit the live site directly.
Is the Godforge hero database still online?
The database and tier list covered the first beta of Godforge, so I retired them once the game moved on, and I plan to rebuild them when Godforge launches.


