pyxel

# Pyxel Build the smallest complete game that satisfies the request, then verify it from observed behavior. Keep the process proportional to the task. ## Runtime Expect the `pyxel` MCP namespace from pyxel-mcp 1.2+ with Pyxel 2.9.6+ and Python 3.11+. Its eight tools are observation verbs: - `validate` reports syntax errors and recognizable code patterns. - `run` drives frames and captures state, screen images, screen grids, or video. - `pyxel_info` reports versions, examples, and resource URIs. - `read_palette`, `read_image`, `read_tilemap`, and `read_audio` inspect the corresponding Pyxel data. - `diff_frames` compares two captured PNGs. If pyxel-mcp is unavailable, register it with `uvx pyxel-mcp install`; if older than 1.2.0, update it with `uvx --refresh-package pyxel-mcp pyxel-mcp install`. While blocked, use focused logic tests plus direct Pyxel headless runs temporarily, and state that visual and interaction verification is weaker. ## Workflow 1. Infer the smallest playable scope. Ask only when a missing choice would materially change the game. 2. Implement a complete slice: entry state, controls, objective, and a retry or terminal state when the genre needs one. 3. Run `validate`; fix errors and review relevant warnings. Read `pyxel://validation-patterns` only when a category needs explanation. 4. Use `run` from frame 0 with deterministic input. Capture `state` for mechanics and `screen_image` for what the player sees. Prefer `until` with snapshots at `"end"` f...