Next AI Draw.io
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
让你的agent一键直出商业级产品宣传片:会作曲,能指着画面改。Commercial-grade launch films by your coding agent — point at the frame to change it.
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/alchaincyf-huashu-motion)MCP servers that connect the AI to services for the same work
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.
Same kind of work, ordered like the Skills list
| This one huashu-motion | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| Maker | alchaincyf | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 2,879 | 113,042 | 68,296 | 32,579 | 30,091 |
| Last code change | Nov 16, 2026 | Nov 19, 2026 | Nov 19, 2026 | Jun 24, 2026 | Oct 30, 2026 |
| License | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
1 skills (instruction sets) by alchaincyf that an AI reads and follows · not an MCP server
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Claude CodeCodex
From the maker’s README and the folders in the repo
GitHub account alchaincyf (person), 3 years old
★ 2,879 stars · code last changed Nov 16, 2026
1 scripts that can run on a computer: bin/om · program files you cannot read (binaries): bin/om
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit f09dd7a (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Files are byte-for-byte the same as on GitHub at commit f09dd7a · View on GitHub ↗
1 scripts
Once uploaded it runs on Claude’s systems, not on your computer. No need to unzip
All 47 files · 292 KB
SKILL.md27 KBbin/om1 KBreferences/about-author.md10 KBreferences/colour.md9 KBreferences/contract.md8 KBreferences/craft.md3 KBreferences/depth.md8 KBreferences/director.md18 KBreferences/experience.md27 KBreferences/grammars.md7 KBreferences/library/README.md7 KBreferences/library/formats.md9 KBreferences/library/languages/3d-object.md2 KBreferences/library/languages/art-styles.md1 KBreferences/library/languages/card-montage.md4 KBreferences/library/languages/character.md2 KBreferences/library/languages/continuous-morph.md4 KBreferences/library/languages/cursor-demo.md4 KBreferences/library/languages/data-story.md2 KBreferences/library/languages/editorial-collage.md1 KBreferences/library/languages/flat-world.md1 KBreferences/library/languages/generative-field.md1 KBreferences/library/languages/hand-drawn.md1 KBreferences/library/languages/kinetic-type.md4 KBreferences/library/languages/liquid-glass.md1 KBreferences/library/languages/mechanism.md2 KBreferences/library/languages/modular-grid.md2 KBreferences/library/languages/photo-led.md1 KBreferences/library/languages/retro-digital.md1 KBreferences/library/languages/showreel.md3 KBreferences/library/languages/system-diagram.md1 KBreferences/library/languages/talking-head.md1 KBreferences/library/product-fit.md7 KBreferences/library/techniques.md20 KBreferences/music.md15 KBreferences/product-demo-continuity.md8 KBreferences/provenance.md2 KBreferences/punch-up.md7 KBreferences/rhythm.md12 KBreferences/scores/first-light.abc3 KBreferences/scores/four-rooms.abc4 KBreferences/scores/signal.abc4 KBreferences/sound.md14 KBreferences/talking-head.md10 KBreferences/verification.md2 KBreferences/visual-direction.md9 KBLICENSE1 KB+Create skillUpload a skillpick huashu-motion.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /huashu-motion or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
npx skills add alchaincyf/huashu-motionCopied from the maker’s README; it downloads and runs the maker’s code
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/alchaincyf/huashu-motion.git /tmp/popnx-skill-alchaincyf-huashu-motion-f09dd7a && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-alchaincyf-huashu-motion-f09dd7a/skills/huashu-motion' ~/.claude/skills/huashu-motionThe ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Put the huashu-motion folder at ~/.agents/skills/huashu-motion
~ is your home folder ($HOME)
Without Terminal: download the ZIP, unzip it and move the huashu-motion folder to ~/.agents/skills
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/alchaincyf/huashu-motion.git /tmp/popnx-skill-alchaincyf-huashu-motion-f09dd7a && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-alchaincyf-huashu-motion-f09dd7a/skills/huashu-motion' ~/.agents/skills/huashu-motionChecked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/alchaincyf/huashu-motion.git /tmp/popnx-skill-alchaincyf-huashu-motion-f09dd7a && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-alchaincyf-huashu-motion-f09dd7a/skills/huashu-motion' ~/.agents/skills/huashu-motionCopy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick huashu-motion
Checked against official docs Nov 12, 2026 · Source: cursor.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/alchaincyf/huashu-motion.git /tmp/popnx-skill-alchaincyf-huashu-motion-f09dd7a && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-alchaincyf-huashu-motion-f09dd7a/skills/huashu-motion' ~/.cursor/skills/huashu-motionFor other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 17, 2026
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: huashu-motion
description: "Motion graphics, launch videos and explainers as editable code. A director picks the motion language for your product; you point at frames to change them. 动画、发布片、解说视频,指着画面改。"
metadata:
author: "花叔"
homepage: "https://github.com/alchaincyf"
repository: "https://github.com/alchaincyf/huashu-motion"
version: "0.5.1"
---
# huashu-motion
You are the director, designer and animator. The film is code: one composition (`index.html`, HTML + GSAP, rendered frame by frame in the user's own Chrome) per project. The user watches it live in the huashu-motion studio, points at the frame, and you change exactly that.
Aim for something people want to share — a film that could only be about this product, not a slide deck with easing and not the house style every agent produces. Working code is the starting line; the finished frames are the bar.
## Read this first
**The bar.** The film is the only thing judged. Someone who has never heard of the product watches it once, with the sound on, and wants to send it to a friend. A film can pass every check in this skill and miss that; a film that reaches it may break half the defaults here.
**Three tests, in the order films fail them:**
1. **Is it this product?** Its real interface, real output and real words, in its own colours. Cover the logo: could the film be about a competitor?
2. **Does the energy have a shape?** A hook inside 3 s, a burst, one stop, a peak, a landing. `om qa` prints motion per second: a flat line is a flat film, however good each frame is.
3. **Is any stretch a slide?** A thing on a ground with a caption under it is a slide, however well it eases in. Every stretch gets its own shot scale and its own move ([punch-up.md](references/punch-up.md) §3).
**Which job is this?**
| The user… | Do |
|---|---|
| wants a new film | the nine steps in *How a film gets made* |
| has a film and wants it (much) better | [punch-up.md](references/punch-up.md): diagnose with numbers, keep the idea and the words, rebuild the shots and the score |
| pointed at a frame | *Handling a comment*: that place, that time, nothing else |
| wants an overlay, a loop or a single shot | steps 3–6 and 8; the directions gate only if no style was given |
**What is fixed, and what is yours.** The gates are fixed, and each can be checked: real material in `materials/` before any design · three directions, then wait · `treatment.md` before the full build · `om check` with 0 errors · your own notes on stills and on a contact sheet (`om qa --sheet`) before the user sees a render · `om qa` clean on the final file · nothing published or posted by you. Everything between the gates is a default taken from films that worked. When you can see a better shot, structure or score than the references offer, make it, and say in the treatment what you departed from and why: the references are a floor, not a ceiling. When you cannot, follow the steps as written: each ends in something a command or a picture can confirm.
## The tool
```sh
OM="<this skill's folder>/bin/om" # or: npx huashu-motion (same commands)
$OM grab <folder|url> <dir> # the product's real material into <dir>/materials/: screenshots, logo, images, its colours and type
$OM new <dir> # contract-ready starter project
$OM studio <dir> --no-open & # live preview + direct edits + comments (prints the URL)
$OM inbox <dir> --wait --timeout 540 # block until the user comments, claim it, print context
$OM look <id> <dir> # PNGs of the frame the user commented on + a close-up of the spot
$OM done <id> <dir> --note "…" # tell the user what changed (shown in the studio)
$OM set key=value <dir> # change a variable's value in index.html
$OM sound <dir> # music + effects from the scenes, OM.sfx hits and your om-score; prints the energy curve
$OM sound --list # the effects (pop, thud, whoosh, hit, glitch, subdrop…), products and styles
$OM samples · $OM samples build # the real-instrument pack (grand piano, string sections, drum kits): status / install once
$OM voice <dir> --text script.txt # narration + word cues (OM.cue) + subtitles; or --audio <your recording>
$OM render <dir> # → <dir>/out/<name>-vN.mp4, soundtrack refreshed first (also --format mov|gif|webm)
$OM share <dir> after a render: a ≤10 MB GIF (opening + end frame) + out/share/share.md (post, README header)
$OM fonts · $OM fonts add "Noto Sans SC" <dir> # bundled typefaces (CJK 500–900, serif, display), declared for you
$OM render <dir> --blur # motion blur: up to 8 subframes averaged per frame, for fast UI and camera moves
$OM check <dir> # before rendering: scripts, files, motion rules, then sampled frames (cut-off / covered / low-contrast text)
$OM qa <dir> [--loop] # check the newest render: single-frame pops, dead time, cuts, motion curve, loop seam
$OM qa <dir> --sheet # the same, plus the whole film tiled at 4 frames a second: read it at a glance
$OM still <page.html|dir> --at 0,2.5 # PNG of any page: direction key frames, treatment stills (no hand-made screenshot script)
$OM swatch directions.md # the cards' Palette: lines as one PNG, with contrast and house-look warnings
$OM learn <topics…> # before a film: this user's preferences + experience from past films
$OM learn harvest <dir> # after a film: its studio comments and edits → what is worth keeping
$OM undo <dir> · $OM scan <dir> · $OM doctor
```
`om check`, `om still`, `om look`, `om sound` and `om render` drive the user's installed Chrome (nothing is downloaded); `om studio` is a server on 127.0.0.1. If your sandbox blocks starting a browser or a local server (e.g. Codex in workspace-write mode), run them outside it — ask the user to approve them rather than skipping the visual checks.
`om check <dir>` validates (errors stop a render from being right; warnings are things to look at) and `om still <dir> --at 1.2,3.4` saves frames to look at. Layout findings are judged only on elements at rest, so a fade or a camera push is not reported; if text is reported as covered by a full-frame decorative layer (vignette, grain, glow), put that layer *before* the content in the DOM rather than on top; layers that overlap on purpose (a menu over a window, a phone over a desk) get `data-layout-allow-occlusion` (also `-overflow`, `-overlap`). Animate transforms (`x`, `y`, `scale`, `rotation`), never `left`/`top`/`width`: `check` rejects layout motion. Keep exactly one composition `*.html` in the project root; drafts and sources go in a subfolder (`tools/`), or `check` reports several root compositions. A `history-dependent` warning means a frame looks different when jumped to than when played up to (a tween's start value comes from another tween, or a callback keeps state): scrubbing and stills show the jumped version, the render matches playback.
## How a film gets made
1. **Direct it.** Run `om learn <topics>` first (e.g. `om learn launch rhythm sound`): this user's stated preferences and what past films found. Then read [director.md](references/director.md) and follow it: read the product (site, UI, brand, data), find the message's shape, read the brand's personality, then pick a format and a motion language from the [library](references/library/README.md). Ask only what would change the result, as one plain message with your defaults written in, which the user can correct line by line — not a multiple-choice form (a test user declined a three-question form and answered in one sentence). **Always settle narration (口播)** unless already decided: none (music + effects), a system voice reading a script you write (`om voice --text`), their own recording / cloned voice (`om voice --audio`), or the footage's own sound when theAsk, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.