presentation-creator
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
- 0
- Installs
- —
- Rating
- —
- Success rate
- 3
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 c41ba8587b146c2e… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
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:
- What is the presentation topic?
- How many slides (typically 5-8)?
- What data/charts are needed? (time series, comparisons, diagrams, zone charts)
- 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
<!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,GRAD@20..48,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
{
"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
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import { viteSingleFile } from 'vite-plugin-singlefile'
export default defineConfig({ plugins: [react(), viteSingleFile()] })
main.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:
const SLIDES = [
() => ( /* Slide 0: Title */ ),
() => ( /* Slide 1: Context */ ),
// ...
];
Each slide function returns a <div className="slide-content"> with:
- An
<h2>heading - Optional subtitle paragraph
- Main content (charts, cards, diagrams, tables)
- Animation classes:
.anim,.d1,.d2,.d3for 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.
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
ResponsiveContainerwith explicit height - Wrap in
.chart-wrapdiv with max-width 920px - Use
useMemofor 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:
ComposedChartwith stackedArea/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:
fadeUpkeyframe with staggered delays - Layout:
.colsflex rows,.cardsgrid,.chart-wrapcontainers - Tags:
.tag-purple,.tag-red,.tag-green,.tag-amberfor slide labels - Logo: Read the official SVG from
references/sentry-logo.svg(full wordmark) orreferences/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:
- Run
npm install && npm run devto start the dev server - Iterate on chart data models and visual design
- Adjust animations, colors, and layout spacing
- Build final output:
npm run buildproduces a single HTML file indist/
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.jsxand 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
Files
3- SKILL.md
28c0cef6259.1 KB - references/chart-patterns.md
9d4450eda37.1 KB - references/design-system.md
da787393698.9 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from getsentry/skills8
Creates and maintains concise AGENTS.md and CLAUDE.md project instruction files. Use when asked to create AGENTS.md, update AGENTS.md, maintain agent docs, set up CLAUDE.md, document repository agent conventions, or keep coding-agent instructions minimal and reference-backed.
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, creat
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.
Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
Use for every request to commit changes or draft a commit message. Creates Sentry-style conventional commits with issue references.
Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.
Related frontend skillsscan passed
Combines all of the `better-*` skills into a single review across accessibility, layout, writing, typography, color and UI polish.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
PostHog error tracking for Next.js
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.