spelunkai/README.md
Jonas 65155ce22e Scaffold monorepo structure for all pipeline components
Add top-level README, .gitignore, and per-component directories
(recording, labeling backend/frontend, training, inference, control)
with READMEs and pyproject.toml/package skeletons per CLAUDE.md §2-3.
No implementation yet, just structure to build against.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-16 07:16:55 +02:00

28 lines
1.3 KiB
Markdown

# SpelunkAI
A multi-stage AI system that learns to play *Spelunky Classic HD*: trained perception
models, deterministic HUD-state classifiers, and a control agent that first imitates
human play (behavior cloning) and later learns autonomously (reinforcement learning).
Full project spec, architecture, timing constraints, and roadmap live in
[`CLAUDE.md`](./CLAUDE.md) — that document is the source of truth. This README is just
a map of the repo.
## Layout
| Directory | Component | Spec section |
|---|---|---|
| [`recording/`](./recording) | Recording Tool — captures gameplay video + input log on the recording PC | 3.1 |
| [`labeling/`](./labeling) | Web-Based Labeling Tool — backend + frontend for bounding-box labeling | 3.2 |
| [`training/`](./training) | Per-set training pipeline for the anchor-free CNN detectors | 3.3 |
| [`inference/`](./inference) | Runtime inference loop — capture → detectors → HUD classifiers → state vector, within the 66ms/tick budget | 3.4, 3.5 |
| [`control/`](./control) | Control Agent — behavior cloning now, RL later | 3.6 |
Each component directory has its own README with more detail and its own `.venv`
(per `CLAUDE.md` §6), since components run on different machines (recording PC vs.
`jai`) and have independent dependencies.
## Status
Repo scaffold only — no components are implemented yet.