ScreenReel

Chapter 2 · Maintain

It refuses to rot.

Here’s where every other demo dies: three sprints later, a button gets renamed, and nobody finds out until a prospect is watching. ScreenReel drives the live app — so instead of hiding from change, it detects and repairs it.

📖 Read the doctor + CI guide →

The doctor, on a real break

This is genuine output — a selector renamed out from under a flow, re-matched by the fingerprint Studio stamped when the target was picked:

$ screenreel flow doctor --flow demo.json --base-url http://localhost:3000 --fix ✖ tour-opening action 2 selector matches multiple elements repair .flow-row → [data-flow-step="1"] confidence 100 ▲ tour-controls action 5 has no matches (follows a state-mutating action — dry-run warning, not repaired) 1 fix applied — re-run: ok: true

And in CI, before anyone presents

Every PR validates the flows against the running app. A break shows up as an inline annotation on the PR that caused it — “flow guided-tour scene tour-kpis action 2: selector has no matches” — instead of a surprise mid-call.

- run: npm ci - name: Start my app run: npm run dev & npx wait-on http://localhost:3000 - uses: Alafazam/screenreels/.github/actions/validate-flows@main with: flow: demos/sales-demo.json base-url: http://localhost:3000