yuru-sha

Pyrogue — AI skill for Claude Code

AI community

Here is a sample of the AI agent's Claude Code.

How to install Pyrogue

This entry records only its repository, not the path inside it, so there is no exact command to give. Open yuru-sha/pyrogue and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Pyrogue does

Here is a sample of the AI agent's Claude Code. I created a roguelike game using Python.

Alternatives in AI

AGENTS.md - Skill Seekers — Concise reference for AI coding agents 11.1k ★
Azure OpenAI Python — Azure OpenAI with GPT-4 for Python 1.8k ★
Loushang — AI-native agent harness for coding workflows by python: multi-model LLM orchestration, stateful sessions, tool 1.3k ★

README

PyRogue

PyRogue is a small Python 3.12 roguelike inspired by Rogue 5.4. Version 0.3.0 uses a deterministic, seedable game state and a text-cell renderer for both CLI and TCOD GUI play.

Run

uv sync --locked --extra dev
uv run --locked game --cli --seed 1234
uv run --locked game --seed 1234

Omit `--seed` for an automatically generated seed. The same game version, seed, and command sequence produces the same game state.

Rules at a glance

26 floors, ordinary room-and-corridor floors, and maze floors at 7, 13, and 19.
Field of view, explored-map memory, reachable stairs, turn-based combat, and permadeath.
Rogue-style A-Z monsters, original traps, hunger, food, equipment, potions, scrolls, wands, rings, gold, and the Amulet.
The Amulet is carried back to the surface; merely reaching floor 26 does not win.
A dead game cannot be resumed. The final screen records score, deepest floor, and death cause.

Movement uses vi keys (`h`, `j`, `k`, `l`, `y`, `u`, `b`, `n`) and `.` waits. Use `?` in-game for the complete command list.

Architecture

The canonical path is deliberately small:

GameState -> DisplayCell -> CLI / GameRenderer
       ^          ^
       +-- commands / JSON save

`GameState` owns the RNG, floor state, entities, inventory, combat, hunger, visibility, and terminal status. The CLI and TCOD renderer share the same `DisplayCell` input and turn it into characters and colors. JSON saves include the version, complete state, RNG state, death/win status, and permadeath metadata; incompatible versions are rejected explicitly.