slide-density-rules
Fix slides that are documents in landscape mode — the one-point-per-slide rule, the projection-vs-reading fork that decides density, the text diet (headlines and evidence, prose to notes), and the glance test. Use when asked my slides are too busy, how much text per slide, fix this wall-of-bullets deck, or make this readable from the back of the room. Produces the density diagnosis, the per-slide fixes (split, strip, or move-to-notes), the projection/document fork decision, and the glance-test results.
npx skills add mohitagw15856/pm-claude-skills --skill slide-density-rules --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Slide Density Rules Skill The wall-of-bullets slide fails twice simultaneously: the audience reads instead of listening (reading speed beats talking speed, so they finish and disengage while the presenter catches up), and nothing on it is retained because everything competed. The fix starts with a fork most decks never take: is this *projected* (accompanying a live talk — then slides are billboards: one point, big, glanceable) or *read* (sent as a document — then it's a doc wearing slide clothes, and density is fine but it should be built as a [outline-before-prose](../outline-before-prose/SKILL.md) memo-deck on purpose)? Hybrid decks that try both do both badly; the rules below are the fork, then the diet. ## What This Skill Produces - **The fork decision** — projected / reading-deck / both-needed (= two artifacts, honestly) - **The density diagnosis** — per slide: points-per-slide count, the glance-test verdict - **The fixes** — split (two points → two slides), strip (prose → the speaker's mouth), demote (detail → notes/appendix) - **The glance test results** — three seconds per slide: what survives, what was noise ## Required Inputs Ask for these if not provided: - **The deck
- What This Skill Produces
- Required Inputs
- Framework: The Density Rules
- Output Format
- The Fork Decision
- The Diagnosis & Fixes
- The Redistribution
- Quality Checks
- Anti-Patterns
What does the slide-density-rules skill do?
Fix slides that are documents in landscape mode — the one-point-per-slide rule, the projection-vs-reading fork that decides density, the text diet (headlines and evidence, prose to notes), and the glance test. Use when asked my slides are too busy, how much text per slide, fix this wall-of-bullets deck, or make this readable from the back of the room. Produces the density diagnosis, the per-slide fixes (split, strip, or move-to-notes), the projection/document fork decision, and the glance-test results.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill slide-density-rules --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.