Skip to content

Roguelike / RPG

Traditional Turn-Based Roguelike, Built to Be Remixed

Tested with Claude · produced Minimal Rogue

The Prompt

Build a traditional turn-based roguelike as ONE self-contained HTML file (inline CSS/JS, no libraries, no external assets).

Core rules:
- Grid-based dungeon with procedural floors, permadeath, monsters that move only when you move, items, stairs and a single dungeon goal.
- Controls: arrow keys move and attack by bumping, Space defends, X opens the menu or cancels, Enter confirms. Autosave when changing floors; Continue resumes at the start of the reached floor.
- Display: readable retro look, either ASCII glyphs or minimal inline-SVG tiles, high contrast, no external fonts or images. It must stay legible at phone width.
- Difficulty: the early floors are survivable with patience, the deep floors are not. Every monster and item must have a clearly stated effect in the in-game help.
Architecture:
- Separate rules from rendering: a pure `step(state, action)` function returns the next state and a list of events; the renderer only draws state. This must be testable headlessly.
- Seeded generation so a run can be reproduced from its seed.
- Data-driven content: monsters and items as plain objects with stats and tags, not hard-coded branches.
Testing and balance:
- Build a random-play bot that runs 1,000 games and reports: average floor reached, death floor distribution, items never picked up, monsters never killed, and any floor that can generate without an exit.
- Fix what the report exposes, then print the before/after table.
Licensing:
- Add an MIT license header and keep the source readable enough that another person can feed it to an AI and remix it.

After the code, print the content tables and the bot report.

What This Prompt Produces

A pure step function plus a random-play bot is the difference between a roguelike that works and one that generates unwinnable floors. Minimal Rogue on this site was built this way and published under the MIT license so anyone can remix it.

Modification Tips

  • Keep the rules engine separate from the renderer from the first commit.
  • Never let a generated floor lack an exit — the bot should catch it, not a player.
  • Seeded runs make bug reports reproducible; always show the seed.
  • Publish the source if you want the game to outlive the first build; remixing is the point.

The Game This Prompt Produced

Want to try it? Open Claude, paste the prompt, and you'll have a playable game in minutes. When you're happy with the result, submit it to Daily AI Games.