What problem does it solve? Demo recordings fail when the app shows empty tables, dev banners, placeholder data, or timestamps that change between takes. This Skill gets a project into a demo-worthy, reproducible state before any capture begins, so every take looks identical and the app appears genuinely used. ## Core Features & Use Cases - Deterministic state control: Freezes clocks, fixes random values, hides dev-only UI, and suppresses toasts and third-party widgets so re-recorded sections match their neighbours. - Realistic data seeding: Guides seeding through the project's own seed scripts, the app's API, or direct database inserts, with domain-shaped names, realistic magnitudes, and time-relative dates anchored to a frozen instant. - Auth and reset handling: Sets up seeded demo accounts, injected session state, or dev bypass flags, plus idempotent reset scripts for sections that mutate data. - Use Case: Before recording a product walkthrough, you boot the app, seed 200 plausible invoices dated relative to a frozen "now", inject a demo session, hide the Intercom widget, and verify two dry runs produce identical screenshots. ## Quick Start Prepare my app for demo recording by seeding realistic data, freezing the clock, and hiding all dev-only UI before capture.
