From project-to-marp
Create a Marp presentation (markdown slides) introducing a project. Use when the user wants to make a presentation or slides about their project, codebase, or work. Triggers on requests like "make slides for this project", "create a presentation", "プレゼンを作って", "スライドを作りたい".
How this skill is triggered — by the user, by Claude, or both
Slash command
/project-to-marp:project-to-marpThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a Marp presentation introducing the current project with minimal user effort.
Create a Marp presentation introducing the current project with minimal user effort.
Write the presentation in the same language as the user's request/conversation, unless the user specifies otherwise.
Before anything else, check the current conversation for clues about the user's intent — what they want to communicate, to whom, or any constraints already mentioned.
Do a lightweight survey — just enough to ask informed questions:
Only ask what cannot be reasonably inferred. Ask all questions in a single message.
Ask using AskUserQuestion (multiple choice) when options are clear:
Always ask about purpose / key message — choose the form based on how much you can infer:
The audience question can be skipped if clearly inferable.
After receiving the user's answers, thoroughly explore the project to understand it well:
Take time here — a well-understood project leads to a much better presentation.
Based on the user's answers and your deep exploration, design two distinct storyline proposals — think of them as two different angles or narratives for the same project. Each proposal should have a different structure, emphasis, or rhetorical flow. For example:
Other possible contrasts: technical depth vs. business value, chronological story vs. feature-driven, demo-first vs. theory-first. Choose contrasts that make sense for the project and audience.
Do not ask the user to choose — generate slides for both.
Generate two .md files in the project root:
presentation-a.md — Proposal Apresentation-b.md — Proposal BStructure per proposal (adjust based on storyline angle):
Writing style:
<!-- _class: lead -->For Marp syntax, see references/marp-syntax.md.
Check if Marp CLI is available:
marp --version
If available, export both presentations to HTML:
marp --no-stdin --allow-local-files presentation-a.md -o presentation-a.html && marp --no-stdin --allow-local-files presentation-b.md -o presentation-b.html
If Marp is not installed, inform the user and suggest: npm install -g @marp-team/marp-cli
After generating both presentations, explain them to the user in a single message:
presentation-a.md): describe its storyline angle, opening hook, and what kind of audience or occasion it suits bestpresentation-b.md): same breakdownnpx claudepluginhub gyu-don/project-to-marp --plugin project-to-marpScaffolds Slidev presentation decks with slides.md, package.json, Makefile, and public/ folder. Generates concise markdown slides from project docs or prompts.
Generates Marp-compatible markdown slide decks from JSON schema. Converts dev context into presentations for tech talks, sprint reviews, feature demos, and tutorials.
Generates project showcase materials: intro docs, technical docs, slides, and optional poster images. Supports interactive selection, full generation, and versioned history.