Next AI Draw.io
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Precision PPT design skill for OpenCode/Claude Code/Codex, with 40,000+ styles, pixel-perfect Build Mode control, AI image generation, and fully editable PPTX. 面向专业演示设计场景,帮助用户从需求分析、视觉方向选择到原生可编辑 PPTX 交付,打造高质量、可持续修改的演示文稿。
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/sunchaokun-ppt-design-skill)同じ作業で 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 一覧と同じ並び
| これ PPT-Design-Skill | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| 作者 | sunchaokun | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub スター | 511 | 112,544 | 68,069 | 32,514 | 30,030 |
| 最終コード更新 | 2026年9月16日 | 2026年11月18日 | 2026年11月13日 | 2026年6月24日 | 2026年10月30日 |
| ライセンス | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
sunchaokun による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
CodexOpenCode
提供元の README と repo のフォルダから判断
GitHub account sunchaokun (person), 8 years old
★ 511 stars · code last changed 2026年9月16日
17 scripts that can run on a computer: scripts/audit_case_outputs.py, scripts/audit_prototype_provenance.py, scripts/audit_regression_pairs.py, scripts/audit_visual_review_records.py and 13 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 cbf7ef1 (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 cbf7ef1 · View on GitHub ↗
17 scripts
Once uploaded it runs on Claude’s systems, not on your computer. No need to unzip
All 56 files · 148 KB
SKILL.md19 KBagents/openai.yaml1 KBreferences/composition-recipes/c1-01.json1 KBreferences/composition-recipes/c2-01.json1 KBreferences/composition-recipes/c3-01.json1 KBreferences/composition-recipes/c4-01.json1 KBreferences/composition-recipes/composition_index.json1 KBreferences/content-schema.md1 KBreferences/design-direction-coach.md5 KBreferences/design-principles.md5 KBreferences/domain-paradigms.md2 KBreferences/install-and-runtime.md3 KBreferences/public-api.md5 KBreferences/qa-and-delivery.md6 KBreferences/scientific-visual-baseline.md4 KBreferences/template-brand.md3 KBreferences/visual-rendering-packs/dark-cinematic-tech.json2 KBreferences/visual-rendering-packs/editorial-infrastructure-ledger.json2 KBreferences/visual-rendering-packs/rendering_packs_index.json1 KBreferences/visual-rendering-packs/scientific-atlas.json2 KBreferences/workflow.md8 KBschemas/acceptance-record.schema.json1 KBschemas/composition-entry.schema.json2 KBschemas/composition-recipe.schema.json3 KBschemas/prototype-record.schema.json2 KBschemas/rendering-pack.schema.json2 KBschemas/runtime-trace.schema.json1 KBscripts/audit_case_outputs.py2 KBscripts/audit_prototype_provenance.py4 KBscripts/audit_regression_pairs.py3 KBscripts/audit_visual_review_records.py2 KBscripts/build_regression_baselines.py4 KBscripts/check_runtime.py1 KBscripts/check_scientific_baseline.py3 KBscripts/init_presentation_task.py3 KBscripts/inspect_pptx.py1 KBscripts/inspect_visual_assets.py3 KBscripts/refresh_case_prototypes.py5 KBscripts/render_pptx.ps16 KBscripts/run_visual_workflow.py3 KBscripts/runtime_deps.py2 KBscripts/validate_acceptance_record.py2 KBscripts/validate_runtime_trace.py2 KBscripts/validate_visual_pack.py12 KBtemplates/case-prototype-index.json2 KBtemplates/case-prototypes/README.md1 KBtemplates/regression-manifest.json1 KBtemplates/task-init/acceptance-contract.md1 KBtemplates/task-init/brief.md1 KBtemplates/task-init/page-plan.md1 KBtemplates/task-init/research.md1 KBtemplates/task-init/task.yaml1 KBtemplates/task-init/theme-lock.yaml1 KBtemplates/task-init/visual-direction.md1 KBtemplates/task-init/visual-review.md1 KBLICENSE1 KBコマンドを確認中 · 確認が通るとコピーボタンが出ます
+Create skillUpload a skillpick ppt-design-skill.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 を開き直し、/skill と入力するか関連する作業を頼むと Claude が自動で使います
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
ChatGPT デスクトップアプリには 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
ppt-design-skill フォルダを ~/.agents/skills/ppt-design-skill に置きます
~ はホームフォルダ($HOME)です
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Checked 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 のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
この文をコピーして 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 チャットで / を入力し skill を選ぶ
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Skill を読めるほかのアプリ向けです。この文には 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 フォルダを確認
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
最初の 8,000 文字を表示 · GitHub で全文を開く
---
name: ppt-design-skill
description: Design, generate, review, and revise editable PowerPoint presentations through a rigorous brief-to-PNG workflow using the public pptx-designer Python library.
metadata:
short-description: Design and visually review editable PowerPoint decks
category: design
tags: [ppt, powerpoint, presentation, deck, slides, design, python, editable]
---
# PPT Design Skill
This skill is a presentation design director and delivery workflow. The
`pptx-designer` Python package is the rendering engine; this skill decides
what should be designed, how it should be structured, how it should look, and
whether the rendered result actually satisfies the user's need.
The design framework below keeps the mature design judgment, content rules,
domain paradigms, and quality standards that make the workflow reliable. The
implementation engine is the public `pptx-designer` Python library.
## Designer mindset
Act as a senior presentation designer. Make decisions from the audience and
the communication goal, not from the list of available Python functions.
- **Audience first**: decide what the audience must understand, remember, feel,
or do before choosing a layout.
- **Restraint over decoration**: one clear accent system is better than random
effects; every element must earn its place.
- **Systematic thinking**: a deck is one visual system, not independent pages.
Lock margins, spacing rhythm, typography, color roles, corner treatment,
image treatment, and component language.
- **Intentional variation**: vary page architecture and density when the story
changes, not merely to make pages look different.
- **Explain decisions**: be able to state why a page uses a figure, chart,
comparison, diagram, image, or sparse statement for this audience.
## Stop before writing code
For a new delivery-grade presentation task, initialize the task from
`templates/task-init/` and keep task-specific requirements in those task
files. Run `init_presentation_task.py` from the loaded Skill's `scripts/`
directory (use its absolute path if the working directory is the project):
`python <skill-root>/scripts/init_presentation_task.py --project <project-root>
--name <lowercase-task-slug>`. It creates an isolated
`<project-root>/ppt_tasks/<task-slug>/` and refuses to overwrite it. Do not
begin implementation while a required research or direction decision remains
unresolved.
For a delivery-grade deck, do not write the build script until these decisions
are explicit:
- topic, audience, scenario, language, and desired action;
- domain paradigm;
- page count and page-by-page goals;
- visual direction and design tokens;
- when supplied, reference qualities stated as observable features, their
intended transfer, and the final PNG evidence that will demonstrate them;
- variance, motion, and density levels;
- generation mode: FreeStyle `generate_ppt()`, Build Mode, or VI Build Mode;
- image and template constraints;
- the user's confirmation of the structure and visual direction.
The only acceptable shortcut is an explicitly requested quick exploratory draft.
## Non-negotiable outcome
A PPTX file that merely runs successfully is not complete. A task is complete
only after the deck has been rendered through the confirmed `PPTX -> PDF ->
PNG` path, the LLM has inspected the PNG output, material visual issues have
been revised, and the user has confirmed the final direction or result.
## Workflow
1. Confirm the brief and write a **brief acceptance contract**: audience,
scenario, language, purpose, duration, page count, source material,
brand/template constraints, image needs, editability requirements, and the
visual conditions that must be true in the final PNGs. Classify each
condition as `MUST`, `SHOULD`, or `NICE_TO_HAVE`.
2. Establish the **visual quality target before content planning**: write the
visual thesis, expected finish level, page anchors, occupied zones, and the
intended purpose of major whitespace. When reference material is supplied,
convert its observable qualities into transfer decisions and PNG evidence;
do not reduce it to vague style labels or mechanically copy its content.
Run a thumbnail preflight; a page without a focal point or a complete visual
composition is not ready for content or code.
3. Detect the domain and set the design read: page goal, core takeaway, content type, and
relationship to surrounding pages. The domain must refine the visual target,
not reduce it to a generic template.
4. Coach the user through the visual direction: infer the design read, present
two or three genuinely different directions when needed, explain the
tradeoffs in plain language, and recommend one.
5. Lock the selected direction in a versioned **Theme Lock**: mood, visual
thesis, palette intent, typography intent, grid, spacing, density, image
treatment, chart language, page archetypes, and forbidden patterns. A Theme
Lock is a project design record, not a `pptx-designer` API object. Resolve
it once with `ThemeComposer.compose(...)`, save the resulting complete
**resolved theme**, and pass that object to the generation API.
6. Present the structure and visual direction for confirmation before building
a delivery-grade deck, unless the user explicitly requests a one-shot draft.
7. Generate a reproducible Python build script or structured `content` using documented public
`pptx_designer` APIs. Record the Theme Lock version, resolved-theme source,
seed, package version, and module path with the generation result.
8. Run the generation path and perform basic structural checks.
9. Export the PPTX to PDF and PNG using `skill/scripts/render_pptx.ps1`.
10. Inspect the rendered PNGs directly using two gates. **Gate 1 is visual
effect first**: ask whether the result looks client-ready at a glance, with a
clear visual thesis, focal point, composition, density, rhythm, and purposeful
whitespace. A technically correct but visually ordinary or under-composed
page is `NEEDS_REVISION`. **Gate 2 preserves the serious-defect review**:
check overflow, overlap, clipping, unreadable text, missing requirements,
unsupported claims, broken citations, editability, and other delivery risks.
11. Check every page against the brief
acceptance contract; use a contact sheet only as an overview, never as the
sole review for a delivery deck.
12. Record requirement-by-requirement evidence: `PASS`, `NEEDS_REVISION`, or
`BLOCKED`. Do not replace this comparison with a generic aesthetic opinion.
13. If the PNG review finds a material issue or a failed `MUST` condition,
identify the source-code/content cause, revise, regenerate, and inspect
again. Return to the failed decision level: revise the visual direction,
composition, or asset strategy for a directional failure; use local edits
only for a local defect. A deck is not complete while a `MUST` condition is
unresolved.
14. Present the reviewed PNGs or contact sheet and the acceptance result for
user confirmation, then deliver the PPTX, source script, PDF, and PNG
preview directory.
## Design read: variance, motion, density
Set three 1-10 dials before choosing layouts:
- **Variance** controls structural variation. Low variance uses a consistent
grid and component family; medium variance mixes two or three strategies;
high variance permits section dividers and distinct page architectures.
- **Motion** controls animation ambition. Low motion uses no animation or fade;
medium motion reserves transitions for section changes and emphasis; high
motion is only appropriate when the delivery context supports it.
- **Density** controls information load. Low density uses generous whitespace
and one or two major elements; medium density mixes narrative and data;
high density uses dashboards, tables, and carefully organized grids.
These dials change composition, not just colors. They must remain compatible
w質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。