Who it is forA founder or marketer using Claude Code who needs a premium, scroll-driven landing page and does not want to write the scroll mechanics by hand.
The problemAI website output is often either plain and forgettable or a flashy scroll animation with weak body text and a layout that breaks on phones.
The outcomeA built scroll-driven page in your workspace, following the skill's design standard, with the engine left unedited.
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
- In Claude Code, run
/plugin marketplace add nateherkai/scroll-craft - Run
/plugin install nateherk-design - If the install summary says Run /reload-plugins to activate., run
/reload-plugins - Run
/nateherk-design:scroll-craftand describe the site you want, including the brand, audience, and sections - Review the contact sheet the skill writes and ask for changes to any section that does not match your brief
Prompt for your agent
Using the scroll-craft skill from the nateherkai/scroll-craft repo, build a scroll-driven landing page for <target brand and product>. Follow the skill's brief, page grammar, and verification steps. Expected output: a built page in the workspace plus a contact sheet image. Verify that the verification pass reports no dead scroll and no cues stuck below full opacity.
Caveat. Scroll-craft says it has only been run on Windows, so expect to set SCROLLCRAFT_FFMPEG or SCROLLCRAFT_CHROME if your tools are installed elsewhere.
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