nateherkai /scroll-craft
An agent skill for building premium, immersive, scroll-driven websites. Works with Codex, Claude Code, and other coding agents. Also available as a Claude Code plugin.
★ 4,833⑂ 677👁 30⑃ 6● 9▤ 0◈ 0
4,833
stars
+52
677
forks
30
watchers
6
prs
9
issues
0
releases
0
discussions
README
scroll-craft An agent skill for building premium, scroll-driven websites, with a real design standard. Use it with Codex, Claude Code, or another coding agent that can read instructions, edit files, run commands, and inspect a browser. The skill contains the design workflow, references, engine, and verification tools. It also ships as a Claude Code plugin for convenient installation. Most AI website output fails in one of two directions. It is either well behaved and forgettable, or it is a flashy scroll animation with 2.1:1 body text, a headline that wraps to six lines on a phone, and the same six sections every other AI page has. scroll-craft is built to fail neither way: it treats interaction and craft as one job rather than two. --- New in 0.3.0: the approved ten-site standard The skill now includes the process behind ten approved immersive websites: AI Automation Society, PERKFORM, Glaido, Herkules Advisory, Serein, FORME, Pelagic, NOEMA, OFFGRID, and Afterhours. See the worked examples in motion A 50-second walkthrough of several approved sites, showing their layered heroes, pointer response, and scroll transitions. https://github.com/user-attachments/assets/d193073b-5af9-45de-93ae-95bf7c6934d5 - Plan independent depth planes, contact anchors, and opening/midpoint/exit states. - Use authentic brand assets and verified product details before generating imagery. - Choose photographic compositing or real 3D rendering to suit the subject. - Give each site its own navigation, information order, useful controls, and ending. - Art-direct phones separately and verify actual scroll frames, fallbacks, and packages. - Honor explicit creative delegation without forcing a redundant interview. Read the worked examples and production workflow and the hero-depth guide. These examples describe design behavior; client assets and private form data are not bundled. The existing engine and video compatibility fixes are preserved. Three builds, three completely different pages Same skill, same engine, no shared skeleton. The differences below are not themes: they are different page grammars, different navigation models, different endings. AI Automation Society · an AI community A dark editorial landing for a 450,000-member community. One stat carries the whole promise, a live product surface rises into the frame, and the proof stacks under it as you fall down the page. !AI Automation Society, a dark editorial community landing Nate Herk · a creator portfolio High-key and bright, the opposite of the first. A lit-glass hero with the numbers up front, a portrait held in the light, and two clear next steps instead of a wall of links. !Nate Herk, a high-key lit-glass creator portfolio PERKFORM · a protein coffee A filmic one-shot that hard-cuts to two full-bleed inverted grounds mid-page. Loud, product-forward, and the only one of the three that raises its voice. !PERKFORM, a filmic one-shot product page --- What it actually does Inte
Top issues
#16Optional: publicly verifiable certificate for scroll-craft (one workflow file)0 comments · 2026-10-26#15Engine perf: perpetual rAF tick, per-frame scrollHeight reads, cues hidden until mount0 comments · 2026-10-23#14serve.mjs still serves dotfiles, so an API key kept in the build folder is readable over HTTP0 comments · 2026-10-12#11workspace.mjs: CLI silently does nothing when the skill directory is a symlink0 comments · 2026-10-02#5Request for compatibility to othe ai agent0 comments · 2026-09-01#1data-sc-kinetic is silently ignored when it sits on a child of the cued element0 comments · 2026-08-25