build-viz

Builds, reviews, and embeds one interactive HTML explainer for a fluid mechanics chapter.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/shammun/fluidpy --skill build-viz-shammun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-viz
Source: https://github.com/shammun/fluidpy/tree/main/.claude/skills/build-viz
Command: npx skills add https://github.com/shammun/fluidpy --skill build-viz-shammun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating or improving a single interactive explainer for a textbook chapter normally requires running the entire chapter pipeline; this Skill isolates one explainer so it can be storyboarded, built, reviewed, embedded, and committed on its own. ## Core Features & Use Cases - Targeted explainer builds: Build or rebuild one explainer by chapter number and slug, with an optional verbatim improvement request passed to the builder. - New explainer workflow: For new ideas, it coordinates curation, storyboard design, mirrored function implementation with tests, and notebook embedding. - Quality gates: Runs lint and screenshot checks via tools/viz_lint.py and tools/shot.py, then a reviewer pass with up to two fix rounds before committing. - Use Case: Run /build-viz 7 dispersion_relation "make the particle orbits bigger on phones" to iterate on a single explainer without touching the rest of chapter 7. ## Quick Start Ask the assistant to run /build-viz with a chapter number, an explainer slug or the word new, and an optional change request, for example to rebuild the chapter 7 dispersion relation explainer with larger particle orbits on phones.

Frequently Asked Questions about build-viz

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rebuild a single interactive explainer without running the full chapter pipeline?

Run /build-viz with the chapter number and the explainer slug, optionally followed by a quoted change request. The skill briefs the builder with the storyboard and mirrored function, iterates on lint and screenshot checks, then commits only that explainer.

How do I add a new explainer to a chapter?

Use /build-viz N new followed by a quoted idea. The skill adds a curation entry and storyboard, implements and tests the mirrored fluidpy function if missing, builds the explainer, embeds it in the notebook, and commits.

Is there a limit on how many explainers a chapter can have?

Yes. A chapter keeps four to five explainers, capped by project.max_explainers_per_chapter in book.yaml. If a new explainer would exceed the limit, the skill asks which existing one to replace.

What quality checks run before an explainer is committed?

The builder iterates with tools/viz_lint.py and tools/shot.py until they pass, then a reviewer updates the slug's section in the chapter viz report. Must-fix findings go back to the builder for up to two rounds.

What happens after an explainer is built for a published chapter?

The skill commits with a chapter-scoped message and runs /publish-chapter for new explainers. For rebuilt existing explainers, only a push plus a site-only publish is needed so the gallery text stays current.