Skip to main content
skill CX Codex

presentation-creator · getsentry — Claude Code skill: build slides

Creates interactive React and Vite slide decks with Sentry styling. Use it when a presentation needs real metrics, charts, and slide navigation.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add getsentry/skills --skill presentation-creator -a claude-code
Open on GitHub

What presentation-creator does

The skill first asks for the topic, slide count, required data, and narrative. It then scaffolds a presentation app with React and Vite, styled with the Sentry design system and built into one distributable HTML file.

The project includes index.html, package.json, vite.config.js, src/main.jsx, App.jsx, and App.css. Arrow keys and Space move through slides, while the bottom overlay provides buttons, dots, and a slide number.

Recharts visuals are created only when the material contains real quantitative data. Qualitative content uses cards, tables, lists, or diagrams instead. Source figures are therefore something to check before requesting charts.

What it helps with

  • turn source metrics into Recharts charts
  • scaffold a React and Vite slide application
  • build keyboard navigation for a slide deck
  • use text layouts when chart data is unavailable

Example prompts for the agent

  • Create a presentation from these metrics and chart only confirmed numbers.
  • Build slides for this technical deep-dive using cards instead of charts.
  • Make a Sentry-styled presentation with Arrow key and Space navigation.

How to install presentation-creator

1Skills CLI (Vercel)

npx skills add getsentry/skills --skill presentation-creator -a claude-code

2Manually: put the files in place

~/.claude/skills/presentation-creator/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/presentation-creator/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about presentation-creator

How do I install presentation-creator in Claude Code?

Run npx skills add getsentry/skills --skill presentation-creator -a claude-code, then run npx skills add getsentry/skills --skill presentation-creator -a claude-code.

What does presentation-creator do?

It scaffolds a React and Vite presentation project with slides, animations, and a single HTML output. It uses Recharts for visualising numeric source data.

Does it create charts for qualitative material?

No. For narratives, opinions, and process descriptions, it uses text-based layouts such as cards, tables, lists, or diagrams rather than fabricated chart values.

Source text

SKILL.md · Apache-2.0
---
name: presentation-creator
description: Create data-driven presentation slides using React, Vite, and Recharts with Sentry branding. Use when asked to "create a presentation", "build slides", "make a deck", "create a data presentation", "build a Sentry presentation". Scaffolds a complete slide-based app with charts, animations, and single-file HTML output.
---

# Sentry Presentation Builder

Create interactive, data-driven presentation slides using React + Vite + Recharts, styled with the Sentry design system and built as a single distributable HTML file.

## Step 1: Gather Requirements

Ask the user:
1. What is the presentation topic?
2. How many slides (typically 5-8)?
3. What data/charts are needed? (time series, comparisons, diagrams, zone charts)
4. What is the narrative arc? (problem → solution, before → after, technical deep-dive)

### Data Assessment (CRITICAL)

Before designing any slides, assess whether the source content contains **real quantitative data** (numbers, percentages, measurements, time series, costs, metrics). Only create Recharts visualizations for slides where real data exists. Do NOT fabricate, estimate, or invent data to fill charts.

- **Has real data** → use a Recharts chart (bar, area, line, etc.)
- **Has no data** → use text-based layouts: cards, tables, bullet columns, diagrams, or quote blocks. Do NOT create a chart with made-up numbers.

If the source content is purely qualitative (narrative, opinions, strategy, process descriptions), the presentation should use zero charts. Recharts and `Charts.jsx` should only be included in the project if at least one slide has real data to visualize.

## Step 2: Scaffold the Project

Create the project structure:

```
<project-name>/
├── index.html
├── package.json
├── vite.config.js
└── src/
    ├── main.jsx
    ├── App.jsx
    ├── App.css
    └── Charts.jsx
```

### index.html

```html
<!doctype html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <link rel="preconnect" href="https://fonts.googleapis.com" />
    <link href="https://fonts.googleapis.com/css2?family=Rubik:wght@300;400;500;600;700&display=swap" rel="stylesheet" />
    <link href="https://fonts.googleapis.com/css2?family=Material+Symbols+Outlined:opsz,wght,FILL,[email protected],100..700,0..1,-50..200&display=swap" rel="stylesheet" />
    <title>TITLE</title>
  </head>
  <body>
    <div id="root"></div>
    <script type="module" src="/src/main.jsx"></script>
  </body>
</html>
```

### package.json

```json
{
  "name": "PROJECT_NAME",
  "private": true,
  "type": "module",
  "scripts": { "dev": "vite", "build": "vite build", "preview": "vite preview" },
  "dependencies": { "react": "^18.3.1", "react-dom": "^18.3.1", "recharts": "^2.15.3" },
  "devDependencies": { "@vitejs/plugin-react": "^4.3.4", "vite": "^6.0.0", "vite-plugin-singlefile": "^2.3.0" }
}
```

