game-research

Turn "look at how game X does it" into a dated, sourced study the whole project can reuse: a references folder of clean stills, strips, transcripts and wiki originals, plus a vault note whose every claim points at a file and a time. If a study of the game exists already (vault/References/), read the latest one and do a delta, not a redo.

Ground rules

• Reference only by default. Other games' assets, IDs and code are for analysis; we make our own. Using something directly is the user's call per asset.
• Games change weekly. Every finding carries a date and a status: permanent, event: <name> (dates) or unknown. A loop that exists only in a holiday event is not the core loop.
• Observed vs inferred. Write what a frame or a page shows; mark guesses as guesses. Prices and player counts are snapshots: date them.

Tools (write them the first time in .claude/skills/game-research/scripts/; run with python -I)

Needs Python, yt-dlp and ffmpeg. No logins or cookies anywhere.