tufte-slide-design
This skill applies Edward Tufte's data visualization principles from "The Visual Display of Quantitative Information" to create high-impact slides. Use when designing presentations, creating charts/graphs, reviewing slides for clarity, or transforming data into visual displays. Triggers on phrases like "make a slide", "create presentation", "design chart", "visualize data", "review my slides", or "make this more impactful".
What this skill does
# Tufte Slide Design
Apply Edward Tufte's principles from "The Visual Display of Quantitative Information" to create presentations that communicate complex ideas with clarity, precision, and efficiency.
## Core Philosophy
Tufte's central insight: **"Clutter and confusion are failures of design, not attributes of information."**
Information overload is rarely the problem—poor information design is. The goal is graphical excellence: the well-designed presentation of interesting data combining substance, statistics, and design.
## The Five Laws of Data-Ink
When designing any slide with data:
1. **Above all else, show the data** - Data is the primary focus
2. **Maximize the data-ink ratio** - Every pixel should convey information
3. **Erase non-data-ink** - Remove decorations that don't inform
4. **Erase redundant data-ink** - Eliminate duplicate information carriers
5. **Revise and edit** - Continuously refine toward simplicity
### Data-Ink Ratio Formula
```
Data-Ink Ratio = Ink presenting data / Total ink used
```
Target: As close to 1.0 as possible. Each element should earn its place.
## Slide Design Workflow
### Step 1: Identify the Data Story
Before creating any slide, answer:
- What is the ONE key insight this slide must communicate?
- What data supports this insight?
- What would be lost if this slide were removed?
### Step 2: Apply the Chartjunk Elimination Checklist
Remove or minimize:
| Chartjunk Element | Action |
|-------------------|--------|
| 3D effects | Flatten to 2D |
| Gradient fills | Use solid colors |
| Heavy gridlines | Lighten or remove |
| Decorative borders | Remove entirely |
| Background images | Remove unless data |
| Drop shadows | Remove |
| Unnecessary legends | Label directly on chart |
| Excessive tick marks | Reduce to minimum |
| Moiré patterns | Use solid fills |
### Step 3: Check Graphical Integrity
Tufte's Six Principles of Graphical Integrity:
1. **Proportional representation** - Visual size must match numerical quantity
2. **Clear labeling** - Label data directly on the graphic
3. **Show data variation, not design variation** - Design should not distort
4. **Use proper monetary units** - Deflate/standardize when showing money over time
5. **Match dimensions** - Don't use 2D/3D to represent 1D data
6. **Preserve context** - Never quote data out of context
### Step 4: Calculate the Lie Factor
```
Lie Factor = Size of effect in graphic / Size of effect in data
```
- Lie Factor = 1.0: Truthful
- Lie Factor > 1.0: Overstates the effect
- Lie Factor < 1.0: Understates the effect
**Example violation**: A 53% numerical change shown as 783% visual change = Lie Factor of 14.8
### Step 5: Apply Advanced Techniques
#### Small Multiples
Use for comparing related data:
- Same graphic structure repeated with different data slices
- Enables visual comparison within eye span
- "Move to the heart of visual reasoning—to see, distinguish, choose"
#### Sparklines
Word-sized graphics for inline data display:
- High resolution in small space
- Embed in tables or text
- "Datawords: data-intense, design-simple, word-sized graphics"
#### Direct Labeling
Instead of legends, label data directly:
- Reduces eye movement
- Eliminates legend decoding
- Places information where attention focuses
## Slide Types and Tufte Approaches
### Data-Heavy Slides
1. Strip unnecessary gridlines
2. Use range-frame axes (only show data range)
3. Consider small multiples for comparisons
4. Direct label instead of legends
5. Horizontal orientation where possible
### Text-Heavy Slides (Anti-Pattern)
Tufte's critique of bullet points ("The Cognitive Style of PowerPoint"):
- Bullet lists fragment thought
- Hierarchical bullets obscure relationships
- Low information density
**Alternative approaches:**
- Use sentence-case prose for complex ideas
- Provide detailed handouts instead
- Show data tables with full context
- Use visual diagrams showing relationships
### Title Slides
Apply same principles:
- Remove decorative elements
- Use typography for hierarchy, not ornament
- Every word should contribute meaning
## Quick Reference: Before/After Patterns
### Bar Charts
**Before**: 3D bars, gradient fills, heavy gridlines, legend below
**After**: 2D bars, solid colors, no gridlines, direct labels
### Line Charts
**Before**: Multiple colors, thick lines, point markers, legend
**After**: Direct labels on lines, minimal markers, reduced palette
### Pie Charts
**Tufte's view**: Generally avoid. If required:
- Never use 3D
- Limit to 3-4 slices maximum
- Consider bar chart instead
### Tables
**Before**: Heavy borders, alternating row colors, centered text
**After**: Minimal rules, left-aligned text, whitespace for separation
## Resources
For detailed principles and examples, reference:
- `references/tufte-principles.md` - Complete principle documentation with examples
- `references/slide-checklist.md` - Quick checklist for slide review
## Anti-Patterns to Avoid
1. **PowerPoint defaults** - Override all default templates and effects
2. **Chart templates** - Design from data, not from template
3. **Decoration for engagement** - Data is engaging when well-presented
4. **Hiding complexity** - Show the complexity, design it well
5. **Animation for emphasis** - Use visual hierarchy instead
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.