scroll-craft
Skill0 starsChanged 2 months agoMITView on GitHub
Build scroll-led storytelling websites where scroll is the timeline: scrollytelling, signature interaction, pin/pan/reveal, layered hero, cinematic scroll without camera flight. Use when the user runs /scroll-craft, or asks for a site where scrolling tells the product story. Not for ordinary dashboards or landings (impeccable), continuous camera fly-through / diorama / 3D world (scroll-world), chrome motion (emil-design-eng), or photoreal ads (visual-studio).
6 other projects use a version of this.
Adopted by
Most recently taken up by
- AhmedMerza/claude-skillstheir own version, first seen Nov 8, 2026
- AhmedMerza/agent-skillstheir own version, first seen Nov 8, 2026
- BWERepo/ClaudeSkillstheir own version, first seen Nov 1, 2026
- cadendane-droid/claude-skillstheir own version, first seen Nov 1, 2026
- kschiavo-beep/claude-skillstheir own version, first seen Oct 11, 2026
- flyingwebie/skillstheir own version, first seen Sep 9, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- flyingwebie/skills★ 9same name
- AhmedMerza/agent-skills★ 2same name
- AhmedMerza/claude-skills★ 2same name
- BWERepo/ClaudeSkills★ 0same name
- cadendane-droid/claude-skills★ 0same name
- kschiavo-beep/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository47 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- academicSkill
- adhdSkill
- agent-architecture-auditSkill
- api-designSkill
- automation-audit-opsSkill
- browser-actSkill
- chrome-devtools-axiSkill
- click-path-auditSkill
- codebase-designSkill
- code-tourSkill
- contract-firstSkill
- cost-aware-llm-pipelineSkill
- diagnosing-bugsSkill
- diagram-designSkill
- domain-modelingSkill
- emil-design-engSkill
- eval-harnessSkill
- found-this-designSkill
- full-audit-keamananSkill
- full-performance-auditSkill
- gh-axiSkill
- grill-with-docsSkill
- humanizerSkill
- hyperframesSkill
- id-demo-videoSkill
- img2threejsSkill
- impeccableSkill
- install-anti-slopSkill
- markitdownSkill
- matt-code-reviewSkill
- mongodb-opsSkill
- playwright-qaSkill
- prompt-optimizerSkill
- prototypeSkill
- researchSkill
- scroll-worldSkill
- skill-stocktakeSkill
- smartbook-ingestSkill
- smartdocSkill
- supabase-opsSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- vercel-opsSkill
- visual-studioSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Do not read every reference on every request.
- Distinctive: line 42
Follow the project stack. Do not force a standalone HTML file onto React/Vue.
- Very specific: line 45
No scroll hijacking. No wheel/touch/keyboard traps.
- Very specific: line 46
No KIE, Higgsfield, ffmpeg, Playwright, font CDN, or remote assets on the core path.
- Distinctive: line 48
Do not invent brand facts, stats, testimonials, or user quotes.
- Distinctive: line 71
Read PRODUCT.md, DESIGN.md, tokens, and existing assets.
- Distinctive: line 73
Write the visitor journey and feeling curve.
- Distinctive: line 80
Verify along the scroll: desktop, mobile portrait, reduced motion, reverse, anchor jump, keyboard.
- Distinctive: line 89
Tier 1 (default): no generation, no video. Complete experience offline.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Scroll Craft
Scroll is the timeline. The page is a story the visitor drives with their hand. One grammar, one peak, one signature move. Premium means clear composition and a meaningful interaction, not video, pinning, or effects.
Load when
| Need | File |
| Journey, feeling curve, peak | journey.md |
| Eight grammars | grammars.md |
Devices and --sc-p | devices.md |
| Signature + fingerprint | signature-fingerprint.md |
| Optional hero depth | hero-depth.md |
| Mobile, keyboard, reduced motion | mobile-accessibility.md |
| Scroll verification | verification.md |
| Continuous World / media / QA | handoff.md |
Do not read every reference on every request. Engine:
scrollcraft.js, scrollcraft.css.
The mechanism CSS is safe for an existing design system; the scoped
starter theme is optional. Copy what the project
needs; do not edit the mechanism per page. Drive bespoke behaviour from
--sc-p. Attribution: NOTICE.md.
Hard rules
- One primary specialist. This skill owns the scroll story. Do not auto-load Impeccable for every build step.
- Ordinary scrollable UI stays Impeccable. Words like
premium,cinematic,interactive, orlayeredalone are not enough. - Continuous camera / fly-through / diorama / 3D world → hand off to
scroll-worldafter a minimum brief. Do not implement worldflight here. - Follow the project stack. Do not force a standalone HTML file onto React/Vue.
- Semantic HTML for headings, CTA, nav, and forms. Core content readable with JS off and with reduced motion.
- No scroll hijacking. No wheel/touch/keyboard traps.
- No KIE, Higgsfield, ffmpeg, Playwright, font CDN, or remote assets on the core path. Tier 1 is HTML/CSS/transforms/sticky/local assets/light JS.
- Do not invent brand facts, stats, testimonials, or user quotes.
- Live Surface controls must work. Label synthetic demos. Never fake a successful transaction.
- Design V2 is optional, offline, read-only. Empty bank does not block build.
- Store brief/fingerprint/evidence under
.scratch/scroll-craft/<slug>/in the user project. Not in this skill folder. No new global home.
Handoff
| Request | Owner |
| Scroll-led storytelling / scrollytelling | this skill |
/scroll-craft plus Continuous World | this skill enters, then scroll-world |
| Continuous camera, diorama, 3D world (no slash) | scroll-world |
| Dashboard, ordinary landing, design system | impeccable |
| Hover/press/easing after the surface exists | emil-design-eng |
| Standalone photoreal / ads / identity | visual-studio |
| Deterministic HTML composition rendered to video | hyperframes |
| Exploratory QA | browser-act |
| Observed browser cause | opencode-chromium-cdp then chrome-devtools-axi |
Run
- Read PRODUCT.md, DESIGN.md, tokens, and existing assets. Reuse answers.
- Lock the brief. Interview only missing decisions. Mark assumptions.
- Write the visitor journey and feeling curve. One engineered peak.
- Pick one page grammar. grammars.md.
- Invent one domain-relevant signature interaction with a static fallback.
- Compare fingerprint if history exists; else record
NO_HISTORY. Design V2 retrieval is optional. - Assign a device per beat, with fallback. No quota of device families.
- Build in the project stack. Copy the engine if the page uses
data-sc-*. - Verify along the scroll: desktop, mobile portrait, reduced motion, reverse, anchor jump, keyboard. verification.md.
- Fix, save evidence under
.scratch/scroll-craft/<slug>/, record fingerprint.
/scroll-craft with an explicit Continuous World brief: write the story,
waypoints, and feeling curve, then hand off. Do not take the renderer.
Media
- Tier 1 (default): no generation, no video. Complete experience offline.
- Tier 2: existing local images with clear license. No ffmpeg.
- Tier 3: video only if the brief needs it and native tooling exists.
A finished non-video path is normal, not DEGRADED. Use DEGRADED only when a
requested capability cannot be met. Do not invent tools.
Output
The page (or mount into the existing site), the journey table, grammar and why
the others lost, signature move, fingerprint (NO_HISTORY or diffs), peak,
verification actually performed, and limits (emulation vs device). Do not dump
prompts or claim uniqueness without evidence.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

