๐ŸŽฌ Limited Time Flash Sale: Save $160 on the Yearly Max Plan! Ends in 2d 06h 45m 49s

Try iMini AI Now

Making a PPT used to mean spending most of your time on "making the content look good." How to anchor the title, where to place images, how to keep a data slide from looking chaotic, how to give a cover that subtle tech feel โ€” every step felt like a fight with layout.

Running Claude Code bare can generate a PPT. The problem is it tends to interpret "tech style" as gradients, glow effects, glassmorphism, random color blocks, and a heap of decorations that look like they're trying very hard. It might look busy at first glance, but when you actually go to present it, you'll often find unstable titles, jumbled hierarchy, inconsistent slide styles โ€” almost impossible to use as-is.

This is where Skills come in. A Skill locks down style, layout, image slots, type hierarchy, and export format ahead of time, giving Claude Code less room to improvise and more room to deliver consistently. The result is no longer "AI tried to make a few slides" โ€” it's something much closer to a presentation asset you can actually demo, screenshot, and extend.

Comparison: raw Claude Code output vs Skill-guided deck

This article uses Guizang PPT Skill as the main example. It's designed to turn articles, Markdown, and talk outlines into single-file HTML landscape-scroll PPTs, and can be extended to WeChat cover images, Xiaohongshu covers, and share cards. Here's a cover made with its Swiss International style direction.

Guizang Swiss-style tech deck cover example

This example follows Guizang's Style B โ€” Swiss International. Dark canvas, strict grid, hairline rules, right angles, a single high-saturation accent color. It makes topics like AI tools, product launches, data reviews, and tech talks look clean. The point isn't "more decoration" โ€” it's knowing what you're not allowed to mess with.

Why This Skill Has Blown Up Recently

Guizang PPT Skill's rise comes from a very specific unmet need: people are no longer satisfied with AI generating generic template pages. What's actually needed is a stable set of visual rules โ€” rules that let an Agent understand what "magazine style" means, what "Swiss style" means, which pages should use big headlines, which should use flowcharts, and which content can only live in image slots.

As of 2026-06-05, Guizang PPT Skill has 15k stars and 1.1k forks. The long-form post about its major update has 1,276 likes, 272 reposts, 47 comments, 2,057 saves, and roughly 224,000 reads. Those numbers tell the story. What people save and share is the aesthetic system and export workflow that makes "AI can make PPTs" actually stable and reusable.

Guizang's two styles can be understood like this. Style A is editorial ink โ€” suited for personal expression, opinion-sharing, and narrative talks. Think of it as a digital magazine that flips pages, with more of an author's personality.

Guizang Style A editorial ink deck example

Style B is Swiss International โ€” suited for facts, products, analysis, and methodology. It's more restrained, with emphasis on grid, type scale, numbers, process flows, and whitespace. Tech-style PPTs can start here directly.

Guizang Style B Swiss International deck example

This is exactly why I recommend Guizang as the entry example. It provides not just templates, but clearly defined aesthetic and delivery boundaries. When Claude Code generates within those boundaries, the result looks more like a usable PPT and less like a freeform experiment.

The Key Difference: Lock the Rules First, Then Generate

Claude Code PPT generation workflow with Skill

The most reliable way to make PPTs with Claude Code: install the Skill first, hand it your topic and materials, let it extract a slide rhythm using the Skill's visual system, then generate the HTML Deck, preview it page by page in a browser, and iterate based on feedback โ€” extending to covers, share images, or export files.

The order matters. When you run Claude Code bare, the Agent guesses layouts, guesses colors, guesses animations. The more it guesses, the more the output falls apart. Guizang's value is in narrowing those choices upfront: Style A for narrative, Style B for facts and methodology, images into fixed slots, Swiss style using locked layout, delivered as a single-file HTML.

Step 1: Install Guizang First

You can use the install command directly in Claude Code.

npx skills add https://github.com/op7418/guizang-ppt-skill --skill guizang-ppt-skill

Or paste this directly into Claude Code:

Please install guizang-ppt-skill.
Clone https://github.com/op7418/guizang-ppt-skill into ~/.claude/skills/guizang-ppt-skill.
After installation, verify that SKILL.md, assets/, and references/ exist.

Already installed? You can update it.

Please update guizang-ppt-skill.
Go into ~/.claude/skills/guizang-ppt-skill and run git pull.
Tell me the latest commit when done.