### vite.config.js

```javascript
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import { viteSingleFile } from 'vite-plugin-singlefile'

export default defineConfig({ plugins: [react(), viteSingleFile()] })
```

### main.jsx

```jsx
import React from 'react'
import ReactDOM from 'react-dom/client'
import App from './App'
import './App.css'

ReactDOM.createRoot(document.getElementById('root')).render(<App />)
```

## Step 3: Build the Slide System

Read `references/design-system.md` for the complete Sentry color palette, typography, CSS variables, layout utilities, and animation system.

### App.jsx Structure

Define slides as an array of functions returning JSX:

```jsx
const SLIDES = [
  () => ( /* Slide 0: Title */ ),
  () => ( /* Slide 1: Context */ ),
  // ...
];
```

Each slide function returns a `<div className="slide-content">` with:
1. An `<h2>` heading
2. Optional subtitle paragraph
3. Main content (charts, cards, diagrams, tables)
4. Animation classes: `.anim`, `.d1`, `.d2`, `.d3` for staggered fade-in

Do NOT add category tag pills/badges above headings (e.g., "BACKGROUND", "EXPERIMENTS"). They look generic and add no value. Let the heading speak for itself.

### Navigation

Implement keyboard navigation (ArrowRight/Space = next, ArrowLeft = prev) and a bottom nav overlay with prev/next buttons, dot indicators, and slide number. The nav has **no border or background** — it floats transparently. A small low-contrast Sentry glyph watermark sits fixed in the top-left corner of every slide.

```jsx
function App() {
  const [cur, setCur] = useState(0);
  const go = useCallback((d) => setCur(c => Math.max(0, Math.min(SLIDES.length - 1, c + d))), []);

  useEffect(() => {
    const h = (e) => {
      if (e.target.tagName === 'INPUT') return;
      if (e.key === 'ArrowRight' || e.key === ' ') { e.preventDefault(); go(1); }
      if (e.key === 'ArrowLeft') { e.preventDefault(); go(-1); }
    };
    window.addEventListener('keydown', h);
    return () => window.removeEventListener('keydown', h);
  }, [go]);

  return (
    <>
      {cur > 0 && <div className="glyph-watermark"><SentryGlyph size={50} /><span className="watermark-title">TITLE</span></div>}
      <div className="progress" style={{ width: `${((cur + 1) / SLIDES.length) * 100}%` }} />
      {SLIDES.map((S, i) => (
        <div key={i} className={`slide ${i === cur ? 'active' : ''}`}>
          <div className={`slide-content${i === cur ? ' anim' : ''}`}>
            <S />
          </div>
        </div>
      ))}
      <Nav cur={cur} total={SLIDES.length} go={go} setCur={setCur} />
    </>
  );
}
```

## Step 4: Create Charts (Only When Data Exists)

**IMPORTANT: Only create charts for slides backed by real, concrete data from the source content.** If a slide's content is qualitative (strategies, learnings, process descriptions, opinions), use text-based layouts instead (cards, tables, bullet lists, columns). Never invent numbers, fabricate percentages, or generate synthetic data to populate a chart. If you are unsure whether data is real or inferred, do NOT create a chart.

If NO slides require charts, skip this step entirely — do not create `Charts.jsx` or import Recharts.

When real data IS available, read `references/chart-patterns.md` for Recharts component patterns including axis configuration, color constants, chart types, and data generation techniques.

Put all chart components in `Charts.jsx`. Key patterns:

- Use `ResponsiveContainer` with explicit height
- Wrap in `.chart-wrap` div with max-width 920px
- Use `useMemo` for data generation
- **Color rule**: Use the Tableau-inspired categorical palette (`CAT[]`) for distinguishing data series and groups. Only use semantic colors (`SEM_GREEN`, `SEM_RED`, `SEM_AMBER`) when the color itself carries meaning (good/bad, success/failure, warning).
- Common charts: `ComposedChart` with stacked `Area`/`Line`, `BarChart`, custom SVG diagrams
- **Every data point in a chart must come from the source content.** Do not interpolate, extrapolate, or round numbers to make charts look better.

## Step 5: Style with Sentry Design System

Apply the complete CSS from the design system reference. Key elements:

