DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to save one PNG per deck stop for a visual review with Awesome HTML Scrolline Deck

Capture each stop of a deck as a PNG so a team can review every frame without scrolling.

  • Content
  • Beginner
  • 30 minutes
  • From the README
  • Any agent

Who it is forA design or content reviewer who needs to check every stop of a deck before it is signed off or printed as a handout.

The problemReviewing a scroll-driven deck means scrolling through it by hand, and a missed stop can hide a layout error.

The outcomeOne PNG per stop in out/capture/<deck-id>/ that the reviewer can check in any image viewer.

What you need first

  • Node.js 22 or newer
  • git
  • ffmpeg, only if you cut frame sequences for scrubbed video
  • A Pexels or Pixabay API key in .env, only if you add stock video

Steps

  1. git clone https://github.com/gongnyang/awesome-html-scrolline-deck.git
  2. cd awesome-html-scrolline-deck
  3. git checkout v2
  4. npm install
  5. npm run capture -- rail-ai-decade --stops

Prompt for your agent

In the awesome-html-scrolline-deck repo on branch v2, run `npm run capture -- <deck-id> --stops` and list the PNG files written to out/capture/<deck-id>/. Verify that the number of PNG files equals the number of stops that `npm run deck -- plan <deck-id>` reports.

Caveat. The capture command is documented only with the --stops flag, so this flow covers stop images and not other capture modes.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page