After installing, restart Claude Code. Then do a small test run โ€” something like "make me a 3-slide Swiss-style PPT." This step just confirms Claude Code can find the Skill.

Step 2: Hand Claude Code the Topic โ€” Don't Rush to a Final Output

Guizang handles long articles, Markdown, talk outlines, and product docs well. Paste your material to Claude Code and let it break down the content first.

Please use guizang-ppt-skill to turn the following topic into a tech-style PPT.

Topic: [fill in topic]
Target audience: [fill in audience]
Use case: [in-person talk / product launch / Demo Day / internal review / course lecture]
Slides: [fill in count, e.g. 7 slides]
Talk length: [fill in duration, e.g. 8 minutes]
Existing material: [paste article, notes, data, product screenshots, links, or Markdown]

Hard constraints:
Text must be clearly readable in Chinese
One core message per slide
No wall of text
No blue-purple gradient as primary visual
Browser preview required

The most useful thing here is Claude Code's first pass at extraction. It will tell you which content works as a cover, which works as a data slide, which works as a methodology slide, and what should be cut.

Step 3: Review the Slide Rhythm Before Generating HTML

The biggest mistake in tech-style PPTs: every slide looks like a cover. A good deck needs rhythm โ€” cover grabs attention, problem slide tightens focus, method slide opens up, data slide provides evidence, closing slide wraps it up. So before generating, ask Claude Code for the slide rhythm first.

For this PPT, please use Guizang's Style B โ€” Swiss International.

Visual direction:
Dark canvas / strict grid / right-angle blocks / 1px hairline rules / single high-saturation accent color / high-contrast large headline / restrained body text

Accent color: prefer lemon yellow or safety orange.

Slide feel: tech product launch / AI tool demo / data review / methodology sharing

Please give me the slide rhythm table first. I'll confirm before you generate the full HTML.

Once you confirm the slide rhythm, have it generate the HTML Deck.

Slide rhythm confirmed.
Please continue with guizang-ppt-skill and generate the full HTML Deck.

Requirements:
Around 7 slides
Style B Swiss International
One core point per slide
Short headlines
Body text no more than three lines
2โ€“3 image slot positions
Use structured graphics or placeholder layouts when no real images are available
Tell me the HTML file path when done

Guizang's core deliverable is a single-file HTML. No server needed, no build step. Open it in a browser and you can flip through slides horizontally.

Step 4: Browser Preview Is the Real Test

Guizang HTML deck browser preview

Don't just check the cover during preview. Go through every slide: is the headline overflowing? Is the body text too dense? Are the image slots aligned? Are the navigation components covering content? The sophistication of tech-style PPTs often comes down to "nothing went wrong."

Please open the generated HTML Deck for browser preview.
Check each slide for:
Headline overflow / body text too dense / image slots misaligned / footer or navigation blocking content / too many accent colors / readability at mobile or small window sizes
List the slides that need changes.

Guizang's Swiss style also comes with a validation script. It checks common layout errors โ€” centered headlines, images outside their slots, text stuffed into SVGs, slide structure that doesn't match the locked layout.

node scripts/validate-swiss-deck.mjs path/to/index.html

Validation sets a floor. The real judgment still happens in the browser. PPTs are for people โ€” the script can only catch some basic mistakes.

Step 5: Revise Like a Design Review

When the first version is done, don't just say "make it more premium." Claude Code responds better to specific feedback: which slide is too dense, which slide has numbers too small, which slide has an empty image slot, which slide has a weak headline.

Please revise the current HTML Deck.

Keep: overall dark Swiss style / lemon yellow accent color / cover headline structure / methodology flow on slide 3

Change: slide 2 body text too dense / slide 4 numbers not prominent enough / slide 5 image slot too empty / closing slide CTA not clear enough

Revision approach: fix layout structure first / then adjust type size and spacing / don't add complex decorations / don't change the overall style / re-preview after changes

One layer per round. Structure first, then text, then visual, then animation. That way Claude Code is less likely to break what was working while fixing what wasn't.

Step 6: Extend the PPT Into Covers and Share Images

Another value of Guizang: it puts PPTs and social media images into the same visual system. After finishing a deck, you can pull out WeChat cover images, 1:1 share cards, Xiaohongshu covers, and Video Account horizontal covers from the same visual.

Deck visual system extended to covers and share cards

