mangue-dev/autokap
Screenshots produced by your agent, from a demo world it builds and cannot leave.
Equip a repository with autokap — write captures/config.mjs, adapter.mjs and scope.mjs by reading the project's own migrations, cron routes, workers and triggers, then create the demo account. Use when the user says "set up autokap", "install autokap", "/autokap init", when captures/scope.mjs is still the empty template, or when a world or shot task cannot proceed because the perimeter is not declared.
Produce, change, refresh and drop product screenshots — write captures/shots/<name>/intent.md and shot.mjs with assertions, run them, then open the PNG and judge it. Use when the user asks for a screenshot of a screen, says "/autokap <what to show>", "change this shot", "refresh", "drop <name>", or when npx autokap run comes back red and something needs repairing.
Create and maintain the demo world that screenshots are taken of — write idempotent seed files under captures/world/seed/, keep captures/world/world.md in step with them, and apply changes only through the autokap guard engine after explicit human consent. Use when a shot needs data that does not exist, when the user says "put this data here instead", "add a few more tickets", "the demo account needs X", or when a run fails on an assertion like "0 rows, expected at least 8".