scrolline-deck
발표 브리프를 스크롤로 진행하는 발표 덱(Scrolline v2)으로 만든다. 무대 1개·연속 timeline 1개·handoff move·컨셉 6종(rail·data·launch·zoom·canvas·kinetic)별 움직임 문법. deck.yaml 작성 → node plan 확인 → 브라우저 smoke → HyperFrames MP4 내보내기까지. 트리거 — "스크롤 덱 만들어", "스크롤 발표", "스크롤텔링 덱", "스크롤로 넘어가는 발표자료", "연표 덱", "데이터 스토리 덱", "제품 발표 스크롤", "줌 드릴다운 발표", "덱을 MP4로", "scrolline", "scrolline deck", "scroll deck", "scrollytelling deck", "scroll-driven presentation", "export deck to mp4". 후속 — "이 beat만 move 바꿔", "정지점 추가", "홀드 길게", "컨셉 바꿔서", "smoke 다시", "MP4 다시 뽑아" 도 이 스킬. ※ 이산 슬라이드·발표자 노트 중심이면 slideshow, 덱과 무관한 영상 제작이면 hyperframes 소관.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
Its scripts were only partly scanned.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/gongnyang/awesome-html-scrolline-deck with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/gongnyang/awesome-html-scrolline-deck'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/gongnyang--awesome-html-scrolline-deck)HTML
<a href="/listings/gongnyang--awesome-html-scrolline-deck"><img src="/api/listings/gongnyang--awesome-html-scrolline-deck/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Requires Node.js 22 or newer. ffmpeg is needed only to cut frame sequences, and the HyperFrames CLI (fetched by `npx`) only to export MP4.
git clone https://github.com/gongnyang/awesome-html-scrolline-deck.git cd awesome-html-scrolline-deck git checkout v2 npm install npm run dev
Open `http://localhost:5173/decks/rail-ai-decade/` and scroll, or press <kbd>→</kbd>.
Start your own deck from a concept:
npm run deck -- new my-review --concept data # decks/my-review/{deck.yaml,index.html,main.js,assets/}
# write beats in decks/my-review/deck.yaml
npm run deck -- plan my-review # stops and timings, computed in node
npm run export -- my-review # out/export/my-review.mp4The full walkthrough is in [docs/getting-started.md](docs/getting-started.md), and every `deck.yaml` field is in [docs/writing-a-deck.md](docs/writing-a-deck.md).
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 113 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- ---
- name: scrolline-deck
- description: 발표 브리프를 스크롤로 진행하는 발표 덱(Scrolline v2)으로 만든다. 무대 1개·연속 timeline 1개·handoff move·컨셉 6종(rail·data·launch·zoom·canvas·kinetic)별 움직임 문법. deck.yaml 작성 → node plan 확인 → 브라우저 smoke → HyperFrames MP4 내보내기까지. 트리거 — "스크롤 덱 만들어", "스크롤 발표", "스크롤텔링 덱", "스크롤로 넘어가는 발표자료", "연표 덱", "데이터 스토리 덱", "제품 발표 스크롤", "줌 드릴다운 발표", "덱을 MP4로", "scrolline", "scrolline deck", "scroll deck", "scrollytelling deck", "scroll-driven presentation", "export deck to mp4". 후속 — "이 beat만 move 바꿔", "정지점 추가", "홀드 길게", "컨셉 바꿔서", "smoke 다시", "MP4 다시 뽑아" 도 이 스킬. ※ 이산 슬라이드·발표자 노트 중심이면 slideshow, 덱과 무관한 영상 제작이면 hyperframes 소관.
- ---
- # scrolline-deck — 스크롤 발표 덱 (v2)
- - 산출물: `decks/<id>/` 덱 1개(브라우저 발표용) + `out/export/<id>.mp4`(선택)
- - 작업 위치: 이 SKILL.md가 있는 레포 루트. 다른 폴더에서 호출되면 레포 루트로 이동 후 진행(`cd ~/.claude/skills/scrolline-deck` 등). 모든 명령은 레포 루트 기준
- - 정본: `plan/CONTRACTS.md`(인터페이스), 사용 문서 `docs/*.md`. 이 파일과 문서가 다르면 CONTRACTS가 우선
- ## 원칙
- 1. **내용은 beat, 움직임은 move**: `deck.yaml`에는 내용과 move 이름·params만. 덱을 위해 engine·moves 코드를 고치지 않는다. 덱 고유 장면이 꼭 필요하면 `decks/<id>/sequences/<use>.js`(`type: sequence`)
- 2. **컨셉 문법 준수**: 컨셉 `moves.allow` 밖 move는 쓰지 않는다(불가피하면 `override: "<사유>"`). 컨셉 `moves.signature` move는 덱에서 1회 이상 사용
- 3. **컷 대신 handoff**: 이어지는 두 beat가 같은 대상(숫자·막대·사건·글자)을 다루면 `link` move로 잇는다. link가 B를 다 그리면 B의 `enter`는 `engine:none`
- 4. **수치 날조 금지**: 실데이터 덱(`sample: false`)은 number·chart·quote·photo·값 있는 compare마다 `source` 필수, `sources[]`에 url·확인일. 가상 회사면 `sample: true`(화면에 「표본」 표기)
- 5. **한 정지점 = 한 주장**: 정지점마다 초점 1개, 글자 위계 3단(결론·보충·출처) 이내. 메타 캡션(「25초」「녹화」 등) 금지
- 6. **3D는 카메라만**: 설명용 3D 오브젝트 금지. 깊이·기울기는 camera family move와 `data-depth` 층으로만
- ## 절차
- ### 1. 브리프 정리
- - 확인 항목: 주제, 청중, 발표 길이, 결론 1문장, 보유 자료(수치·출처·영상·사진), 실데이터/표본 여부, 언어(ko|en)
- - 정지점 수 기준: 발표 1분당 정지점 1~2개
- - 출처 없는 수치는 사용자에게 출처를 받거나 표본으로 전환. 임의 수치 생성 금지
- ### 2. 컨셉 선택
- | 이야기 구조 | 컨셉 | signature move |
- |---|---|---|
- | 시간 순서로 사건이 이어짐(연혁·로드맵) | `rail` | `rail-advance` `era-shift` `counter-handoff` |
- | 수치·차트가 변하며 주장을 쌓음(실적·시장 분석) | `data` | `dot-multiply` `mark-morph` `annotation-pin` |
- | 제품 하나를 공개(신제품·신기능) | `launch` | `lit-from-dark` `sticky-scrub-link` `number-slam` |
- | 전체에서 원인 하나로 파고듦(진단·TAM-SAM-SOM) | `zoom` | `zoom-dive` `zoom-surface` `depth-ladder` |
- | 여러 영역을 지도 위에서 순회(피치덱·전략 지도) | `canvas` | `arc-flight` `establish-crane` `atlas-pullback` |
- | 문장이 무대(강의·키노트·선언) | `kinetic` | `word-door` `slot-pick` `phrase-fold` |
- - 허용 beat type·move·기본값: `concepts/<id>/concept.json`. 참고 덱: 컨셉마다 `decks/` 예제 1편
- - 사용자에게 컨셉과 beat 목록(id·type·한 줄 내용·정지점)을 표로 보여 주고 합의 후 작성
- ### 3. 덱 생성·작성
- ```bash
- npm run deck -- new <deckId> --concept <concept>
- npm run deck -- moves --family <family> --role <role> # 쓸 수 있는 move 목록
- ```
- - `decks/<deckId>/main.js`의 `boot({...})`에 `mode: import.meta.env.SCROLLINE_MODE`가 있는지 확인(없으면 추가. MP4 내보내기 필수 조건)
- - `deck.yaml` 필드: `docs/writing-a-deck.md`. beat type별 필수 필드·part: CONTRACTS C4
- - move params: 해당 `moves/<family>/<id>.js`의 `params`(doc·min·max). 범위 밖 값은 검증 실패
- - 같은 move를 같은 role로 2회 이상 쓰면 `repeat: intended`(의도된 리듬일 때만)
- - 영상: 스크럽 = `npm run frames -- <in.mp4> decks/<id>/assets/frames/<name>` 후 `mode: scrub` + `frames`. 재생 = `mode: play|loop`. 스톡은 라이선스와 출처를 `decks/<id>/assets/CREDITS.md`에 기록(`docs/media.md`)
- ### 4. 정지점 확인(node)
- ```bash
- npm run deck -- plan <deckId>
- ```
- - 확인: 정지점 순서·간격, 빈 구간 없음, step 정지점(`<beat>/<step>`) 위치
- - 정지점 간격이 너무 짧으면 `hold`·move `duration`, 너무 길면 `timing.unit`·`overlap` 조정
- ### 5. 브라우저 smoke
- ```bash
- npm run dev -- --port 5190 # 별도 터미널
- node tools/smoke.mjs <deckId> --driver chrome --shots
- ```
- - 결과: `out/smoke/<deckId>/report.json`, `stop-XX.png`, `sheet.png`
- - 통과 기준: errors 0, empty 0, overlaps 0, clipped 0, tiny 0
- - `sheet.png`를 직접 열어 정지점마다 원칙 5(초점 1개·위계·메타 캡션) 판정
- ### 6. MP4 내보내기(요청 시)
- ```bash
- npm run export -- <deckId> --dry-run # 길이·발표 경로 확인
- npm run export -- <deckId> # out/export/<deckId>.mp4
- npm run capture -- <deckId> --stops # 정지점 PNG, out/capture/<deckId>/
- ```
- - 정지점별 머무는 시간: beat `exportHold`(초), 기본 1.6초
- - 배경 음악·이어 붙이기는 ffmpeg 후처리(도구 범위 밖)
- ## 게이트(전부 통과해야 완료 보고)
- | 게이트 | 확인 방법 | 기준 |
- |---|---|---|
- | 스키마·내용 감사 | 브라우저 로드(boot의 validateDeck) 또는 `npm test`(덱 `deck.test.js`가 있을 때) | 오류 0. 자리표(`TODO`·`TBD`·`lorem`·`???`·`{{`·`자리표` 등)·빈 문자열·출처 누락·허용 밖 move 차단 |
- | 정지점 | `npm run deck -- plan <deckId>` | 계획한 정지점이 순서대로 존재 |
- | 브라우저 | `node tools/smoke.mjs <deckId> --driver chrome --shots` | errors·empty·overlaps·clipped·tiny 전부 0 |
- | 컨셉 문법 | `deck.yaml` 대조 | signature move 1회 이상, 같은 move 반복은 `repeat: intended`만 |
- | 저장소 | `npm run ci` | 녹색(엔진·move·덱 테스트 + 의존·테스트 존재·state·move 정적 규칙) |
- | 화면 판정 | smoke `sheet.png` 육안 | 정지점마다 초점 1개, 위계 3단 이내, 메타 캡션·장식 3D 없음 |
- | 내보내기(요청 시) | `npm run export -- <deckId>` | exit 0, `out/export/<deckId>.mp4` 생성 |
- ## 금지
- - 덱 하나를 위해 `engine/`·`moves/`·`concepts/` 수정(필요하면 별도 작업으로 분리, `docs/moves.md`·`docs/concepts.md` 절차)
- - `tl.from`·`Math.random`·`Date.now`·tween 값 안 `var(`(move 작성 시)
- - 출처 없는 실수치, 표본 덱의 실존 회사·인물 이름
- - Playwright로 캡처(캡처는 `capture`·`smoke` 경로만)
- ## 참고 문서
- - `docs/getting-started.md`: 설치부터 MP4까지
- - `docs/writing-a-deck.md`: `deck.yaml` 필드·beat type·내용 감사
- - `docs/concepts.md`: 컨셉 팩 6종·새 컨셉 추가
- - `docs/moves.md`: move 계약·작성·테스트
- - `docs/media.md`: 프레임 시퀀스·영상·마스크
- - `docs/export.md`: 내보내기·캡처·smoke
- - `docs/architecture.md`: 층 구조·timeline 모델·개발 원칙·state 기록
README.md · README · 187 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- <p align="center">
- <img src="docs/hero.png" alt="Scrolline v2 decks: a time rail, a morphing chart and a zoom into a single bar" width="100%">
- </p>
- <h1 align="center">Scrolline</h1>
- <p align="center"><b>Scroll-driven presentation decks: one stage, one continuous timeline, and moves that turn one element into the next.</b></p>
- <p align="center">
- <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-5e6ad2.svg" alt="License: MIT"></a>
- <img src="https://img.shields.io/badge/node-%E2%89%A522-5e6ad2.svg" alt="Node 22 or newer">
- </p>
- <p align="center">
- <a href="README.ko.md">한국어</a> · <a href="docs/getting-started.md">Getting started</a> · <a href="SKILL.md">Claude Code skill</a> · <a href="docs/architecture.md">Architecture</a>
- </p>
- You write a `deck.yaml`. Scrolline lays every beat on one paused GSAP timeline, the mouse wheel scrubs it, presenter keys jump between stops, and the same timeline renders to MP4.
- ## Why v2
- - **v1 reused 12 scene templates**, so every deck read as the same deck with new pictures. v2 has no scenes: a deck is one continuous master timeline on one stage.
- - **Beats hand off instead of cutting.** A link move carries part of one beat (a bar, a dot, a date) into the place it holds in the next beat, so the audience follows one object rather than a slide change.
- - **Each concept has its own motion grammar.** A concept pack fixes the camera axis, timing and allowed moves, and names signature moves the deck must use. The six example decks move differently because their grammars differ.
- > Adding video? Issue your own Pexels or Pixabay API key first and keep it in `.env` (git-ignored, blocked by `npm run check`). See [docs/media.md](docs/media.md).
- ## Example decks
- Six decks, one per concept. Decks marked *sample* use a fictional company and say so on screen. The others use real data with a source list in `deck.yaml`.
- | Deck | Concept | Typical use | Signature moves |
- |---|---|---|---|
- | [`rail-ai-decade`](decks/rail-ai-decade/deck.yaml) · Generative AI, 2017 to 2026 | `rail` · horizontal time rail | company history, roadmap, an industry's decade | `rail-advance` `era-shift` `counter-handoff` |
- | [`data-ev-shift`](decks/data-ev-shift/deck.yaml) · How far the EV shift has come | `data` · data journalism | quarterly results, market analysis | `dot-multiply` `mark-morph` `annotation-pin` |
- | [`launch-orbit-note`](decks/launch-orbit-note/deck.yaml) · Minute product launch *(sample)* | `launch` · product launch | product or feature launch | `lit-from-dark` `sticky-scrub-link` `number-slam` |
- | [`zoom-root-cause`](decks/zoom-root-cause/deck.yaml) · Q3 revenue diagnosis *(sample)* | `zoom` · infinite zoom drill-down | root cause, TAM-SAM-SOM, org structure | `zoom-dive` `zoom-surface` `depth-ladder` |
- | [`canvas-pitch`](decks/canvas-pitch/deck.yaml) · Seed pitch on a map *(sample)* | `canvas` · camera flythrough | pitch deck, strategy map, process | `arc-flight` `establish-crane` `atlas-pullback` |
- | [`kinetic-next-word`](decks/kinetic-next-word/deck.yaml) · How AI writes an answer | `kinetic` · kinetic type lecture | lecture, keynote, statement | `word-door` `slot-pick` `phrase-fold` |
- The decks are in Korean. See [docs/concepts.md](docs/concepts.md) for what each concept allows.
- ## Quick start
- Requires Node.js 22 or newer. ffmpeg is needed only to cut frame sequences, and the HyperFrames CLI (fetched by `npx`) only to export MP4.
- ```bash
- git clone https://github.com/gongnyang/awesome-html-scrolline-deck.git
- cd awesome-html-scrolline-deck
- git checkout v2
- npm install
- npm run dev
- ```
- Open `http://localhost:5173/decks/rail-ai-decade/` and scroll, or press <kbd>→</kbd>.
- Start your own deck from a concept:
- ```bash
- npm run deck -- new my-review --concept data # decks/my-review/{deck.yaml,index.html,main.js,assets/}
- # write beats in decks/my-review/deck.yaml
- npm run deck -- plan my-review # stops and timings, computed in node
- npm run export -- my-review # out/export/my-review.mp4
- ```
- The full walkthrough is in [docs/getting-started.md](docs/getting-started.md), and every `deck.yaml` field is in [docs/writing-a-deck.md](docs/writing-a-deck.md).
- ## A beat in `deck.yaml`
- ```yaml
- - id: b-trend
- type: chart
- kind: bar
- categories: ["Q1", "Q2", "Q3"]
- series:
- - { name: "Revenue ($M)", values: [3.1, 3.6, 4.2] }
- title: "Each quarter added about $0.5M"
- states:
- - name: steps
- notes:
- - { index: 1, text: "+0.5" }
- - { index: 2, text: "+0.6" }
- place: { slot: full }
- steps:
- - { name: steps, move: annotation-pin } # a stop after the step
- ```
- Beats hold content and moves hold motion. A beat renderer draws only the finished state. The concept supplies default moves, and each beat can name its own `enter`, `exit`, `link`, `steps`, `camera` or `ambient` move.
- ## Structure
- ```mermaid
- flowchart TD
- site["site/ (gallery)"] --> decks
- decks["decks/<id>: deck.yaml, main.js, assets/, sequences/"] --> concepts
- concepts["concepts/<id>: concept.json, tokens.css"] --> moves
- moves["moves/<family>/<id>.js: enter, exit, link, step, camera, ambient"] --> engine
- engine["engine/: stage, plan + build, scroll, presenter, handoff, media, export"]
- tools["tools/: cli, check, export, capture, smoke"] -.-> decks
- tools -.-> engine
- ```
- - **engine** knows nothing about content. It renders beats, plans the timeline in node (no DOM), builds the master timeline, drives it from scroll and keys, and exports.
- - **moves** are small units of motion with a fixed contract: pure `timing`, deterministic `build`, no `tl.from`, no clock or `Math.random`. Each move ships with a test.
- - **concepts** pick a camera axis, timing, eases, tokens and an allow list of moves.
- - **decks** are data plus assets. Deck-only scenes go in `sequences/`.
- Imports only go downward, and `npm run check` blocks upward imports, cycles and imports across sibling folders. See [docs/architecture.md](docs/architecture.md).
- ## Presenter keys
- | Key | Action |
- |---|---|
- | <kbd>→</kbd> <kbd>↓</kbd> <kbd>Space</kbd> <kbd>PageDown</kbd> | next stop |
- | <kbd>←</kbd> <kbd>↑</kbd> <kbd>Shift</kbd>+<kbd>Space</kbd> <kbd>PageUp</kbd> | previous stop |
- | <kbd>Home</kbd> <kbd>End</kbd> | first, last stop |
- | <kbd>b</kbd> <kbd>.</kbd> | blackout |
- | <kbd>f</kbd> | fullscreen |
- The wheel and the keys move the same scroll position. A key press travels to the next stop in 0.9 to 2.6 s, depending on distance. With reduced motion, or with `?motion=reduce`, the jump is instant and moves fall back to fades of the same length, so every stop lands at the same time.
- ## Video
- | Need | How | Beat |
- |---|---|---|
- | Video that scrubs with the scroll | image sequence drawn on a canvas, cut with `npm run frames` | `type: video`, `mode: scrub` |
- | Live footage inside a beat | `<video muted playsinline>` that plays while the beat is active | `type: video`, `mode: play` or `loop` |
- | Video inside letters or a shape | text mask applied by a move (`mask-word-in`), or a `clip-path` shape | `mask: { type: text, text: "10년" }` |
- Scrubbed video uses frames rather than `video.currentTime` so that seeking is exact in both directions on every browser. See [docs/media.md](docs/media.md).
- ## MP4 export
- ```bash
- npm run export -- rail-ai-decade # out/export/rail-ai-decade.mp4
- npm run export -- rail-ai-decade --dry-run # print the timeline map and path only
- npm run capture -- rail-ai-decade --stops # one PNG per stop in out/capture/rail-ai-decade/
- ```
- Export replaces scrolling with a presentation path. It travels from stop to stop, holds 1.6 s on each one (`exportHold` per beat), and renders the paused timeline through [HyperFrames](https://github.com/heygen-com/hyperframes) at 1920×1080. Because the timeline depends only on time, the MP4 shows the same frames as the browser. See [docs/export.md](docs/export.md).
- ## Tests and CI
- ```bash
- npm test # vitest + happy-dom: engine modules, every move, every deck
- npm run check # dependency rules, a test next to every module, state schemas, move static rules
- npm run ci # both; the merge condition
- ```
- Move tests run a shared contract check: seek determinism, rewind to the initial state, no blur or 3D under reduced motion, and handoff landing within 1 px. GitHub Actions runs `npm ci`, `npm test` and `npm run check` on every push to `main` and `v2`, and on every pull request.
- ## Use it from Claude Code
- `SKILL.md` makes this repository a Claude Code skill named `scrolline-deck`. It takes you from a brief to a concept, then `deck.yaml`, a smoke run and the MP4. Link the checkout into your skills folder:
- ```bash
- ln -s "$PWD" ~/.claude/skills/scrolline-deck
- ```
- ## Repository layout
- ```text
- engine/ stage, timeline plan/build, scroll, presenter, handoff, media, export, beat renderers
- moves/ move library by family (reveal, type, morph, camera, rail, data, media, assemble, emphasis)
- concepts/ concept packs: concept.json + tokens.css
- decks/ example decks: deck.yaml + main.js + assets/
- tools/ cli, checks, export, capture, smoke, frame extraction
- site/ gallery
- docs/ guides
- plan/ design source of truth (Korean): PLAN, ARCHITECTURE, CONTRACTS
- state/ board.json + runs.jsonl build-state log
- ```
- ## Contributing
- See [CONTRIBUTING.md](CONTRIBUTING.md). In short, keep commits small, put a test next to every module, keep each commit to one hat (`Hat: feature` or `Hat: refactor`), and run `npm run ci` before a pull request.
- ## License and credits
- Code: [MIT](LICENSE) © gongnyang.
- - **Motion sources.** Every move lists the techniques it borrows from in `sources`, using slugs from [awesome-ai-motion](https://github.com/gongnyang/awesome-ai-motion).
- - **References.** Scroll stories and keynotes such as The Pudding, Our World in Data, The New York Times, Codrops and Apple product pages were studied for ideas only. No code or assets from them are included. See [docs/attribution.md](docs/attribution.md).
- - **Stock footage.** Pexels License, credited per deck in `decks/<id>/assets/CREDITS.md`. Other media was rendered for this repository.
- - **Data.** Each non-sample deck lists its sources, with access dates, in `deck.yaml`.
- - **Dependencies.** Built on [GSAP](https://gsap.com) (GreenSock standard no-charge license), [Lenis](https://github.com/darkroomengineering/lenis) (MIT) and [Vite](https://vite.dev) (MIT). [HyperFrames](https://github.com/heygen-com/hyperframes) (Apache-2.0) renders the exports.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.