The strongest slide in the deck often becomes the cover. You don't need to reinvent a visual system. Reusing the same grid, colors, and type hierarchy keeps your distribution images consistent.

Based on the core message of this PPT, continue with guizang-ppt-skill to generate matching covers.

Generate: WeChat 21:9 header image / WeChat 1:1 share card / Xiaohongshu 3:4 cover

Visual rules: keep Style B Swiss International / keep current accent color / headline first / keep tech-style grid and hairline rules / no platform logos / no extra taglines

Give me 2 cover directions first. I'll confirm before you generate the full versions.

This is another advantage of an HTML Deck: it lives in the browser, so screenshotting, resizing, and extending into covers all feel natural.

A Complete Prompt You Can Copy Directly

If you want to run through this from scratch, paste the following into Claude Code.

Please use guizang-ppt-skill to create a tech-style PPT.

Topic: [fill in topic]
Target audience: [fill in audience]
Use case: [fill in use case]
Slides: around 7
Style: Guizang Style B โ€” Swiss International

Visual requirements:
Dark canvas / strict grid / right-angle blocks / 1px hairline rules / single high-saturation accent color / high-contrast large headline / restrained body text / no blue-purple gradient / no non-functional decoration

Content requirements:
Extract core points first / provide slide rhythm table first / I'll confirm before you generate the HTML Deck / one core message per slide / 2โ€“3 image slot positions / use structured graphics when no real images are available

Generation requirements:
Single-file HTML horizontal-scroll PPT / tell me the file path / open browser preview / check each slide for text overflow, information density, image slots, and navigation overlap / if issues found, fix layout first, then details

Extension requirements:
After the PPT is complete, generate a WeChat 21:9 header image, 1:1 share card, and Xiaohongshu 3:4 cover using the same visual rules.

The core of this prompt: get Claude Code into the Skill's ruleset before starting to generate. The clearer the rules, the closer the output is to a presentation you can actually use.

When to Switch to a Different Skill

Many people ask: if Guizang already handles PPTs, covers, and images, do you still need to look at other Skills? Yes. Because these Skills solve different problems.

Guizang is more like a web PPT system for content creators. Frontend Slides is more like a web presentation generator. Huashu Design is more like a full design workstation. gpt-image2-ppt-skills is more like a high-aesthetic image-first PPT generator. They all help Claude Code make PPTs, but the aesthetic direction, editability, and export formats are very different.

Public Talks, Article-to-PPT, In-Person Sharing: Use Guizang

If you're doing a public talk with personal style, or converting a long article into a 6โ€“10 slide talk script, Guizang is the most direct choice. Its strength is binding "content expression" and "visual character" together. Style A for narrative and opinion, Style B for product, analysis, and methodology. It doesn't let Claude Code invent slides freely โ€” it makes the Agent choose within a pre-designed layout system.

In terms of community traction, Guizang is among the most representative Chinese AI PPT Skills. As of 2026-06-05: 15k stars, 1.1k forks; its major update post has 1,276 likes, 272 reposts, 2,057 saves, and roughly 224,000 reads. Those save numbers show people aren't just bookmarking it out of curiosity โ€” they're actually storing it as a reusable tool.

Export-wise, Guizang's core is single-file HTML. Good for browser presenting, screenshots, and screen recording. Can be extended to WeChat 21:9, WeChat 1:1 share card, Xiaohongshu 3:4, Video Account 16:9. If you need native PPTX, note that Guizang's main workflow doesn't produce PPTX.

Convert Old PPTs to Web Presentations, Share a Live Link: Use Frontend Slides

Frontend Slides is positioned more as a web presentation tool. Its README defines it as a coding-agent skill that can create HTML presentations from scratch and convert PowerPoint files to web presentations. A key selling point: "generate visual previews first, then let you choose." This matters for most users โ€” many can't articulate what style they want, but can decide in seconds when shown three previews.

Frontend Slides official Neo-Grid Bold template

It has the highest community traction of these projects. As of 2026-06-05: Frontend Slides has 20.3k stars and 1.7k forks. That scale means it's no longer a niche template โ€” it's become the entry point for many users making web slides with Claude Code.

Style-wise, Frontend Slides is more open than Guizang. It has safe presets and integrates the Bold Template Pack, which includes Soft Editorial, Neo-Grid Bold, Editorial Tri-Tone, Signal, and many other visual systems. Guizang feels like two strong style tracks; Frontend Slides feels more like a visual direction selector.

