Next AI Draw.io
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Cinematic launch films and motion design from code, directed by your coding agent.
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/leonxlnx-cinetic)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 cinetic | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| Maker | Leonxlnx | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 1,261 | 111,852 | 67,796 | 32,458 | 29,958 |
| Last code change | Nov 9, 2026 | Nov 17, 2026 | Nov 13, 2026 | Jun 24, 2026 | Oct 30, 2026 |
| License | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
1 skills (instruction sets) by Leonxlnx 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 CodeCodexCursor
From the maker’s README and the folders in the repo
GitHub account Leonxlnx (person), 1 years old
★ 1,261 stars · code last changed Nov 9, 2026
404 scripts that can run on a computer: scripts/accumulate.py, scripts/add-font.mjs, scripts/brand-kit.sh, scripts/check-sync.py and 400 more
Could not check every script (some are too large); read them first
No hooks or writes to machine settings found
Checked automatically from the repo files at commit f4bbfc8 (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
Uploading to claude.ai would fail: the description is over 200 characters (802). Use "Let the AI install it" instead
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 /cinetic 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 Leonxlnx/cineticCopied 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/leonxlnx/cinetic.git /tmp/popnx-skill-leonxlnx-cinetic-f4bbfc8 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-leonxlnx-cinetic-f4bbfc8/skills/cinetic' ~/.claude/skills/cineticThe 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 cinetic folder at ~/.agents/skills/cinetic
~ is your home folder ($HOME)
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/leonxlnx/cinetic.git /tmp/popnx-skill-leonxlnx-cinetic-f4bbfc8 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-leonxlnx-cinetic-f4bbfc8/skills/cinetic' ~/.agents/skills/cineticChecked 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/leonxlnx/cinetic.git /tmp/popnx-skill-leonxlnx-cinetic-f4bbfc8 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-leonxlnx-cinetic-f4bbfc8/skills/cinetic' ~/.agents/skills/cineticCopy 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 cinetic
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/leonxlnx/cinetic.git /tmp/popnx-skill-leonxlnx-cinetic-f4bbfc8 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-leonxlnx-cinetic-f4bbfc8/skills/cinetic' ~/.cursor/skills/cineticFor 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: cinetic
description: Direct, build and render premium motion films from code - launch films, update films ("vX is out"), product and feature videos, looping feature animations, logo stings, UI walkthroughs, teasers and promo clips. Use this whenever the user wants any video, animation, motion graphic or animated demo made with Remotion, HyperFrames, HTML/GSAP or React, or asks to storyboard, time, score, render, polish or critique one - even if they only say "make a video about X", "animate this feature" or "we need a launch clip". It supplies a default path one agent finishes in one to two hours, scenes dealt from a house bank, plain-word copy checked by script, one face with rotating voices, flowing seams, real product UI, current official logos, a licensed track with recorded effects and film-grade finishing.
license: MIT
compatibility: Needs Node 22+, ffmpeg 6+ with libx264, Python 3.11+ with numpy, scipy, soundfile, pyloudnorm, opencv-python and librosa (fonttools, brotli and uharfbuzz for outlined logos; pillow for plates), and Chromium or Chrome Headless Shell for rendering; earshot 0.4+ (in its own virtualenv) listens to the effects and the soundtrack. Works with Remotion 4 (React) or HyperFrames (HTML and GSAP).
---
# cinetic
You are directing a short film, not animating a web page. Picture, words and sound are one system driven by one
timeline file; nothing is finished until rendered, measured and reviewed once against the standard below.
- **Engines.** Remotion 4.0.529 (React, frame-driven) is the default. HyperFrames 0.8.79 (HTML, a paused GSAP timeline) mirrors the tokens and timeline contract for HTML projects ([hyperframes-engine.md](references/hyperframes-engine.md)).
- **Paths.** Scripts work from the skill root and in a film project (`new-film.sh` copies them in); each prints `--help` (not the helpers `brand-svg.ts`, `hf-preflight.cjs`).
- **Brand.** A supplied brand (logo, colours, fonts, screenshots, tone) wins over the house taste ([brand-kits.md](references/brand-kits.md)); record any banned look it brings in `BRIEF.md`.
- **Python.** Commands say `python3`: `node scripts/frames.mjs python` names the interpreter with `scripts/requirements.txt`; set `PYTHON` to it once.
## The standard
Every film is held to these rules and numbers; the gates in brackets measure them.
1. **Words in the middle.** A statement is centred and sits in the middle band of the frame (its centre at 35-65 % of
the height): centred for 80 % of the statement time or more, in the middle band for 85 % or more. Centred top or
bottom only over a full-bleed picture. Never flush left at the top or the bottom. "Text on top, big picture below"
at most once a film; a line beside, above or below a picture at most once per 30 s. (`layout-audit.sh` placement.)
2. **One element carried, the text mixed in.** Every scene change hands one element on (it grows, swells, flies,
converges): never a cut from a line to a card, never the line-card-line-card loop, never an empty frame between
scenes. Lines alone only for the promise and the claim (read in 1.2 s); between them inside the product's own words or
around the element; first line by 1 s. (`grid-check.ts --part spine`, `forensics.py --spine`, empty-frame.)
3. **The picture tells what the product does.** Each picture proves its line without repeating its words (input ->
output, a count rising; "every" drawn as many at once); a line its picture already says is cut (`copy-check`
repeats, quantity). The first picture beat shows the core action literally, with a real person giving the input where the input is human (real footage or a photo),
and the product's main act plays on screen (the input becoming the output in steps, never a cut from the request to
the finished result); what it makes is rich and holds the brief's own subjects. With the words covered, every
picture beat still reads. Data agrees when paused: newest first in a stack, counts and times that agree, a
face with its own name (`precheck.mjs` cast).
4. **Less text, every word chosen.** 1-5 words a line typically, 2-7 at most, one claim, plain words a customer would
use; 0.3-1.5 headline words a second; what the product is by 3 s. No text in 15 % of the frames or more; at most two
text blocks at once outside a product beat; no floating chips, counters or captions beside a statement.
(`copy-check.py`, `--ui src`.)
5. **Text with love: one face, voices that rotate, events.** Lines arrive in the film's one face, the voice turning
line by line (build, blur-in, ink-in: never two lines in a row alike, [catalogue.md](references/catalogue.md) §1),
big (a line alone at a 9.2 % cap, never under 6.5 %; the claim bigger), whole or in 2-3 chunks, never word by word.
One type event a film (a giant word with the product rising behind it, a line an object pushes apart, a
decode, a build that re-centres). Emphasis is quiet: the key word in the accent on at most two lines, not always the
last word; a box, marker, pill, underline or knockout only as the one signature. Every line reads at 3:1 against
what is behind it, never held up by a grey halo. (`lint-film.mjs` emphasis, `forensics.py` legibility.)
6. **Scene changes that flow.** Every hard cut hides itself: inside a blur making both sides unreadable, an anchor
held within 10 px, or a whip carrying the picture a fifth of the frame in its last 0.2 s, smeared; the kept
ground alone hides nothing; never a cross-fade of two scenes or a cut torn across two frames; at most 10 % of hard
cuts bare (`forensics.py` carried-cut, ghost-cut). One ground a film, changed once on purpose at most (a colour flood; grid-check `grounds`). Two or three seam kinds a film, none
over 40 % of the scene changes, and one exit-then-enter, text-swap or match-cut in a film of four lines or more.
Build them with `fx/Seam` ([transitions.md §2](references/transitions.md#2-recipes-at-60-fps)). (`forensics.py --seams`.)
7. **Clean UI.** The product's real screens built in code at film size, every string the product's own: no bracket
slot, no stand-in number, no kit sample, no title cut with "...". Left edges of stacked rows within 4 px, inner
padding about 2.4 cap heights and even (never under 0.8), no text touching an asset, no accent bar beside a card;
widths measured, never guessed from a letter count (`lint-film.mjs`, `layout-audit.sh`).
8. **Logos current, presented well.** Other products' marks come from `scripts/logos.mjs` in their newest official
form, verified on the brand's own page within 12 months, in one presentation a film (a chip in the line, pills round
a centred line, or a wall), never a pill on every line or a drawn stand-in for a real mark (`logos.mjs check`). The end card is built from the
film's last element (the last picture's element becomes the mark, the last word the wordmark, the badge spins in),
lands centred and keeps creeping in about its centre (never a slide off it) while the music rings out and the frame
settles out with it, the name once and the one fact under it. The logo is the brand's own, never a sparkle, a star or a
generic glyph (`forensics.py` end-drift, end-centre, audio-end).
9. **Its own film, never a template.** One world for the whole film, one face and its voices, two
or three moves, two or three seam kinds, one signature and one end-card design, picked from
[catalogue.md](references/catalogue.md) and declared in `film.json`. The world (kind and hue), the voice, the signature
and the end card differ from each of the last three films, and the move set shares at most 25 % with each of them; a film
made from a template plays another device than its floor in half its slots or more. (`film-diff.mjs`; the deals
leave the last films' choices out.)
10. **Premium, not just clean: every shot keeps the habits.** One sharp plane and a graded blur ladder behind it; one
camera move with a job, fAsk, 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.