Who it is forA developer or designer who has a scroll page built and needs proof that it works in a real browser before launch.
The problemA page can look right in a screenshot but still have scroll that changes nothing, cues that never fully appear, or text that fails contrast over the moving background.
The outcomeA report that lists dead scroll, cues that never reach full opacity, contrast results per line, and stuck video legs, plus a contact sheet.
What you need first
- Node 18+
- A full ffmpeg build (scroll-craft notes that some toolchains ship a stripped ffmpeg)
- playwright-core and Chrome, installed with npm i playwright-core in the build folder
- Your own photos or footage, or a KIE_AI_API_KEY if you want assets generated
Steps
- Run
node plugins/nateherk-design/skills/scroll-craft/scripts/doctor.mjsto confirm playwright-core and Chrome are found - Run the verification script at scripts/shoot.mjs against the built page (inferred, check the README)
- Read the report for dead scroll and for cues that never reach full opacity
- Check the per-line contrast results, then open the contact sheet to judge whether the page means what it should
Prompt for your agent
Using the scroll-craft verification tools in the nateherkai/scroll-craft repo, check the built page at <page path> at every scroll position. Expected output: a report listing dead scroll, faded cues, contrast failures per line, and any video leg stuck on a poster frame, plus a contact sheet. Verify that every reported contrast failure is listed with its line of copy.
Caveat. The README states that a machine can prove a page works but cannot tell you it means anything, so the contact sheet still needs a human look.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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