Export-wise, its primary output is also a zero-dependency single-file HTML. Extra advantage in sharing: the README includes a Vercel deploy script to publish your deck as an accessible link, and a PDF export script using Playwright to screenshot each slide into a PDF. Good for .pptx-to-web conversion, sharing links with others, or dropping a static PDF in email or Notion.

PPT Is Just One Piece โ€” Also Need Prototypes, Animations, Infographics: Use Huashu Design

Huashu Design covers more ground. It's built as an HTML-native design workflow. The README is explicit: ship product launch animations, clickable App prototypes, editable PPTs, and print-quality infographics in 3 to 30 minutes. It's designed for grouped product launch materials, not just individual decks.

Huashu Design multi-output deck workflow

Also strong community traction. As of 2026-06-05: Huashu Design has 16.2k stars and 2.1k forks. Its fork count is higher than both Guizang and Frontend Slides, suggesting many users aren't just saving it โ€” they're probably modifying or integrating it into their own design workflows.

Style-wise, Huashu Design feels more like "creative director + production tool." It suggests design directions and can do 5-dimension design reviews. Compared to Guizang's magazine and Swiss styles, Huashu is better suited for brand launches, App prototypes, product stories, feature explanations, and animation showcases. Give it a logo, color palette, and UI screenshots, and it works more like building a set of assets around brand materials.

Export-wise, Huashu has the clearest advantages. It does HTML decks and emphasizes editable PPTX; animations can export as MP4 or GIF; infographics can export as PDF, PNG, or SVG. That range is much broader than a pure PPT Skill. If you need a full product launch kit โ€” demo videos, prototypes, and infographics โ€” Huashu is the better fit.

Strong Visual Impact, Template Cloning, Full-Page Poster Feel: Use gpt-image2-ppt-skills

gpt-image2-ppt-skills takes an image-generation approach. It treats each slide as a complete visual piece, reducing dependence on text boxes and shapes. The README is direct: generate 16:9 high-res images and a packaged .pptx from a single natural language prompt, or clone any .pptx template to produce new content.

gpt-image2-ppt-skills style gallery

Smaller community footprint than the other three. As of 2026-06-05: 854 stars, 44 forks. But it represents a different branch โ€” skip the HTML/CSS precision layout, and use gpt-image-2's aesthetic, composition, and typography capabilities to generate full-page visuals. For scenarios where "looks great at first glance" is the priority, this approach is compelling.

Style-wise, it has 10 built-in curated styles: Spatial Glass, Tech Blue, Editorial Mono, Dark Aurora, Riso, Swiss Grid, Hand Sketch, Y2K Chrome, and others. It also supports template cloning โ€” drop in a .pptx or image, have AI reference the layout, colors, and illustration style, then swap in your content.

Export-wise, its core output is per-slide high-res PNG plus a 16:9 .pptx. Sounds like a normal PPT, but note: the text and background are often effectively one image. Good for pitch decks, event visuals, template cloning, and fast complete-deck generation. If you need character-by-character editing, strict data table changes, or legal/financial documents, be careful โ€” numbers, tables, financial, medical, and legal content need human review.

So before choosing a Skill, ask yourself one question: what format do you need to deliver? Browser presenting โ†’ Guizang or Frontend Slides. PPTX with editable text boxes โ†’ Huashu. Image-first high-completion visuals โ†’ gpt-image2-ppt-skills. Article into a full talk and cover set โ†’ Guizang is the most reliable starting point for consistent output.

Finally

Making PPTs with Claude Code isn't just about whether it can generate slides. What truly determines output quality is whether it has a clear enough set of design boundaries.

Guizang PPT Skill provides a strong example. It turns PPTs into HTML, writes aesthetic rules into the Skill, and puts covers and images into the same pipeline. For content creators, this means an article can become a talk script, a cover, an infographic, a set of distributable visual assets.

That's what makes this category of Skill interesting. It moves Claude Code from "can generate slides" toward "can export something much closer to a finished PPT." Claude Code handles generation and revision. The Skill locks down aesthetic boundaries and export format. The human decides which slide actually communicates the point.

Related projects: Guizang PPT Skill, Frontend Slides, Huashu Design, gpt-image2-ppt-skills. Additional reference: Claude Chinese Station 2026-05-12 X Daily.