Codex WorldForge TUI Development for Testable Terminal Reports
Maintain WorldForge showcase panes while keeping report data and Rich rendering testable independently of Textual. The skill covers focused tests and intentional screenshot updates.
中文Install in Codex
Codex with a pinned WorldForge checkout and an environment that can run the project's Python tests.
- Copy the entire pinned `.codex/skills/tui-development/` directory to `.agents/skills/tui-development/` in the target checkout.
- Open Codex in that checkout and invoke `$tui-development` with the example task and desired output.
Example task
Invoke `$tui-development` to add a completion message to a local example report. Ask for a deterministic renderer test followed by an import check for the ordinary CLI.What to check
The renderer test asserts the new message, and the base CLI imports without Textual. Any screenshot update corresponds to a verified change.
Original SKILL.md on GitHub · Updated
Frequently asked question
Why test the renderer first?
Deterministic fixtures exercise report content directly. The Textual-specific checks can then focus on layout and interaction.