manimvox-blocks
Skill2 starsChanged 21 days agoMITView on GitHub
Reusable scene components for manimvox episodes: finding a block (Venn diagram, ranked bars, a line chart over levels, a log-scale scatter, a grid of items, a token or config panel, a value flowing through stages, a sequence diagram, a code diff, a 3D surface, a 3D model from a file), copying it into the project with manimvox add, using and adapting it, and writing a new one. Use before drawing a chart or diagram by hand, or when the user asks for a block.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- manimvox-animationSkill
- manimvox-cliSkill
- manimvox-conceptSkill
- manimvox-coreSkill
- manimvox-creativeSkill
- manimvox-paperSkill
- manimvox-playlistSkill
- manimvox-prSkill
- manimvoxSkill
- manimvox-voiceSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 13
Run manimvox add --list. Each line is a block's name, what it draws, and its tags.
- Very specific: line 40
Put that line under from manimvox.kit import * in the episode.
- Distinctive: line 46
Read the copied file. The function's docstring lists the parameters, what it returns, and which parts to reveal one by one.
- Very specific: line 49
Place the result like any kit component (.move_to(...)), and reveal its parts with say and steps as the narration names them.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
manimvox blocks
A block is a function that builds one kind of scene component from the kit's shapes in the project's theme colours. manimvox add copies its code into the project, so the project owns it: a rendered project never changes when manimvox does.
Find one
Run manimvox add --list. Each line is a block's name, what it draws, and its tags. Check the list before you draw a chart, a set diagram, a sequence diagram or a code change by hand.
| Block | Draws |
venn | two overlapping circles with a count in each region |
bar-ranking | horizontal bars ranked by value, leaders highlighted; value_x places a threshold line |
line-by-level | a line chart over named steps (effort levels, versions, weeks) |
log-scatter | labelled points on a log-scale x axis (cost, size, time) |
bug-grid | one square per item, a slice lit as they are counted |
token-panel | a monospace panel of short lines, rows boxed in turn |
request-flow | a value hopping through a chain of stages |
sequence-diagram | actors as lifelines and the messages between them |
code-diff | code before and after, removed and added lines banded |
surface-plot | a 3D surface z = f(x, y) shaded by height, for an Episode3D; downhill gives a ball's route |
mesh-model | a 3D model from a glTF, OBJ or STL file as shaded faces the camera orbits, for an Episode3D; mesh_part picks a part (needs the trimesh extra) |
kinetic-title | a title that arrives as moving type, for an opening with no card or a chapter title |
end-card | a built end card: a challenge, a cliffhanger or a call to action with a link line |
transitions-demo | the chapter-seam transitions side by side, to see which fits |
Copy it into the project
In the project folder, run manimvox add <name>; several names at once are fine. It writes blocks/<name>.py (hyphens become underscores) and prints the import line, for example:
from blocks.bar_ranking import bar_ranking, grow, value_xPut that line under from manimvox.kit import * in the episode. Episodes run from the project folder, so blocks imports as written.
manimvox add never replaces a block already in the project, because it may hold edits; --force replaces it with a fresh copy, so ask the user before using it on a block they changed.
Use and adapt it
- Read the copied file. The function's docstring lists the parameters, what it returns, and which parts to reveal one by one.
- Most blocks reject input they cannot draw (an empty list, a negative value) with a
ValueError; the docstring says which, so read it before passing odd data. - Blocks draw in the theme's colours (
ACCENT,OK, a named colour), so they need no theming step. - Place the result like any kit component (
.move_to(...)), and reveal its parts withsayandstepsas the narration names them; see manimvox-animation. - Helpers that give positions (
value_x,point,place) stay right after you move or scale the block. - The copied file belongs to the project: change sizes, colours or layout in it. After any change run
manimvox draft epNNand read the contact sheets, ormanimvox check layout epNNwhere you cannot view images. - Numbers in a block are claims like any other: each one comes from
FACTS.md.
Write a new block
For a component the list lacks, write a function in the project's own blocks/ folder with the same rules. To contribute it to manimvox, see references/writing-a-block.md: the folder layout, block.json, the demo episode, the preview image and the checks.
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.