When should you use it?
- You explain the same process again and again on calls, in onboarding or to investors
- Diagrams of the process lose people halfway through
- You have a few documents that already describe the steps
Not for: Marketing claims about results or returns; anything investor-facing still needs your compliance review; Processes that only exist in someone's head with no written source
What do you need, and what do you get?
You need
- Claude Code or OpenAI's Codex on your computer
- A new, empty folder with three to five documents that describe the process, saved as PDF or plain text
- Who will watch it and what they should take away
- About an hour, plus time to review the storyboard
You get
- A storyboard you approve before anything is built
- An animated page in its own folder that plays on click
- A sources file mapping every on-screen line to a document
- Screenshot-based fixes for overlaps and text that moves too fast
How does it work, step by step?
- Prepare a clean folderCopy in only the documents that describe this one process, and leave financial models, rent rolls and investor files out, since anything the agent opens is shared with your AI provider.
- Fill in the five header linesName the process, the audience, the feeling they should leave with, the length and a short folder name at the top of the prompt below.
- Approve the story and storyboardRead the agent's two-sentence version of the story, correct it if it is too narrow, then approve or edit the scene-by-scene storyboard.
- Let it build and self-checkThe agent builds the animation, screenshots each scene, fixes what reads badly and traces every claim to a file.
- Review and shareWatch it yourself, check the sources file, then show it live or screen-record it; voice and an MP4 export need extra tools.
The prompt
The original prompt by Avi Hacker, J.D., word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Claude Code. Values in lime are placeholders.
Original prompt by Avi Hacker, J.D.
I want to explain one process with a short animated walkthrough instead of a diagram. The process: [the process you explain most often] Who's watching: [an investor / a new hire / my team / me] What they should feel at the end: [one sentence] Length: [60 to 90 seconds] Folder name: [short-name] 1. Read the files in this folder that describe this process, and list what happens, in order, with the file each step came from. If a file turns out to hold financials (a model, rent roll, budget or statement), stop reading it and tell me. 2. Before you storyboard, tell me in two sentences what story you think this is. If it's narrower than what I described, say so. 3. Write a storyboard for a vertical (9:16) walkthrough at the length above, about one scene per step: what's on screen, the caption, and how long it holds. If the steps don't fit, merge them and tell me what you merged. Show me and wait for my approval. 4. After I approve, build it as ./animations/[short-name]/index.html with GSAP, one module per scene. Put every animation on one paused GSAP timeline, exposed as window.timeline, and don't use setTimeout, setInterval, Math.random or anything clock-based outside it, so it can be rendered frame by frame later. It opens paused and plays on click. 5. Open it in a headless browser (if Playwright isn't installed, give me the install command and wait) and take a screenshot at the start, middle and end of every scene. Fix anything in the screenshots that overlaps, reads too fast, is too small for a phone or looks like a slide deck. If you can't take screenshots, say so instead of saying it's fixed. 6. Check every on-screen claim against the files. Cut anything you can't trace. Save a sources.md that maps each line to its file. 7. Keep everything in ./animations/[short-name]/. Don't send, post or upload anything, and don't write outside that folder.
Exactly as published by Avi Hacker, J.D. in Stop Explaining Your Business With Diagrams. Have Claude Code Animate It..
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
Make a short animated walkthrough of one process, built only from the files in this folder. Process: {process} Audience: {audience} What they should understand by the end: {takeaway} Length: {length_seconds} seconds, vertical 9:16 Folder name: {folder_name} 1. List the steps in order with the file each came from. If a file contains financial figures, stop reading it and tell me. 2. Sum up the walkthrough's message in two sentences so I can confirm it, then pause until I reply. 3. Storyboard one scene per step with on-screen text and timing, give the most time to the step where things usually go wrong, and wait for my approval. 4. Build ./animations/{folder_name}/index.html with one paused animation timeline that plays on click and no timers or randomness outside it. 5. Capture frames at three points in each scene (opening, halfway, closing) and at each transition, then correct overlapping elements, empty frames and captions that are too small or vanish too quickly. If capturing frames isn't possible, tell me. 6. Remove any claim you cannot trace to a file and save sources.md mapping each line to its file. Keep everything in ./animations/{folder_name}/ and do not send, post or upload anything.
What can go wrong?
- Every file the agent reads is sent to the AI provider; only include what you would share with a vendor.
- The first version is a draft; the author needed four rounds, each driven by one line of feedback about who is watching.
- Animations can hide blank frames or overlapping text between scenes; check the screenshots at scene boundaries, not only mid-scene.
- Investor or client-facing versions can read as promises; have counsel or compliance review them before you send them.
Our take
A clever use of a coding agent that has nothing to do with software: turning written procedures into something people can follow. The prompt is well guarded. It stops if it opens financial files, asks you to confirm the story before storyboarding, waits for approval before building, requires screenshots rather than claims of a fix, and confines everything to one folder. We ran it word for word on the box with a fictional bookkeeping firm's onboarding notes plus a planted fee-and-margin spreadsheet. The agent stopped reading the spreadsheet and said why, summarized the story in two sentences, storyboarded eight vertical scenes totaling 60 seconds with the most time on the step clients get stuck on, and built the page on one paused animation timeline. Playwright was missing, so it printed the install command and waited, as instructed. Our own headless-browser screenshots then caught a blank frame between two scenes, which we fixed, and the fact-check pass reworded an outro line the notes did not support.
Where the time goes back: You explain the process once, carefully, and reuse the walkthrough on every call, onboarding and meeting instead of redrawing it each time.
FAQ
Do I need to know animation or code?
Can I get a video file?
Are the author's industry examples real?
Source and credit
The original prompt on this page is by Avi Hacker, J.D., shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- Stop Explaining Your Business With Diagrams. Have Claude Code Animate It.
- Creator
- Avi Hacker, J.D.
- Published on
- AI Tactical Toolbox (Substack)
- Original date
- Oct 19, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 22, 2026: passed. Dry-run tested by our AI test agent on sample input. Prompt guardrails all held; boundary screenshots added to our adapted prompt and pitfalls. Voice, music and MP4 render not exercised.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.