Skip to content

brycewang-stanford/Auto-Empirical-Research-Skills / skills/13-scunning1975-MixtapeTools/skills/compiledeck

compiledeck

Verified

Create and compile beautiful Beamer presentations following the Rhetoric of Decks philosophy. Use when making slides, creating decks, or compiling .tex presentation files.

FileKindSize
SKILL.mdskill md12.1 KB
domain_patterns.mdmarkdown4.5 KB
palette_reference.mdmarkdown2.6 KB
tikz_rules.mdmarkdown15.1 KB

domain_patterns.md

View on GitHub
# Domain-Specific Deck Patterns

## Academic Seminar (60-90 minutes, critical audience)

### Recommended structure
1. **Title slide**
2. **The Puzzle** — one surprising fact or unanswered question. NOT "Motivation" with bullets.
3. **What This Paper Does** — one slide, three contributions max
4. **Related Literature** — why existing work is insufficient (not a list of papers)
5. **Data and Setting** — show the data visually, not just describe it
6. **Identification Strategy** — show the variation: a map, a timeline, an event study
7. **Main Results** — one coefficient prominent, supporting info subordinate
8. **Robustness** — key checks only. Full battery in appendix.
9. **Devil's Advocate** — strongest objection + your response. Builds credibility.
10. **Implications**
11. **Closing** — one takeaway, not "Questions?"

### Domain-specific rules
- Lead with the QUESTION, not the literature
- Identification strategy appears by slide 6 — skeptics want it early
- Regression tables: highlight 1-2 coefficients, not the full table
- Acknowledge limitations BEFORE Q&A — preempt Referee 2
- Every title is an assertion: "Policy X increased Y by Z%"
- Figures: readable from back row, treatment date marked, pre/post distinguished, key pattern annotated, confidence intervals shaded, title states the claim

---

## Teaching Lecture (50-75 minutes, learners)

### How this differs from a seminar
- **Clarity over compression** — more text per slide is acceptable because students take notes from slides
- **Repetition is OK** — learning requires revisiting concepts
- **Progressive revelation** — use `\pause` (Beamer overlays) for step-by-step derivations
- **Definitions get their own slides** with block environments
- **"Why does this matter?"** should appear frequently

### Domain-specific rules
- Font size floor is 18pt (lower than seminars because students sit closer)
- Bullet points are acceptable for lists of properties, axioms, or steps
- Show derivations step by step, not just final results
- Include worked examples
- Proofs use `align` environments revealed step by step with `\pause`

---

## Working Deck (coauthors, variable length)

### How this differs from external
- MORE detail is acceptable and expected
- Document choices: "We chose X over Y because..."
- Preserve uncertainty: "This could be Z but we haven't verified"
- Flag unknowns explicitly with a consistent visual marker (e.g., a colored box)
- Include data quality notes, merge diagnostics, sample construction details
- Regression tables can be fuller — coauthors will scrutinize
- Still follow visual hierarchy — dense does NOT mean ugly

### Domain-specific rules
- Titles still assert, but can be more technical
- Include appendix slides with backup analyses
- Date everything — assume forgotten context when revisited later
- Include the "why" behind methodological decisions

---

## The Dual Audience Problem

All decks increasingly circulate beyond their live audience. Strategies:
- **Assertion titles** carry the argument for readers who skim
- **Figures should be self-interpreting** — title, labels, annotations, source notes
- **Footnotes** in small text provide context for later readers
- **Appendix slides** after `\appendix` for backup material

---

## Opening and Closing Patterns

### Openings that work
- **The surprising number**: "In 2024, 47% of..." (big, centered, no decoration)
- **The puzzle**: "Why did X happen when theory predicts Y?"
- **The provocative claim**: "Everything we thought about Z is wrong."
- **The human story**: "When Maria arrived at the clinic..." (then zoom out to data)

### Openings that fail
- "Motivation" with four bullet points
- "Outline" listing every section
- "Thank you for inviting me to speak"

### Closings that work
- One sentence the audience will remember tomorrow
- A call to action or implication for their work
- A return to the opening puzzle, now resolved

### Closings that fail
- "Questions?"
- "Thank you!"
- A summary slide restating every finding

---

## The Devil's Advocate Slide

This is the most underused persuasion technique in academic presentations. It works because it builds credibility (ethos) through transparency:

1. State the strongest objection to your argument
2. Acknowledge what makes it compelling
3. Explain why it doesn't hold, or how you've addressed it

Format:
> "A skeptic would say: [strongest objection]"
> "This is a fair concern because [why it's reasonable]"
> "Here is how we address it: [your response]"

This should appear BEFORE Q&A, not as a response to it.
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall