Presentation Design

Presentation Design is a skill for Claude Code, Codex from rhuss/cc-slidev. It costs 57 tokens per session (5,259 once invoked), scanned A, original, MIT.

Guidance for planning and designing presentations so ideas are easy for an audience to follow. It covers storytelling, slide structure, visual hierarchy, audience needs, and limits on text, elements, and code.

In plain words
What is it for?
Use it to create an outline, improve slide flow, choose visuals, structure technical content, or make a presentation easier to understand.
Why use it?
It helps prevent overloaded slides and unclear presentation flow. The rules keep each slide focused and leave room for the speaker to explain the topic.

Skill for Claude CodeCodex

Part of the slidev plugin — 8 skills, 18 commands, 2 agents shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/rhuss/cc-slidev/presentation-design
Any agent
npx skills add rhuss/cc-slidev --skill presentation-design
Clone the repo
git clone --depth 1 https://github.com/rhuss/cc-slidev

Made for: Claude Code, Codex.

Or install slidev, the plugin that ships this one along with the rest of its 8 skills, 18 commands, 2 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for Presentation Design

README.md
[![agentmods](https://agentmods.dev/badge/skills/rhuss/cc-slidev/presentation-design.svg)](https://agentmods.dev/skills/rhuss/cc-slidev/presentation-design)
Your own site
<a href="https://agentmods.dev/skills/rhuss/cc-slidev/presentation-design"><img src="https://agentmods.dev/badge/skills/rhuss/cc-slidev/presentation-design.svg" alt="Measured on agentmods" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,259 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00057 $0.05259
Opus 5 $0.00028 $0.02629
Sonnet 5 $0.00011 $0.01052
Haiku 4.5 $0.00006 $0.00526

Measured 5d ago against content hash 9261106f0a17, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Presentation Design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

slidev/skills/presentation-design/SKILL.md · 740 lines

How it starts

The opening of the file, as written. The whole thing — 740 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Presentation Design

Effective presentations combine research-backed design principles, storytelling, and audience understanding. Create compelling narratives that engage audiences and communicate ideas clearly.

Research Basis: These guidelines are based on cognitive load studies (Miller's Law), TED presentation research, MIT Communication Lab recommendations, and analysis of effective technical conference talks. They prevent common mistakes that make presentations hard to follow. See references/presentation-best-practices.md for detailed research citations.

HARD LIMITS (Never Violate)

These are research-backed maximum limits that should NEVER be exceeded. If content exceeds these limits, you MUST split into multiple slides:

🔴 MAX 6 elements per slide (bullets + images + diagrams + code blocks combined) 🔴 MAX 50 words body text per slide (excluding title) 🔴 MAX 1-2 code blocks per slide (8-10 lines each) 🔴 ONE idea per slide (if multiple ideas → split slides)

Why these are hard limits:

  • Cognitive load research: >6 elements exponentially increases audience confusion
  • Reading vs listening interference: >50 words means audience stops listening
  • Code complexity: >2 code examples creates comparison overhead

When content doesn't fit:

  • NEVER compress or shrink to fit
  • NEVER reduce font size below 18pt
  • ALWAYS split into additional slides
  • ALWAYS move details to presenter notes or backup slides

Core Principles

1. One Idea Per Slide

Critical Rule: Each slide communicates exactly ONE central idea, finding, or question.

Why this matters:

  • Prevents cognitive overload
  • Maintains audience focus
  • Enables clear narrative progression

In practice:

  • If a slide requires >2 minutes to explain → split it
  • Each slide title should state one clear point
  • No tangential information on slides
  • Content supports only the title's assertion

Example:

  • ❌ Bad: One "Background" slide covering problem + impact + existing solutions
  • ✅ Good: Three slides → "Problem X costs $Y annually" → "Existing solutions fail at scale" → "No current approach handles edge case Z"

Read the full file on GitHub · 740 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 740 lines · 57 tokens per session scan A 9261106f0a17

Subscribe to this mod's changes

Presentation Design is a skill published in the GitHub repository rhuss/cc-slidev (51 stars, last pushed 17d ago), licensed MIT. It adds 57 tokens to every session and 5,259 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens