milestone-reveal
Skill0 starsChanged 17 days agoMITView on GitHub
Make a 12-second looping milestone clip in code with Claude Code. Thousands of tiny points drift like a night sky, pull together into your real number (followers, subscribers, revenue, customers), a line draws underneath and the label settles in. Premium, not a party. Use when someone says "milestone video", "celebrate 10k followers", "animate my subscriber count", "number reveal", "particle number animation" or wants to mark a result on LinkedIn or Instagram.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- imMamdouhaboammar/motion-graphics-skillsword for word, first seen Nov 1, 2026
- charlie947/motion-graphics-skillsword for word, first seen Sep 26, 2026
Other versions2 projects use a version of this.
Word for word · 2
- charlie947/motion-graphics-skills★ 247100% same
- imMamdouhaboammar/motion-graphics-skills★ 50100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/smokekit-ai-workflow-orchestration/templates/CLAUDE.mdCLAUDE.md
- afficheuxSkill
- animateSkill
- motion-designSkill
- review-loopSkill
- claude-motionSkill
- sound-designSkill
- web-simsSkill
- collectSkill
- explainer-storyboardSkill
- explainrooSkill
- fixitSkill
- herdr-teamSkill
- merge-gateSkill
- motion-designSkill
- motion-graphicsSkill
- animated-chartSkill
- apple-launch-filmSkill
- brand-intakeSkill
- launch-videoSkill
- loop-coverSkill
- model-showdownSkill
- motion-brief-writerSkill
- motion-effectsSkill
- motion-prompt-writerSkill
- newsletter-promoSkill
- reel-exportSkill
- reference-to-motionSkill
- motion-graphics-skillsSkill
- title-sequence-3dSkill
- vox-explainerSkill
- motion-illustrateSkill
- motion-launchSkill
- motion-principlesSkill
- motion-soundSkill
- motion-webSkill
- prd-table-rondeSkill
- product-launch-motionSkill
- remotion-motion-graphicsSkill
- rush-cutSkill
- secretscanSkill
- smokekit-ai-workflow-orchestrationSkill
- uxfixSkill
- wassupSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Before you start: read brand.md and MOTION.md if they exist.
- Very specific: line 48
Chrome can draw the same frame two ways: After repeated pixel reads it switches drawing mode, so a frame came out slightly different.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Milestone reveal, built in code
Each point is one follower, one subscriber or one customer. They gather into the number, hold, then drift apart so the loop has no jump.
Before you start: read brand.md and MOTION.md if they exist. If not, run brand-intake first, or ask for hex codes, a font and a logo file. Never call a result on-brand without them.
Step 1: Ask for four things, then wait
- The number, exactly as it should read, with commas. Example: "250,000".
- Where it comes from. A screenshot or link to the dashboard that shows it. No source, no clip.
- The label, word for word. Example: "LinkedIn followers".
- Brand and size. Background, particle and accent colours, the font file (attached), and the size. Default 1080 x 1350, 12 seconds.
The number is the user's real, sourced number. Never round it up, never add "+", never swap a target for a result. If the source shows 12,431, the clip says 12,431 or the user picks a lower round figure themselves.
Step 2: Build brief (paste into Claude Code)
Build one self-contained HTML file (canvas) for a 12-second seamless loop at [WIDTH] x [HEIGHT]. Tone: premium product launch, not a party. No bounce, overshoot, confetti or sparkle bursts.
Fixed text (real figure, do not alter, round or restyle): "[NUMBER]" and "[LABEL]". No other text on screen.
Brand: background [BG], particles and number [INK], accent line [ACCENT]. Font: the attached [FONT] files, embedded as base64. If the font file is missing, stop and ask me.
Particles: about 3,200 tiny points with varied opacity and a faint twinkle, like a night sky. Build the number's shape by drawing "[NUMBER]" in the bold weight on an offscreen canvas and sampling its filled pixels as targets. Give most points to the number so it reads crisply at feed size, comma included. The rest stay as dimmer drifting stars.
Timing:
1. 0-2s: points drift. Nothing else.
2. 2-6.5s: points pull into the number with a long, staggered ease, like gravity, not a snap.
3. 6.5-7.5s: a thin [ACCENT] line draws left to right under the number.
4. 7.5-8.5s: the label fades in and rises about 12px into place.
5. 8.5-10.5s: hold. The number only shimmers.
6. 10.5-12s: label and line fade, points drift back to their exact start. Frame 12 matches frame 0.
Build rules: a fixed random seed for every position. Add window.seek(seconds) that draws any exact frame from the time alone. Reduced-motion shows the held frame.
After the build: capture frames at 0, 2, 4.5, 6.5, 7.5, 9.5, 11 and 12s. Check the number reads exactly "[NUMBER]", nothing is cut off or overlapping, and frames 0 and 12 are identical. Keep each earlier version when you fix something.What I learned the hard way
- The number looked grey at feed size. Too few points covered each digit. The fix: about 2,700 of 3,200 points on the number, each 2.5px at near full opacity.
- Chrome can draw the same frame two ways. After repeated pixel reads it switches drawing mode, so a frame came out slightly different. Create the canvas context with
willReadFrequently: trueand every seek gives the same pixels. - Seed everything. A
Math.random()at render time makes every export different and breaks the loop. - Measure the seam, do not eyeball it. My passing build had 0 pixels different between frame 0 and frame 12.
Step 3: Export
HyperFrames (free, open source): npx skills add heygen-com/hyperframes, then npx hyperframes render. 1080 x 1350 for the LinkedIn feed. For a Reel, hand the MP4 to reel-export. Put the source of the number in the caption.
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.

