About Boss Fight Atlas
Boss Fight Atlas is an interactive pattern library that helps game designers turn boss mechanics into readable, tunable, and testable systems.
How it started
Boss Fight Atlas began while I was building one of my first games. At the time, I had about a month of game-development experience and had vibe-coded most of the project. The prototype was taking shape, but the same approach broke down at the bosses: I could not give an agent a useful brief because I could not yet name the mechanics, pacing, and constraints I wanted.
I needed a practical thesaurus of familiar boss mechanics: patterns that had already worked in excellent games and could help me describe an encounter precisely. I first asked a model for an illustrated list, then shaped it into a catalog I could use without friction. That became this public atlas. Its current catalog contains 124 mechanics, with detailed material added as each one is developed.
I opened the project early so other developers and game designers could use it, while contributors could improve the code, design material, and translations. It is available in 8 languages. Because it began as part of my own game-development education, the material should not be treated as final authority: professional review is especially valuable, and feedback helps even without a pull request.
From a vague request to an agent-ready brief
While building the atlas, I realized I wanted to throw mechanics into a basket, export a structured brief, and give it to an agent to prototype a boss. That workflow became the Boss Builder.
Make a memorable gatekeeper boss with several phases. Keep it difficult but fair.
{
"name": "Gatekeeper",
"phases": [
{
"goal": "teach-sideways-escape",
"mechanics": [
"charge",
"ground-slam"
]
},
{
"goal": "combine-space-and-timing",
"mechanics": [
"arc-sweep",
"gap-volley"
]
}
]
}What I found first
Before building the atlas I looked for an existing resource. Game Mechanics and SteamMaho are broad databases covering games as a whole, while Jenova offers a dedicated AI boss-fight generator. None matched the narrow, inspectable mechanics workflow I wanted; together they also suggest that the problem is real and worth exploring.
How the atlas is made
Research before taxonomy
The catalogue starts from observed mechanics and cited sources. Categories are working navigation, not a claim that every game follows one universal taxonomy.
Rules you can interact with
Animations and the Boss Builder turn written ideas into behavior you can inspect, combine, and test.
Translation and review
Versions in 8 languages share the same content contract. Automated checks protect structure; factual, design, and language accuracy still require independent human review.
Open by default
Original text and illustrations are published under CC BY 4.0, and implementation code under MIT, so the work can be studied, cited, and improved.
We use Cloudflare Web Analytics to count page views and measure site performance. It does not use cookies or build individual visitor profiles.
About the creator
I am Igor Polyakov, a software engineering manager and product-minded engineer. I build systems that connect research, product decisions, and disciplined delivery.