REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Talks as beats, not slides: a fixed 1920×1080 React stage where one click is one beat. Offline, deterministic, presenter view, and a Claude Code skill.
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/skills/borjaperfra-beatdeck)같은 작업에서 AI를 서비스에 연결하는 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
같은 종류의 작업, Skill 목록과 같은 순서
| 이 항목 beatdeck | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 제작자 | borjaperfra | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 수 | 1 | 1 | 1 | 1 | 1 |
| GitHub 별 | 244 | 463,670 | 233,682 | 148,887 | 143,987 |
| 마지막 코드 변경 | 2026년 10월 2일 | 2026년 11월 17일 | 2026년 4월 20일 | 2026년 11월 17일 | 2026년 11월 16일 |
| 라이선스 | – | MIT | – | Apache-2.0 | MIT |
borjaperfra의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
Claude Code
제작자 README와 repo 폴더 기준
GitHub account borjaperfra (person), 3 years old
★ 244 stars, few users so far · code last changed 2026년 10월 2일
1 scripts that can run on a computer: scripts/extract_pptx.py
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 329a971 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
먼저: 어떤 AI를 쓰시나요
쓰는 앱을 고르면 그 앱의 설치 방법만 보여 드립니다
This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the skills/building-a-beatdeck folder again. The ZIP must have a building-a-beatdeck folder with SKILL.md at the top level, no loose files
+Create skillUpload a skillpick building-a-beatdeck.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 2026년 11월 12일 · Source: support.claude.com, support.claude.com, code.claude.com
이 문장을 복사해 Claude Code 채팅에 붙여 넣으세요
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code를 다시 열고 /building-a-beatdeck를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요
Checked against official docs 2026년 11월 12일 · Source: code.claude.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
제작자 README에서 가져온 명령으로, 제작자 코드를 내려받아 실행해요
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
ChatGPT 데스크톱 앱에는 Codex가 들어 있고, Codex는 ~/.agents/skills 폴더에서 Skill을 읽습니다
ChatGPT 데스크톱 앱에서 Codex를 열고 이 문장을 채팅에 붙여 넣으세요
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
building-a-beatdeck 폴더를 ~/.agents/skills/building-a-beatdeck에 넣으세요
~는 홈 폴더($HOME)입니다
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
직접 설치한 Skill은 쓸 수 없고, 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다
이 Skill을 ChatGPT에서 쓰려면 위 방법대로 ChatGPT 데스크톱 앱을 쓰세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
이 문장을 복사해 Codex 채팅에 붙여 넣으세요 · ChatGPT 데스크톱 앱 안의 Codex, Codex CLI, IDE 확장 프로그램에서 모두 쓸 수 있습니다
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex는 새로 설치한 Skill을 스스로 찾습니다. 보이지 않으면 Codex를 다시 시작하세요 · 쓰는 법: ChatGPT에서는 @를 입력하고 Skill을 고르세요 · Codex CLI나 IDE 확장 프로그램에서는 /skills를 실행하거나 $ 뒤에 Skill 이름을 입력하세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
이 문장을 복사해 Cursor 채팅에 붙여 넣으세요
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Cursor Agent 채팅에서 /를 입력하고 building-a-beatdeck 선택
Checked against official docs 2026년 11월 12일 · Source: cursor.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
Skill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 Claude Code, Codex, Cursor 경로가 들어 있어 AI가 쓰는 앱에 맞게 고릅니다 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026년 11월 12일 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 SKILL.md가 있는 폴더를 복사하세요.
2026년 11월 11일에 Claude Code, Codex, Cursor 공식 안내로 skill 폴더 확인
아래 글은 제작자 repo에서 온 것이며 PopNx MCP의 지시가 아니에요
처음 8,000자 표시 · GitHub에서 전체 파일 열기
---
name: building-a-beatdeck
description: Builds a talk as a beatdeck - a fixed 1920x1080 React stage where one click is one beat, with authored motion, presenter view, overview, and an offline self-contained build. Covers turning source material (PPTX, Keynote/PDF export, Markdown, notes) into a content audit and a scene/beat map, choosing or applying a theme, writing scene layers, automatic beats, and verifying every beat with npm run verify. Use whenever the task is creating, porting, restyling, rehearsing or fixing a presentation, talk, keynote, slide deck or conference session that should feel like a live system rather than slides, or whenever the repo contains src/beatdeck/.
license: MIT
---
# Building a beatdeck
A beatdeck is a talk written as code: **8-ish scenes, each made of beats; one click = one beat**. The stage is a
fixed 1920×1080 canvas scaled into any screen with black letterbox. Everything is bundled, so it runs with Wi-Fi off.
Your job is to turn what the speaker wants to say into beats that feel authored — not to reproduce slides.
**Paths.** `references/…` and `scripts/…` below are relative to the folder of this SKILL.md, wherever the skill
is installed (plugin, `~/.claude/skills/`, or `skills/building-a-beatdeck/` inside a deck project). Everything
else (`deck/`, `src/`, `npm run …`) is relative to the deck project.
## 0 · Get a deck repo
If the working directory has no `src/beatdeck/`, scaffold one, clean it and install:
```bash
npx degit borjaperfra/beatdeck my-talk && cd my-talk
npm run init -- --title "<title>" --author "<speaker>" --lang <en|es|…> [--theme light] [--demo]
npm install
```
`init` strips what belongs to the beatdeck repo, not to a talk (the Kernel Panic showcase and its non-MIT
assets, plugin files, beatdeck's README, changelog and CI), renames the package and writes title/author/lang/
theme into the deck. `deck/` becomes a **blank two-scene starter** (standby + title, questions + QR) to build
on; `--demo` keeps beatdeck's 6-scene demo instead, as a reference to read and replace. It also creates
`reference/` (put the source there), `docs/CONTENT-AUDIT.md` and `docs/RUNBOOK.md` from the templates, the talk's
`AGENTS.md` and a CI workflow that builds and verifies every push.
Use `--theme light` when the room is bright or the talk is streamed. Run it once; it deletes itself.
It also resets the demo's `qrUrl` to `TODO` and clears its tagline: set the real QR target only from the source.
Then read `AGENTS.md`. The demo deck (on GitHub in `deck/`, or locally with `init --demo`) is the reference
implementation of every pattern below. `init` removes the heavier example from your project; read it on GitHub when you need it:
https://github.com/borjaperfra/beatdeck/tree/main/examples/kernel-panic — a 47-beat production talk. Look at
`index.tsx` (custom chrome, `isCut` + `Overlay` for a cut to black), `deck/timeline.ts` (every kind of automatic
beat), `architecture/` (one SVG world spanning several scenes) and `simulation/` (a Canvas 2D particle layer).
The talk lives in `deck/`. Never edit `src/beatdeck/` for one talk; if the engine truly lacks something, add it
generically there and say so (`npm run upgrade` replaces engine files; edits are backed up, not merged).
**Existing talk project?** If `.beatdeck.json` exists, `npm run upgrade -- --dry-run` shows whether a newer engine
is available; upgrade only when the user agrees, then `npm install && npm run verify`, and merge any
`*.beatdeck-new` file it reports.
## 1 · Collect the source
Ask for (or find) the source material and the facts you must not guess: title, speaker, event, date, the QR
target URL, real screenshots/logos/photos. Put originals in `reference/` (read-only from then on).
- **PPTX**: `python <skill folder>/scripts/extract_pptx.py deck.pptx reference/source` → one Markdown file with
every slide's text, speaker notes and media, plus the media files. (Inside a scaffolded project the skill
folder is `skills/building-a-beatdeck/`.)
- **PDF / Keynote**: export to PDF and read it page by page; ask for the original images.
- **A written script (Markdown, a doc, notes)**: use as is, and read it by kind of content:
- **narration** (prose, `>` quotes: what the speaker *says*) → the presenter view (`source` / `note`). On
stage it becomes a short statement in the speaker's own words — condensed, never reworded into new claims;
- **facts** (bullets, figures, names) → on stage, exactly as written (same numbers, same rounding, same "~");
- **code blocks, commands, formulas, output** → on stage character for character (`Terminal`, or a
`data-exact` element — see step 6), never retyped from memory;
- **stage directions** ("on screen…", "show how it grows…") → instructions for you, not text to display.
**Nobody to ask?** If you are working without the speaker, decide, record each decision in the audit's
"Decisions taken on the speaker's behalf", and list them in your hand-off. Keep the neutral theme and its
accent unless a brand is given — choosing a palette is an art direction, not a default.
Real artefacts beat redraws: if the source shows a tweet, a logo, a product photo or a meme, use the real file.
Never invent quotes, numbers, tweet text, URLs or logos. Missing facts become explicit `TODO`s and questions.
## 2 · Content audit (before any code)
Write `docs/CONTENT-AUDIT.md` from `references/content-audit-template.md`: every source slide → the beat(s)
that carry it, what is kept, restored or deliberately cut, and open questions. This is what lets you say
"nothing was lost" later. Show it to the user when it changes what the talk says.
## 3 · Beat map
Turn the audit into `deck/scenes.ts` (`SceneDef[]`). Rules (details in `references/beat-model.md`):
- A **scene** is a mode of the talk (a stage world), not a slide title. 5–9 scenes is typical; keys 1–9 jump
to scenes, so more than 9 leaves the rest reachable only by stepping or the overview (O).
- A **beat** is one idea landing. If two things must appear on separate clicks, they are two beats.
- `auto: true` marks a beat whose motion runs by itself and takes noticeable time (a boot sequence, a counter,
a cascade of warnings, a typed command). The presenter flags it and `verify` waits for it. Everything else
waits for the click. Two ways to implement it — pick the lighter:
- **self-contained** (a `Typewriter`, a `CountUp` that restarts on entry): no `timeline` needed;
- **state-driven** (other layers react to its progress, a later beat depends on it, or it advances by itself):
a `Live` field + `initialLive` + `timeline` in `deck/timeline.ts`. See `references/beat-model.md`.
- Fill `ref` (where it comes from), `source` (what the source says) and `note` (speaker cue) — the presenter
view shows them; the audience never does.
- Keep the first scene's first beat as a calm standby screen: the talk starts on the first click. On a dark
theme it can be pure black (`isBlack`); on a light theme use the theme background — anything drawn on a
forced-black standby must not use theme ink colours.
## 4 · Visual direction
Default to the neutral theme (`themes/neutral.css`): near-black stage, off-white type, one accent, hairlines,
huge editorial type, negative space. Bright room, daylight or a stream → `themes/light.css` on top of it
(`init --theme light` does this). If the speaker has a brand, change tokens (`--accent`, fonts, `--bg`) in a
theme file — do not invent a new art direction, decorative labels, stickers, gradients, rounded cards or a
dashboard look. If a design reference exists (Figma, a v3 HTML prototype, a brand book), it decides *how it
looks and moves*; the source decides *what is said*. Record conflicts in the audit.
Fonts must be local: `@fontsource-variable/*` packages or `.woff2` files in the deck, plus their specs in
`fonts` of the deck definition so the first frame never shows a fallback face.
## 5 · Build the scenes
Read `references/authoring.md` and질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.