- name
SKILL.md
File skill tetap berada di repositori penerbit.
Tempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add nexu-io/open-design --skill guizang-ppt -a cursor -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add nexu-io/open-design --skill guizang-ppt -a claude-code -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add nexu-io/open-design --skill guizang-ppt -a codex -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add nexu-io/open-design --skill guizang-ppt -a grok -yKirim pesan yang disalin di chat Grok Bot. Bot mengambil SKILL.md ini dari GitHub dan menambahkannya ke skill yang dipakai bersama oleh semua Bot Anda.
Install this skill: https://github.com/nexu-io/open-design/tree/HEAD/design-templates/guizang-pptDari penerbit
Generates a single-file HTML horizontal-swipe deck with a visual tone of:
This skill's aesthetic is not "corporate PPT," nor "consumer-internet UI": it looks like Monocle magazine after code was stitched onto it.
Suitable scenarios:
Unsuitable scenarios:
Infer one of the 5 magazine directions from the brief, audience, content, and known context. Each direction packages its theme color, recommended layouts, chrome style, and slide count. Use the closest fit and continue without asking.
Only when the user explicitly asks to see or compare direction options, open
references/styles.md and present the 1-line summaries in one
direction-cards question form:
1. Monocle Editorial · International magazine style ✦ default
2. WIRED Tech · Data + engineering
3. Kinfolk Slow · Slow living / humanist
4. Domus Architectural · Architecture / sense of space
5. Lab / Reference · Academic + craft manual
If the user says "I don't know, you recommend" or provides no direction cue: default to Monocle Editorial without asking, because it has the lowest failure probability. If the user mentions "AI / benchmark / technical launch": choose WIRED; "reading / private / social circle": choose Kinfolk; "design / architecture / portfolio": choose Domus; "research / academic / methodology": choose Lab.
After picking a direction, create or update 项目记录.md (Project Record) in the project folder, with the first line clearly stating direction + theme color + audience + duration (see the template at the end of styles.md). Do not change direction at any point: switching midway = everything before is wasted.
If the user has already given a complete outline + images, you can skip straight to Step 2.
Infer the checklist below from the brief, project metadata, supplied content, and conversation. If a missing answer would materially change the deck and no safe default exists, ask only those unresolved fields in one consolidated question form. Do not ask the checklist one by one.
Direction and theme color are inferred in Step 0 unless the user explicitly asks to compare options.
Use the "narrative arc" template to build the skeleton, then fill in content:
Hook → 1 page : throw out a contrast / question / hard number that makes people stop
Context → 1-2 pages : explain the background / who you are / why this topic
Core → 3-5 pages : the core content, interleaving Layouts 4/5/6/9/10
Shift → 1 page : break the expectation / propose a new view
Takeaway → 1-2 pages : a punchline / a suspenseful question / a call to action
Narrative arc + page-count plan + theme rhythm table (see layouts.md); align all three tables before moving to Step 2.
It's best to save the outline as 项目记录.md (Project Record) or 大纲-v1.md (Outline v1) for later iteration.
Make these clear to the user before starting:
项目/XXX/ppt/images/ (sibling to index.html){page number}-{semantic}.{ext}, e.g. 01-cover.jpg / 03-figma.jpg / 05-dashboard.png
images/oldname and change it to the new nameCopy assets/template.html to the target location (usually 项目/XXX/ppt/index.html), and create an images/ folder as a sibling, ready to receive images.
mkdir -p "项目/XXX/ppt/images"
cp "<SKILL_ROOT>/assets/template.html" "项目/XXX/ppt/index.html"
template.html is a complete, runnable file: CSS, WebGL shader, paging JS, font/icon CDNs are all preset; only inside <main id="deck"> are there 3 example slides (cover, act divider, blank filler page).
Right after copying, change the placeholders below, or the browser tab will show awkward text like "[必填] replace with the PPT title":
The first thing to do every time you finish copying template.html: grep for "[必填]" to confirm everything is replaced.
This skill only allows picking one of 5 carefully tuned presets; it does not accept user-defined hex values: a wrong color pairing makes the visuals ugly in an instant, and protecting the aesthetic matters more than offering freedom.
How to do it:
references/themes.md and find the :root block for the corresponding theme:root{ block of assets/template.html (the copied version): --ink / --ink-rgb / --paper / --paper-rgb / --paper-tint / --ink-tintvar(--...), no other changes neededHard rules:
This is the source of all generation problems. The layouts.md skeletons use many class names (h-hero / h-xl / stat-card / pipeline / grid-2-7-5, etc.); if assets/template.html's <style> has no corresponding definition, the browser falls back to default styles: the big title turns sans-serif, the data cards squeeze into a clump, the pipeline mushes into one line, the images pile up at the bottom of the page.
Before writing any slide code:
assets/template.html (at least through the end of the <style> block)<style><style>, don't rewrite it inline on every slidestyle="..." inlineClasses commonly missed (must be confirmed to exist in advance):
h-hero / h-xl / h-sub / h-md / lead / kicker / meta-row / stat-card / stat-label / stat-nb / stat-unit / stat-note / pipeline-section / pipeline-label / pipeline / step / step-nb / step-title / step-desc / grid-2-7-5 / grid-2-6-6 / grid-2-8-4 / grid-3-3 / grid-6 / grid-3 / grid-4 / frame / frame-img / img-cap / callout / callout-src / chrome / foot
Before picking layouts, you must first list the theme class for each page (hero dark / hero light / light / dark) and write it to a document or draft to align. For detailed rules, see the "Theme rhythm planning" section at the top of references/layouts.md.
Mandatory rules:
light / dark / hero light / hero dark; don't write just herohero dark + ≥1 hero lightlight body pages; it must have a dark body page to create breathing roomSelf-check after generating: grep 'class="slide' index.html lists all themes; manually confirm the rhythm is reasonable before delivering.
Don't write slides from scratch. Open references/layouts.md; it has 10 ready-made layout skeletons, each a complete, paste-ready <section> code block:
Pick the corresponding layout, paste it in, change the copy and image paths. Be sure to complete the 3.0 pre-check first.
Always use a standard ratio, never the source image's odd ratio (like 2592/1798):
Never use align-self:end on an image: it slides to the bottom of the cell, hidden by the browser toolbar. Use a grid container + align-items:start (already preset in the template) so the image sticks to the top; if you want the left column to stick to the bottom, use flex column + justify-content:space-between.
Component details (fonts, colors, grids, icons, callout, stat-card, etc.) are in references/components.md.
After generating, always open references/checklist.md and check item by item. It summarizes every pitfall stepped on during real iteration; the P0-level issues (emoji, images breaking out, title wrapping, type division of labor) must all pass.
A few items to watch especially:
h-hero class is missing from template.htmlheight:Nvh, not aspect-ratio (it breaks out)align-self:end, use grid + align-items:start (see Step 3.2)nowrap (avoid 1 character per line)Just open index.html directly in the browser. On macOS:
open "项目/XXX/ppt/index.html"
No local server needed. Images use the relative path images/xxx.png.
Modify based on user feedback: the template's CSS is highly parameterized, and 90% of adjustments are changing inline styles (font size font-size:Xvw / height height:Yvh / spacing gap:Zvh).
magazine-web-ppt/
├── SKILL.md ← you are reading this
├── assets/
│ ├── template.html ← the complete runnable template (seed file)
│ └── example-slides.html ← a 9-page sample deck (for the Examples preview)
└── references/
├── styles.md ← the 5 magazine directions (Monocle / WIRED / Kinfolk / Domus / Lab)
├── components.md ← component handbook (fonts, color, grid, icons, callout, stat, pipeline...)
├── layouts.md ← 10 page layout skeletons (paste-ready)
├── themes.md ← 5 theme color presets (pick only, no customization)
└── checklist.md ← quality checklist (P0/P1/P2/P3 tiers)
Recommended loading order:
SKILL.md (this file) to understand the wholestyles.md: each of the 5 directions packages up theme color + recommended layouts + chrome stylethemes.md for palette details<style> block of assets/template.html: this is the single source of class names; missing classes crash the whole page's stylinglayouts.md to pick a layout (the top has the Pre-flight class-name list and theme rhythm planning)components.md to look up componentschecklist.md to self-check (the top P0-0 rule enforces the pre-check)These principles are distilled from 5 rounds of iteration on the "one-person company" talk deck. Violating any one of them makes the visual feel collapse.
height:Nvh, not aspect-ratio stretchingThis skill's visual tone references:
You can treat these as style anchors.
|
---name: magazine-web-pptdescription: |---# design-templates/guizang-ppt/SKILL.mdFAQ
Unduh design-templates/guizang-ppt/SKILL.md dari penerbit, atau salin path-nya dan buka repositori. PlugMCP hanya mendaftar skill ini dan tidak meng-host filenya.
Penerbit menyimpannya di https://github.com/nexu-io/open-design.
Claude, Cursor, Codex, dan Grok Build bisa membaca SKILL.md yang Anda tambahkan dari repositori penerbit. Grok Bot memasangnya saat Anda mengirim tautan folder GitHub skill tersebut di chat.