Storybook is pretty flexible if your work can render in a web browser. We recently rebuilt Chromatic's CLI and as an experiment decided to write stories to reco

Storybook is pretty flexible if your work can render in a web browser. We recently rebuilt Chromatic's CLI and as an experiment decided to write stories to record and regression test the many states the CLI can be in. We were able to use Storybook as we used a React based library to output to STDOUT. We're loving the result so far as it makes it really easy to answer questions like - "what will the user see if they have passed flag X but their workspace is in state Y and Z their build has failed to upload". You can check out the Storybook here: https://5d67dc0374b2e300209c41e7-kgfpdfjsbm.chromatic.com/?path=/story/cli-messages-errors--incompatible-options https://5d67dc0374b2e300209c41e7-kgfpdfjsbm.chromatic.com/?p... If I was building a game I'd find the component driven methodology (https://www.componentdriven.org https://www.componentdriven.org) with a component explorer like Storybook or something specific to the game dev environment ideal because of how many hard to reach key states games have that could easily break as a result of code changes somewhere else.