Slides logo

Slides

Organization
Fergana-Labs
slides

How to build presentation slide decks as HTML pages. Covers the slide format, canvas dimensions, and recommended libraries.

Overview

PublisherFergana-Labs
Repositorystash
Skill nameslides
Stars
340
Forks
44
Bundled files
Instructions only
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.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Fergana-Labs on GitHub. Read the source before you install it.

Installation

Install the Slides 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/Fergana-Labs/stash/tree/main/docs/skills/slides
  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/Fergana-Labs/stash.git /tmp/stash
mkdir -p .claude/skills
cp -r /tmp/stash/docs/skills/slides .claude/skills/slides
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Slides 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 Slides 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 Slides 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.

Building slide decks

A slide deck is a single HTML page with html_layout: "fixed-aspect" whose <body> contains one <section class="slide"> per slide.

The canvas — 1920 × 1080 (16:9)

Every slide is a fixed 1920 × 1080 px canvas with overflow:hidden. Stay inside a 64 px safe-area margin (working area 1792 × 952 px). Nothing should scroll inside a slide; the viewer scales the canvas to fit the viewport, and the exporter renders at native 1920×1080.

Required structure

html
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <title>Deck title</title>
  <script src="https://cdn.tailwindcss.com"></script>
  <link href="https://cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@6/css/all.min.css" rel="stylesheet">
  <style>
    /* Belt-and-suspenders — the viewer enforces these too. */
    section.slide {
      width: 1920px; height: 1080px;
      overflow: hidden; position: relative;
      box-sizing: border-box;
      padding: 64px;
    }
  </style>
</head>
<body>
  <section class="slide" data-type="cover">…</section>
  <section class="slide" data-type="content">…</section>
  <section class="slide" data-type="content">…</section>
  <section class="slide" data-type="final">…</section>
</body>
</html>

Page types (data-type, optional but recommended)

  • cover — title slide.
  • toc — table of contents.
  • chapter — section divider.
  • content — regular content slide.
  • final — thanks / Q&A / contact slide.

These let presenter view and future templates target slides by role.

Typography

  • Title text: ≥ 56 px.
  • Body text: ≥ 28 px.
  • Footnotes / captions: ≥ 20 px.
  • Use the system font stack or one CDN font (Inter, Geist). Avoid @font-face — it adds latency in export.

Recommended libraries (all CDN-loadable)

NeedUse
ChartsChart.js for 1–2 charts per slide; ECharts for dashboards; D3 only when custom
TablesPlain <table> + Tailwind classes. No DataTables.
IconsFont Awesome 6 (CDN) or Lucide
CodeShiki (preferred, vector-clean) or highlight.js
MathKaTeX with auto-render (never MathJax inside iframe)
DiagramsMermaid via CDN, render once on load

Render charts at load time (inline <script> in the slide) so screenshot exporters capture them. Don't rely on interactivity in PPTX/PDF.

Anti-patterns

  • More than ~40 words of body text per slide.
  • Low contrast (white text on light backgrounds, etc.).
  • vh / vw units — use px. The canvas is fixed-pixel.
  • Images without max-width: 100% (they'll overflow).
  • Fixed-positioned elements depending on viewport (position: fixed).
  • Custom fonts loaded via @font-face from arbitrary URLs.
  • Multiple <section class="slide"> nested inside each other.

Editing

Users can touch up text inline with the Edit button on the page. Keep markup semantic — use <h1>, <h2>, <p>, <ul> rather than a sea of <div>s — so the WYSIWYG editor's text selection and the exporter's text-overlay extraction both work cleanly.

Export

The PDF export is vector text. The PPTX and Google Slides exports embed each slide as a high-DPI image plus an invisible text overlay so users can select, copy, and search the text in PowerPoint / Keynote / Slides. Don't ship interactive controls — they won't survive the export.

Frequently asked questions

What does the Slides AI skill do?

How to build presentation slide decks as HTML pages. Covers the slide format, canvas dimensions, and recommended libraries.

Why use Slides on TypingMind?

Because you install it once and use it with any model. Slides 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 Slides in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Fergana-Labs/stash/tree/main/docs/skills/slides. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Slides?

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 Slides?

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

Is the Slides AI skill free?

Yes. It is published on GitHub by Fergana-Labs 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 👇