nateherkai/scroll-craft

Fallowbank · a landscape design-build studio

Quiet, documentary, restrained. Museum-label copy over real photography, and a close that is a line of running text rather than a button.

What it actually does

Interaction, engagement, and being unrepeatable

• Scroll is the timeline. Video scrubs frame by frame under the wheel, sections pin while their argument advances, rails pan sideways, headlines assemble line by line, the page ground shifts colour as you travel, and the pointer moves things that are not scrolling.
• Eight mutually exclusive page grammars. Filmic one-shot, chaptered editorial, live surface, continuous world, typographic poster, gallery, split stage, rhythmic cutlist. Each one forbids what the others require, so two builds cannot quietly converge.
• A required signature move. Every build invents one bespoke interaction that exists on that site alone. A recoloured spotlight does not count.
• A fingerprint gate. A new build must differ from every page you have already made on at least 4 of 6 dimensions: grammar, nav, hero, act shape, close, signature move. Fail it and you change the plan, not the record.

Craft, and how the page actually feels

• A feeling curve before any act exists. One line per act: the emotion, then what on screen causes it. Two adjacent acts with the same feeling means one is filler.
• One engineered peak. Peak-end rule, applied literally. The peak gets the asset budget, the silence in front of it, and the most scroll room. A page with three peaks has none.
• A typography floor. Two families maximum, tracking that tightens as size grows, 45 to 75ch measure, line height inverse to measure, and light-on-dark compensated on three axes.
• A spacing scale with actual rhythm. 4px base, more space above a heading than below it, fluid section padding so a phone does not inherit desktop air.
• Colour with six roles and one accent, secondary text tinted rather than flat grey, no pure black, and a documented escape for pages that hard-cut between light and dark grounds.
• Depth as five tools, not one. Offset shadows, edge light, scale-and-blur as distance, overlap, and grain.
• Brand guidelines are inputs, not decoration. Point it at a brand kit and its hard rules win, including rules that forbid things the skill would otherwise reach for.
• A refuse list. Identical feature-card grids, 01 / 06 counters, scroll cues, gradient text, em dashes, invented statistics, fake dashboards, AI-purple gradients, and the cream-and-brass artisan palette every craft brand defaults to.

It checks its own work

A headless browser walks the finished page at every scroll position, waits for the video playhead to settle, and reports:

• dead scroll: scroll that changes nothing on screen
• cues that never reach full opacity: copy the reader can only ever see faded
• contrast measured on the composited page, per line, at the brightest frame that ever passes under it, with the direction picked per line so light-on-dark and dark-on-light are both graded correctly
• legs stuck on a poster: a clip that silently never decoded, which looks exactly like a paused film

Then it writes a contact sheet, because a machine can prove a page works and cannot tell you it means anything.

Install

/plugin marketplace add nateherkai/scroll-craft

/plugin install nateherk-design

Then use it by describing what you want, or invoke it directly:

/nateherk-design:scrollcraft

If the install summary says Run /reload-plugins to activate., run that.

To hack on the skill without installing:

claude --plugin-dir ./plugins/nateherk-design

First run

node scripts/doctor.mjs              # preflight: says exactly what is missing
node scripts/workspace.mjs --ensure  # creates your workspace and an empty registry

Run doctor before anything else. The three most common setup faults all surface later as misleading errors otherwise: a stripped ffmpeg reports a missing filter as a syntax error in your command, a missing WebP muxer reports as a bad filename, and playwright-core resolves from the wrong directory.

Requirements

The workspace

Your builds and your fingerprint registry live in one directory, resolved rather than assumed. First hit wins:

1. SCROLLCRAFT_HOME
2. the nearest .scrollcraft.json walking up from the current directory: { "workspace": "path/to/builds" }
3. <project root>/scrollcraft

Builds land in <workspace>/builds/<name>/; your registry is <workspace>/FINGERPRINTS.md.

Your registry starts empty, and that is correct. The gate exists to stop you repeating yourself, so your first build has nothing to clear and every build after it does. EXAMPLES.md is the author's twelve-row table, included so you can see what a filled registry looks like and which shapes tend to collide. It is illustration, not constraint.

What is in here

plugins/nateherk-design/
└── skills/scrollcraft/
    ├── SKILL.md            the procedure: interview, grammar, score, build, verify
    ├── references/
    │   ├── uniqueness.md   eight page grammars, the signature move, the fingerprint gate
    │   ├── feel.md         the feeling curve, the engineered peak, the feel check
    │   ├── devices.md      nine scroll devices and the cue contract
    │   ├── worldflight.md  continuous-world mode: one fixed stage, no seams
    │   ├── worlds.md       art direction, and the style-preamble method
    │   ├── taste.md        the design floor: spacing, type, colour, depth, motion
    │   ├── assets.md       generation, camera moves, encoding for scrubbing
    │   ├── verify.md       the harness, and what it cannot tell you
    │   └── template.html   a starting skeleton, not a layout
    ├── engine/             scrollcraft.js + .css. The mechanism, never edited per project
    ├── templates/          the empty registry a new workspace is seeded from
    └── scripts/            doctor · workspace · kie · encode · serve · shoot · worldflight-assert

CHANGELOG.md is worth reading on its own: it records what broke on each build and the rule that came out of it, rather than a feature list.

The one rule that matters most

The engine is the mechanism and it is never edited per project. Theme it with six colour tokens and two fonts, write your own semantic HTML, and drive anything bespoke off the --sc-p custom property the engine publishes. A runtime that builds the page from a config object is exactly why every site built on one looks the same.

Honest limitations

• Only ever run on Windows. The scripts look for ffmpeg and Chrome in Windows, macOS and Linux locations, but no build has been done on a Mac. SCROLLCRAFT_FFMPEG and SCROLLCRAFT_CHROME override the search.
• Generated video is not free. A ten-leg continuous-world flight is a real spend. A page built from your own assets costs nothing.
• It is opinionated on purpose. It will refuse the layouts and palettes that make AI pages recognisable, and it will argue with you about your peak. If you want a page that looks like everything else, this is the wrong tool.

Licence

MIT. See LICENSE.