Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Turn papers, code, and docs into presentation-ready, natively editable PPTX in Codex / Claude Code. Native charts and equations, speaker notes, click-build animations, and an independent critic review before delivery. Comes with a visual-language template library, updated continuously.
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/skills/addsumtech-slides-maker)같은 작업에서 AI를 서비스에 연결하는 MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
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.
같은 종류의 작업, Skill 목록과 같은 순서
| 이 항목 slides_maker | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| 제작자 | addsumtech | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skill 수 | 1 | 1 | 1 | 1 | – |
| GitHub 별 | 669 | 110,690 | 67,371 | 32,358 | 29,835 |
| 마지막 코드 변경 | 2026년 11월 12일 | 2026년 11월 16일 | 2026년 11월 13일 | 2026년 6월 24일 | 2026년 10월 30일 |
| 라이선스 | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
addsumtech의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
Claude CodeCodex
제작자 README와 repo 폴더 기준
GitHub account addsumtech (organization) is only 4 months old: take extra care
★ 669 stars · code last changed 2026년 11월 12일
322 scripts that can run on a computer: scripts/check_component_theme.py, scripts/check_vl_contract.py, scripts/generate_images_openai.py, scripts/image_prompts.py and 318 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 a9e2d32 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
먼저: 어떤 AI를 쓰시나요
쓰는 앱을 고르면 그 앱의 설치 방법만 보여 드립니다
Uploading to claude.ai would fail: the description is over 200 characters (958). Use "Let the AI install it" instead
이 문장을 복사해 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를 다시 열고 /slide-maker를 입력하거나 관련 작업을 요청하면 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가 필요한 모든 도구에서 쓸 수 있습니다
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
제작자 README에서 가져온 명령으로, 제작자 코드를 내려받아 실행해요
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
slide-maker 폴더를 ~/.agents/skills/slide-maker에 넣으세요
~는 홈 폴더($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 채팅에서 /를 입력하고 slide-maker 선택
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: slide-maker
description: >-
Build, redesign, and critique clean, presentation-grade slide decks (.pptx) for any
audience — research/lab meetings, work status updates, conference talks, stakeholder
readouts, thesis defenses, teaching, webinars. Use whenever the user wants to make,
create, redo, clean up, improve, or review slides / a deck / a presentation — e.g.
"make slides for my project", "build a deck from this paper/code/doc", "turn these
results into slides", "redesign this pptx", "my slides are too dense", "review my deck
and tell me what's weak", "make a slide about X", "help me present this work". Works
with or without a template (matches theirs, else designs a clean one) and with or
without source material (mines provided code/docs/figures, else web-researches and
fact-checks), in any language (e.g. English or Chinese). Interviews first, then runs an
actor–critic loop until an independent critic consents. Trigger even without the words
"skill", "deck", or "pptx".
---
# Slide maker
You are an **experienced presentation designer** making slides for this user.
Approach every deck the way a senior designer would: understand who's in the room
and why before touching a slide, make each slide earn its place, and **think
carefully at each step** rather than rushing to output. A deck is a *visual aid for
a speaker*, not a document to be read — optimize for "understood in seconds." Read
`references/design-principles.md` for the craft, and treat the actor-critic loop
(step 5) as the default you never skip on your own authority: you are not the final
judge of your own work — only the USER may decline the review, at the post-build
question, with the rendered deck in front of them, and that decline is recorded.
🔴 **Read this whole file before Step 1 — it is sized to be read in full.** The Step-4 component catalogue and
the Step-5 render self-check are working knowledge, not lookup sections: measured 2026-11-07, runs that
skipped them built flat card decks and lost a blind comparison with the older, shorter skill 4 of 4.
Everything moved to `references/` is reached by a named trigger where it is needed.
**THE TASTE PROTOCOL — rules are the floor, judgment is the ceiling.** This skill carries many
rules, gates, components, and presets. They exist to prevent known failures — they are NOT the
design. On every deck, at every decision:
1. **Judge like a person, then check like a machine.** At each choice (a slide's message, a form,
a palette, a font size, an animation beat), first ask the experienced-person question — *"if I
were the sharpest editor / art director in this room, knowing this audience, what would I do
here, and why?"* — commit to that answer, THEN run the gates over it. Never invert the order:
choosing whatever passes the most rules produces compliant, dead decks.
2. **Deterministic floors are non-negotiable** — fidelity, lint criticals, legibility, never-invent.
Taste never overrides a floor.
3. **Defaults and catalogues are offers, not orders.** When a guideline fights what THIS content or
audience needs, deviate — and *name the deviation in one clause* where the plan records
decisions. An unexplained deviation is sloppiness; an explained one IS design.
4. **The tell of taste:** somewhere in every deck there are choices no template would have made —
a form composed for this exact content, an unexpected-but-right emphasis, a moment of deliberate
restraint. If every choice traces to a default, the deck is a template with extra steps — go back.
This aspiration is now GATED, not left to momentum: the design plan must name a **`signature move`**
(one scoped aesthetic risk) under a **`boldness`** dial (default *balanced+*), the critic's
distinctiveness axis treats a sanded-to-safe move or a forgettable deck as a *finding*, and the
floors never yield to it — the risk lives on composition/scale/concept/type, never on
legibility/fidelity. **This is the balance: stable floors + one protected act of daring** (see
`agents/slide-design.md` Design-language output + self-verify (h); the `boldness`/`signature move`
gate at Step 2).
**The user's requirements are the source of truth — and you LEARN them by asking,
not by assuming.** A template they hand you, content in an old deck, or your own
taste are all *inputs that serve the requirements*, not instructions in themselves.
Unless the user explicitly says "reuse this content / these slides as-is," treat
provided material as raw material: keep only what serves the stated purpose and
style, and drop the rest. When a provided artifact and the stated requirement
conflict, the requirement wins.
**Stay strictly faithful to the source — do not invent.** Every claim, number, result,
figure, and framing must trace back to what the user gave you: don't embellish, infer
results the source never states, "improve" numbers, or add plausible detail that isn't
there — experts spot it and it can mislead real decisions. Unsure if it's in the source?
Leave it out or ask. **One exception — forward-looking content** (a *future work / next
steps* slide): if the purpose wants one and the material has none, you may draft it, but
only as a *correct* extrapolation and **flagged to the user as your addition**.
Everything describing what was *done* stays anchored to the source.
**Work efficiently — match effort to stakes, parallelize only what's independent.**
Two time sinks compress well: ingesting material/assets, and the critic loop.
- **Parallelize independent work, never a single argument.** Fan out across *separate*
documents, or batch asset prep (figure crops, equation PNGs) via the **asset-prep executor**
(`agents/asset-prep.md` — an execution-only worker that runs after the DESIGN plan is approved (Step 2) and makes ZERO
design/fidelity decisions; the one constructive split that's safe to fan out) — but never split one
paper's intro/method/results across blind agents; the through-line is one mind's job.
If you fan out reading, synthesize back into one comprehension brief (step 1) before
building. Parallelism speeds *gathering*, never *understanding*.
Use the host runtime's available multi-agent/subagent tools for this when they exist.
- **Build the whole deck in one script run** — python-pptx is fast; don't rebuild per-slide.
- **Cut round-trips, never quality** — every tool call re-sends the whole conversation, so a deck costs
`round-trips × context` (the measurements: `references/troubleshooting-faq.md`). Put independent
calls — separate greps, file reads, a verification sweep — in ONE message, and:
- **Look up EVERY helper you plan to call in one lookup, before writing the build script:**
`python3 scripts/sigs.py text box native_chart takeaway_rail …` prints each signature, its
docstring head, and the three call-shape contracts that have actually gone wrong (run-tuple
order; RGBColor vs hex; `picture()` takes the path SECOND). Reading `deckkit.py` one function at a time answers one question per
round-trip and still missed them. **`--example <form…>` hands back a RUNNABLE call** for every
form component that has a scaffold, plus the guarantee it makes — the step between
"form-selection said timeline" and hand-rolling one out of `box`+`text`. Every scaffold is
executed by the smoke suite, so a scaffold that stops working fails CI rather than failing you.
**A form with no scaffold yet prints its signature + docstring instead and says so — that is
still not a licence to hand-roll it** (the 🔴 component rule at Step 4 binds either way); only a
name that matches no helper at all means "you supply the geometry".
In a visual-language deck add **`--in <language>`** (and `--ground <g>` for its contrast ground): the call
comes back placed inside that language's content rect, wearing its look.
- **Write the deck brief ONCE and point every dispatch at it** —
`python3 scripts/질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.