How to test and iterate on the ratatui TUI (`artifacts tui <character>`) by remote-controlling a zellij pane — launch it, drive keypresses, and capture screen dumps to see the actual rendered layout without a human at the keyboard. Use whenever changing code under src/tui or verifying a TUI behavior/layout claim.
Fetch the open-api specification for a specific action, endpoint, or request to the artifacts API. Use when investigating or implementing any artifacts API related interactions, rather than guessing at artifacts api.
Run all automated code quality and verification tasks. Use when done making any rust file changes.
Learn how to run a live request against the artifacts API using a test character and token/secret. Use when wanting to test something end to end, against the actual game servers.
How to write and review tests in this repo. Enforces a "few, broad, entrypoint-driven" testing standard over many narrow per-function unit tests. Use this whenever writing new tests, reviewing existing ones, deciding whether a change needs test coverage, or consolidating/pruning `#[test]` blocks. Triggers on requests like "add a test for this", "write tests for X", "is this well tested", "clean up these tests", or when a code change touches Fennel workflows, the driver/MockDriver, core game logic, or the TUI.