Slide Design logo

Slide Design

Community
hunkim
slide-design

Rules for building presentation slides that people can actually read — applies Alexei Kapterev's "Death by PowerPoint" principles plus a working checklist. Use whenever making or revising slides, decks, presentations, pitch decks, or HTML slide decks, in any format (.pptx, HTML, PDF). Triggers on "슬라이드", "발표자료", "덱", "deck", "slides", "presentation", "pitch deck", or when a slide comes back as "too complex / 복잡해".

Overview

Publisherhunkim
Repositoryslide-skill
Skill nameslide-design
Stars
4
Forks
0
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by hunkim on GitHub. Read the source before you install it.

Installation

Install the Slide Design AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/hunkim/slide-skill/tree/main
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/hunkim/slide-skill.git \
  .claude/skills/slide-design
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Slide Design in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Slide Design on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Slide Design is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Slide design

The one rule

One point per slide. If a slide is making two points, it is two slides. An extra slide costs $0.00 — splitting is always cheaper than cramming.

Before building any slide, write its single point as one sentence. If you can't, you don't know what the slide is for yet. Everything that does not serve that sentence gets deleted.

Death by PowerPoint — the principles

From Alexei Kapterev's deck (~5M views), the four failure modes are significance, structure, simplicity, rehearsal. Three of them are ours:

Significance — why does this slide exist? "Significance creates passion; passion attracts attention; attention leads to action." A slide that only transfers information is a handout, not a slide.

Structure — give 3–4 reasons, never more. "They will not remember more anyway." Common shapes: Problem → Pathway → Solution, or Problem → Solution → Reasoning. The deck should survive being told in 5 minutes or 45.

Simplicity — "Everything should be made as simple as possible, but not simpler."

  • Less text. More imagery.
  • Few matching colours. Very few fonts.
  • Photos, not clipart.
  • "People read faster than you speak. This means you are useless." Dense text on a slide makes the presenter redundant.
  • Reject mechanical rules like "7 lines × 7 words" — they produce cramped, boring slides. The real test is whether one idea lands in 3 seconds.

Do not use slides as a prompter, a handout, or a data dump. If detail is required, ship two artifacts: visual slides + a separate document with the detail. Never one file trying to be both.

What this means in practice

Instead ofDo
A 6×5 table of who passed which roundA funnel of shrinking dots with the survivor highlighted
A bullet list of five benefitsFive rows, one bold noun each, one line of support
Two charts + notes + a tableThree slides
A paragraph as the subtitleOne sentence, ≤ 20 words
Explaining the mechanism in textDraw the mechanism

Read the slide from 3 metres away. If the point isn't obvious before you read any body copy, the layout is wrong — not the copy.

Redundancy is clutter. If the headline says it, the label doesn't need to. If the next slide covers it, this slide doesn't.

Detail goes to the footnote. Sources, caveats, secondary names, exact dates: one small grey line at the bottom. Present but not competing.

Checklist before shipping a slide

  1. Can I state the slide's point in one sentence? Is that sentence on the slide?
  2. Is anything here making a second point? → split the slide.
  3. Is any element repeating what another element already says? → delete it.
  4. Would a picture of the mechanism beat this text? → draw it.
  5. Does anything only matter to 5% of the audience? → footnote it.
  6. From 3 metres: what do I see first? Is that the point?

When the feedback is "too complex"

Do not shrink the font or tighten the spacing. Remove content. Pick the single sentence, delete everything that isn't it, and give the survivor more room. Move what you deleted to a footnote, to a second slide, or to the appendix.

Building HTML decks

  • Fixed 1280×720 stage, transform: scale() to fit the viewport.
  • One design system across all slides: kicker → headline → one-line sub → body. Same paddings, same type scale, same accent colour everywhere.
  • Commit to one background tone for the whole deck. Do not mix dark and light slides unless the switch is doing deliberate work (title / section only).
  • Animation is sequencing, not decoration: entrance order should follow the order you speak in. Quiet slide transitions — a fast fade, nothing 3D.
  • Rebuild charts natively (SVG) rather than pasting screenshots, so they can animate and stay legible. Screenshots are fine when the screenshot is the evidence (a leaderboard, a news card).
  • No HTML-in-Canvas.
  • Self-contained single file: inline CSS/JS, images as base64 data URIs.
  • Hide presenter chrome in fullscreen.
  • Verify with Playwright: screenshot every slide, check for 0 JS errors, 0 blank slides, and no element whose scrollHeight/scrollWidth exceeds its container (measure only the active slide — entrance transforms create false positives on inactive ones).

Source

Alexei Kapterev, Death by PowerPoint — https://www.slideshare.net/slideshow/death-by-powerpoint/85551

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Slide Design AI skill do?

Rules for building presentation slides that people can actually read — applies Alexei Kapterev's "Death by PowerPoint" principles plus a working checklist. Use whenever making or revising slides, decks, presentations, pitch decks, or HTML slide decks, in any format (.pptx, HTML, PDF). Triggers on "슬라이드", "발표자료", "덱", "deck", "slides", "presentation", "pitch deck", or when a slide comes back as "too complex / 복잡해".

Why use Slide Design on TypingMind?

Because you install it once and use it with any model. Slide Design is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Slide Design in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hunkim/slide-skill/tree/main. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Slide Design?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Slide Design?

As many as you like. As long as a model supports skills, you can use Slide Design with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Slide Design AI skill free?

Yes. It is published on GitHub by hunkim under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