paper-to-intuition
Paper to Intuition
Transform dense academic papers into genuine understanding through layered explanation and visual intuition.
Process
- Get the paper - Ask for the arXiv link, PDF, or paper title
- Extract the core - Identify the single key insight (one sentence)
- Build the ladder - Create explanations at 4 levels
- Visualize intuition - Generate interactive diagrams
- Stress test understanding - "What breaks if we remove X?"
The Explanation Ladder
Generate explanations at each level, with each building on the last:
Level 1: ELI5 (1 paragraph)
- No jargon, no equations
- Use familiar analogies from everyday life
- A curious 10-year-old should roughly get it
Level 2: Undergraduate (2-3 paragraphs)
- Assume calculus, basic linear algebra, intro ML
- Introduce key terms with definitions
- Connect to textbook concepts they'd know
Level 3: Graduate (3-4 paragraphs)
- Assume ML fundamentals, optimization, probability
- Discuss relationship to prior work
- Explain why naive approaches don't work
- Cover the key equations with plain-English annotations
Level 4: Researcher (2-3 paragraphs)
- Assume field expertise
- Subtle technical contributions
- Limitations and open questions
- How this changes what's possible
Key Equations Breakdown
For each important equation:
[Equation in LaTeX]
In words: [Plain English translation]
Each term:
- [symbol]: [what it represents] [why it's there]
Intuition: [Why this mathematical form? What would change if we used a different form?]
Visual Intuition Artifact
Generate a self-contained HTML file with:
- Architecture diagram - Boxes and arrows showing information flow
- Interactive sliders - Manipulate key parameters, see effects
- Before/after comparisons - What the method improves over baselines
- Failure case visualization - When and why it breaks down
Use SVG for diagrams, vanilla JavaScript for interactivity. Dark theme, clean typography.
<!DOCTYPE html>
<html>
<head>
<title>[Paper Name] - Visual Intuition</title>
<style>
:root { --bg: #1a1a2e; --text: #eee; --accent: #4f8cff; }
/* Clean, research-aesthetic styling */
</style>
</head>
<body>
<h1>[Paper Title]</h1>
<p class="tldr">[One-sentence insight]</p>
<section id="architecture">
<svg><!-- Information flow diagram --></svg>
</section>
<section id="interactive">
<!-- Parameter sliders with live updates -->
</section>
<section id="comparisons">
<!-- Before/after, ablations -->
</section>
</body>
</html>
The "What Breaks?" Analysis
For each major component, explain:
- What it does - The role this component plays
- What breaks without it - Concrete failure mode
- Why this solution - Alternatives considered, why this won
- The tradeoff - What we pay for this choice (compute, complexity, assumptions)
Output Structure
Deliver as a structured document:
# [Paper Title]
**TL;DR:** [One sentence]
**Why it matters:** [One paragraph on significance]
## The Explanation Ladder
### ELI5
[...]
### Undergraduate Level
[...]
### Graduate Level
[...]
### Researcher Level
[...]
## Key Equations
### Equation 1: [Name]
[Breakdown as specified above]
## What Breaks If We Remove...
### [Component 1]
[Analysis]
### [Component 2]
[Analysis]
## Visual Intuition
[Link to or embed HTML artifact]
## Further Reading
- [Prerequisite paper 1]
- [Follow-up work 1]
Quality Standards
- Every analogy must be accurate, not just catchy
- Equations must be explained, not just translated
- Visuals must reveal structure, not just decorate
- The researcher-level section should contain insight, not just summary
- Admit when something is genuinely confusing or poorly explained in the original paper
More from ghostscientist/skills
ios-app-icon-generator
Generates a complete iOS app icon set with all required sizes. Use when asked to create an app icon, design an iOS icon, generate app store artwork, or make an icon for an iPhone/iPad app. Follows a philosophy-first approach - first defining the visual identity and concept, then producing production-ready icons.
17research-question-refiner
Helps transform a vague research interest into a concrete, tractable research question. Use when asked to refine a research idea, develop a research question, scope a research project, or figure out what to work on. Walks through systematic refinement with feasibility analysis.
14create-watchos-version
Analyzes existing iOS/macOS/Apple platform projects to create a comprehensive, phased plan for building a watchOS companion or standalone app. Use when users want to add watchOS support to an existing Apple platform app, create a Watch app version of their iOS app, or build watchOS features. The skill digests project architecture, identifies patterns, analyzes API compatibility, searches for current watchOS documentation, and produces a detailed implementation plan with API availability warnings before any code generation.
9implement-paper-from-scratch
Guides you through implementing a research paper step-by-step from scratch. Use when asked to implement a paper, code up a paper, reproduce research results, or build a model from a paper. Focuses on building understanding through implementation with checkpoint questions.
8turn-this-feature-into-a-blog-post
Generates a technical blog post from code implementation. Use when asked to write a blog post about a feature, explain an implementation for a blog, document code as a blog article, or create technical content from source code. Triggers on phrases like "write a blog post about", "turn this into a blog", "create a technical article", or "explain this for a blog".
5experiment-design-checklist
Generates a rigorous experiment design given a hypothesis. Use when asked to design experiments, plan experiments, create an experimental setup, or figure out how to test a research hypothesis. Covers controls, baselines, ablations, metrics, statistical tests, and compute estimates.
5