- **Font**: Rubik from Google Fonts
- **Colors**: CSS variables for UI chrome (`--purple`, `--dark`, `--muted`). Semantic CSS variables (`--semantic-green`, `--semantic-red`, `--semantic-amber`) only where color conveys meaning. Categorical palette (`CAT[]`) for all other data visualization.
- **Slides**: Absolute positioned, opacity transitions
- **Animations**: `fadeUp` keyframe with staggered delays
- **Layout**: `.cols` flex rows, `.cards` grid, `.chart-wrap` containers
- **Tags**: `.tag-purple`, `.tag-red`, `.tag-green`, `.tag-amber` for slide labels
- **Logo**: Read the official SVG from `references/sentry-logo.svg` (full wordmark) or `references/sentry-glyph.svg` (glyph only). Do NOT hardcode an approximation — always use the exact SVG paths from these files.

## Step 6: Common Slide Patterns

### Title Slide
Logo (from `references/sentry-logo.svg` or `references/sentry-glyph.svg`) + h1 + subtitle + author/date info.

### Problem/Context Slide
Tag + heading + 2-column card grid with icon headers.

### Data Comparison Slide
Tag + heading + side-by-side charts or before/after comparison table.

### Technical Deep-Dive Slide
Tag + heading + full-width chart + annotation bullets below.

### Summary/Decision Slide
Tag + heading + 3-column layout with category headers and bullet lists.

## Step 7: Iterate and Refine

After initial scaffolding:
1. Run `npm install && npm run dev` to start the dev server
2. Iterate on chart data models and visual design
3. Adjust animations, colors, and layout spacing
4. Build final output: `npm run build` produces a single HTML file in `dist/`

## Output Expectations

A working React + Vite project that:
- Renders as a keyboard-navigable slide deck
- Uses Sentry branding (colors, fonts, icons)
- Contains Recharts visualizations **only for slides with real quantitative data** from the source content — no fabricated data
- Omits `Charts.jsx` and the Recharts dependency entirely if no slides have real data
- Builds to a single distributable HTML file
- Has smooth fade-in animations on slide transitions

© getsentry · Apache-2.0 · getsentry/skills

Similar skills

Everything for Frontend and UI →

presentation-creator by other authors comes first.

presentation-creator mblode Builds slide decks with narrative structure, slide copy, and speaker notes from raw ideas or docs. Outputs Marp markdown by default or web deck code. CX Codex +1 872installs sentry-react-sdk getsentry Walks a React project through full Sentry setup: it scans your dependencies, proposes a feature set, and writes the config. Useful when you want error monitoring wired up without reading the docs end to end. CX Codex +1 3,100installs sentry-sdk-skill-creator getsentry Generates complete Sentry SDK skill bundles with wizard flows and reference files for any platform. Designed for building agent skills backed by official docs. CX Codex +1 2,400installs presentation iii-hq Turns a technical-spec directory into an interactive web presentation. Use it when a specification needs a shareable deck with a clear narrative. CX Codex +1 3,500installs adding-error-tracking spencerpauly This skill wires Sentry into a web app: error tracking, performance traces and source maps. Useful when you want crash reporting without hand-rolling the config. CX Codex +1 386installs presentation-design jwynia A skill that shapes presentations around the audience: structure, visual clarity, cognitive load. Use it before building a deck or to review existing slides. CX Codex +1 2,500installs canva-branded-presentation official Canva Pty Ltd. Creates on-brand Canva presentation decks from briefs, raw outlines, or design links. Useful when you need slides formatted to your brand kit. CX Codex GP ChatGPT 26installs

From the same set23

create-branch Creates a git branch named the Sentry way, like feat/... or fix/.... Useful when you start work and don't want to invent a name. CX Codex +1 4,300installs gh-review-requests Finds unread review requests for open GitHub pull requests and filters them by team. Use it when the review queue needs a focused check. CX Codex +1 4,200installs skill-scanner Scans agent skills for prompt injection, malicious code, excessive permissions, secret exposure, and supply-chain risks before installation. CX Codex +1 3,800installs blog-writing-guide A skill that carries the Sentry engineering blog standards: it drafts, reviews and tightens posts until they read like a developer wrote them. CX Codex +1 3,300installs django-perf-review This skill reviews Django code for N+1 queries, unbounded querysets and missing indexes. Useful before a release or when a page slows down on large tables. CX Codex +1 2,900installs django-access-review A skill that hunts IDOR and broken authorization in Django: it walks views, DRF viewsets and ORM queries and shows where checks are missing. CX Codex +1 2,700installs brand-guidelines Applies Sentry brand and copy guidelines to user-facing text, error states, and UI flows. Useful when writing UI labels, empty states, or docs. CX Codex +1 2,500installs skill-writer Designs, synthesizes, and refines agent skills following the Agent Skills specification. Helpful when turning raw workflows or prompt templates into structured skills. CX Codex +1 2,500installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor