grill-for-visualization
Turn an idea into a polished coded video (product showcase or system/concept explainer) — "make an animation of how X works", "visualize this for a demo", "grill me for a visualization". Round-based interview about what to show, a storyboard the user approves, then a React project that renders an MP4, with the source kept editable. For stress-testing a plan with no video at the end, use skill-tree:grill-for-planning instead.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- grill-for-visualization
- description
- Turn an idea into a polished coded video (product showcase or system/concept explainer) — "make an animation of how X works", "visualize this for a demo", "grill me for a visualization". Round-based interview about what to show, a storyboard the user approves, then a React project that renders an MP4, with the source kept editable. For stress-testing a plan with no video at the end, use skill-tree:grill-for-planning instead.
- allowed-tools
- Read, Write, Edit, Grep, Glob, Bash, WebFetch
- user-invocable
- true
- disable-model-invocation
- true
02 资源文件 26
- 参考文档references/BRIEF.md5.0 KB
- 参考文档references/FREE.md2.7 KB
- 参考文档references/REMOTION.md1.7 KB
- 参考文档templates/free/index.html485 B
- 参考文档templates/free/package.json339 B
- 脚本templates/free/scripts/render.ts4.2 KB
- 脚本templates/free/src/fonts.ts216 B
- 其他templates/free/src/main.tsx412 B
- 其他templates/free/src/runtime/frame.tsx1.6 KB
- 脚本templates/free/src/runtime/index.ts295 B
- 脚本templates/free/src/runtime/math.test.ts4.9 KB
- 脚本templates/free/src/runtime/math.ts4.4 KB
- 其他templates/free/src/runtime/Player.tsx4.8 KB
- 参考文档templates/free/tsconfig.json453 B
- 脚本templates/free/vite.config.ts184 B
- 参考文档templates/remotion/package.json352 B
- 脚本templates/remotion/src/fonts.ts179 B
- 脚本templates/remotion/src/index.ts89 B
- 其他templates/remotion/src/Root.tsx316 B
- 脚本templates/remotion/src/runtime/index.ts191 B
- 参考文档templates/remotion/tsconfig.json300 B
- 其他templates/shared/.gitignore29 B
- 其他templates/shared/src/components/Appear.tsx991 B
- 脚本templates/shared/src/content.ts958 B
- 其他templates/shared/src/scenes/TitleScene.tsx985 B
- 其他templates/shared/src/Video.tsx1.1 KB
03 SKILL.md 正文
Grill For Visualization
Interview the user until you know exactly what the video must say, get a storyboard approved,
then build it. The output is a self-contained project directory: a rendered MP4 plus the React
source that produced it, runnable with npm install and two scripts.
Read references/BRIEF.md before the first round. It is the creative standard for everything below: composition, motion, typography, and the review checklist.
1. Grill
Use the round format and frontier rule from grill-for-planning: ask every question whose prerequisites are settled in one numbered round, give a recommended answer for each, wait, recompute. Look facts up yourself (repo, docs, brand assets on disk); put decisions to the user.
The design tree, roughly in dependency order:
- Purpose. What is being visualized, and is it a product showcase or an explainer of how something works? Who watches it, and where (meeting screen, phone, embedded in a doc)? What is the one thing they should understand afterwards?
- Stack. Is this for personal use or for work at a for-profit company of more than three people? This picks the stack in step 3, so ask it in the first round.
- Truth. The actual rules, thresholds, steps, and numbers. Limitations and caveats that must be shown honestly. Anything that must not appear (confidential details, competitor names, unreleased features).
- Form. Duration, aspect ratio, available assets (logo, screenshots, brand colors, fonts), mood or reference pieces, tone of the copy, the closing line.
Keep going for as many rounds as the tree needs. Stop when the frontier is empty, not when the answers start to feel sufficient.
Never invent functionality, customer claims, or metrics to fill a gap: ask. If the user says to just go, stop asking, make the remaining calls yourself, and list every assumption beside the storyboard so each one can be corrected.
2. Storyboard
Present one table, one row per scene: what the viewer sees, what they should understand, the on-screen copy, approximate duration, and how it hands off to the next scene. Under it, list assumptions and anything illustrative rather than factual.
Do not create files until the user approves the storyboard. Changes loop back here.
3. Scaffold
Pick the stack from the answer in step 1 and read its reference:
- Personal use, or the user confirms they hold a Remotion license: references/REMOTION.md.
- Work, or any doubt: references/FREE.md. Same authoring API, no license requirement.
Scenes import from ./runtime in both stacks, so everything in the brief applies to either.
Create the project in ./<slug>/ (or the current directory if it is empty), where <slug> is
a short kebab-case name for the piece:
T="${CLAUDE_PLUGIN_ROOT:-${SKILL_TREE_DIR:-$HOME/projects/skill-tree}}/skills/grill-for-visualization/templates"
mkdir -p <slug> && cp -r "$T/shared/." "$T/<free|remotion>/." <slug>/
Then set name and the output filename in package.json to the slug, and install with the
commands in the stack reference. Dependencies are installed with --save-exact at their
current versions; the templates carry none.
4. Build
- Logic first, test first. Every number or state shown on screen comes from a pure
function in
src/logic/with a parametrized test beside it. A hand-typed figure in a scene drifts from the facts the moment the user edits one of them. - Content. Copy, colors, and timing go in
content.tsundersrc/; add each scene totimingandSCENE_ORDER, and to the component map inVideo.tsx. Total duration derives from these. - Sequence, then polish. Get every scene on screen in order with final copy before
refining any one of them. Shared pieces go in
src/components/. - Run
npm testandnpm run typecheck.
5. Review
Render one still for every beat of every scene (each point where something has just appeared or settled), and open each image. Check them against the checklist at the end of the brief: clipping, overlap, text size, one focal point per frame, an ending that holds. Fix and render again until a full pass is clean. Then render the MP4.
Looking at the frames is the step that makes the result good. Passing tests say nothing about whether a label sits on top of a vehicle.
6. Deliver
Write README.md in the project:
- Length, resolution, frame rate, and the commands (
npm install,npm run dev,npm run render,npm test). - The storyboard as built.
- A "change X in file Y" table: copy, colors, facts and thresholds, scene timing, assets, aspect ratio.
- Assumptions and anything illustrative.
- For the Remotion stack, the license note from its reference.
Tell the user where the MP4 is, what you assumed, and anything in the storyboard that changed during the build.
04 同仓库更多 Skills
wait-what
Stop. Your plan/idea did not land. Re-pitch it.
verify
Verify before answering whether something works, still passes, is gone, is used, or is correct — and whenever the user says "can you confirm", "are you sure", "did that actually work", or reports something is "still" broken. Produces the answer plus the evidence that would have falsified it. A failed GitHub Actions run is skill-tree:debug-ci instead.
ui-designer
Design or restyle a web UI — landing pages, dashboards, docs sites, app chrome — or when the user asks why a site "looks generic", "looks like a template", or wants it to feel intentional. A running list of design lessons learned, applied as rules rather than suggestions.
two-axis-review
Two-axis review of changes since a fixed point (commit, tag, HEAD~N, or default HEAD~1): Standards (does the code follow this repo's conventions?) and Spec (does the code do what it should?). Axes run as parallel sub-agents so neither masks the other. Use when the user says "review against the spec", "does this follow our conventions", "standards and spec review", or "two-axis review". Not a correctness bug hunt — that's the built-in `/code-review`.
tui-screenshots
Use for generating or refreshing TUI screenshots for docs — "regenerate the screenshots", "the README screenshots are stale". Drives a Textual/TUI app headlessly and exports SVG. Not for reading a user's screenshot — that is `screenshot`.
to-tickets
Break a spec, plan, or conversation into tracer-bullet vertical-slice tickets with blocking edges — "turn this into tickets", "break this down", "what's the work?". Pairs with skill-tree:to-spec upstream and skill-tree:handoff downstream.