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.
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/alchaincyf-huashu-motion)同じ作業で AI をサービスにつなぐ MCP
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.
同じ種類の作業。Skill 一覧と同じ並び
| これ huashu-motion | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| 作者 | alchaincyf | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub スター | 2,864 | 112,544 | 68,069 | 32,514 | 30,030 |
| 最終コード更新 | 2026年11月16日 | 2026年11月18日 | 2026年11月13日 | 2026年6月24日 | 2026年10月30日 |
| ライセンス | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
alchaincyf による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
Claude CodeCodex
提供元の README と repo のフォルダから判断
GitHub account alchaincyf (person), 3 years old
★ 2,864 stars · code last changed 2026年11月16日
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
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
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 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
この文をコピーして Claude Code のチャットに貼り付けます
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
Claude Code を開き直し、/huashu-motion と入力するか関連する作業を頼むと Claude が自動で使います
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
もう入っていますか?先に確認 · ターミナルを開き、このコマンドを入力して Enter
node -vMac:⌘ + Space を押し、Terminal と入力して Enter
Windows:スタートメニューを開き、Windows PowerShell と入力して「開く」
まだ入っていない場合: 公式ダウンロードページで LTS 版と、クリックで進むインストーラーを選びます:Mac は .pkg、Windows は .msi。ダブルクリックして最後まで進めるだけで、curl コマンドは不要です
入れ終わったらターミナルを閉じて開き直し、同じコマンドをもう一度実行します。バージョン番号が出れば完了です: node -v
一度入れれば、Node.js を使うすべてのツールで使えます
npx skills add alchaincyf/huashu-motion提供元の README から引用。提供元のコードをダウンロードして実行します
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、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-motionChatGPT デスクトップアプリには Codex が組み込まれていて、Codex は ~/.agents/skills フォルダから Skill を読み込みます
ChatGPT デスクトップアプリで Codex を開き、この文をチャットに貼り付けます
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
huashu-motion フォルダを ~/.agents/skills/huashu-motion に置きます
~ はホームフォルダ($HOME)です
ターミナルを使わない場合:ZIP をダウンロードして展開し、huashu-motion フォルダを ~/.agents/skills に移動します
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、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 2026年11月15日 · Source: learn.chatgpt.com
自分でインストールした Skill は使えません。ディレクトリのプラグインに含まれる Skill だけが使えます
この Skill を ChatGPT で使うには、上の方法で ChatGPT デスクトップアプリを使ってください
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
この文をコピーして Codex のチャットに貼り付けます · ChatGPT デスクトップアプリ内の Codex、Codex CLI、IDE 拡張機能で使えます
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 は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください · 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、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-motionこの文をコピーして Cursor のチャットに貼り付けます
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
Cursor の Agent チャットで / を入力し huashu-motion を選ぶ
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、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-motionSkill を読めるほかのアプリ向けです。この文には Claude Code、Codex、Cursor のパスが入っていて、AI が使っているアプリに合わせて選びます · 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 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、SKILL.md のあるフォルダをコピーしてください。
2026年11月11日 に Claude Code、Codex、Cursor の公式ガイドで skill フォルダを確認
✓ コマンド確認済み 2026年11月17日
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
最初の 8,000 文字を表示 · 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 the質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。