Paper First Principles
Overview
Convert academic papers into progressive, engineer-friendly documentation using first principles thinking.
When to Use
Use when:
- You need to understand a research paper deeply from an engineering perspective
- Extracting design patterns, system architectures, or algorithms from academic literature
- Preparing technical knowledge sharing or documentation for engineering teams
- Mapping theoretical research to practical software engineering applications
Don't use for:
- Papers without clear technical contributions (survey papers, opinion pieces)
- One-off reading without need for structured documentation
- Standard practices already well-documented elsewhere
Quick Start
# Basic usage
kimi paper-first-principles https://arxiv.org/abs/xxxx.xxxxx
# Engineer perspective with domain focus
kimi paper-first-principles paper.pdf --audience engineer --domain distributed-systems
# Output to file
kimi paper-first-principles paper.pdf --output ./docs/analysis.md
Output Structure
Generated documents contain 8 standard sections:
| Section |
Content |
Audience |
| Opening |
One-sentence core insight |
All |
| Mechanism Breakdown |
Comparative analysis tables |
Engineers, Researchers |
| First Principles |
Problem essence and design rationale |
All |
| Progressive Deep Dive |
Layered complexity (simple → complex) |
Engineers, Researchers |
| Edge Cases |
Common pitfalls and misconceptions |
Engineers |
| Decision Tree |
When/how to apply |
Engineers, Managers |
| Engineering Checklist |
Actionable verification items |
Engineers |
| Summary |
Reusable design patterns |
All |
Paper Types & Progressive Paths
| Type |
Characteristics |
Progressive Path |
| Algorithm |
New algorithms/models |
Example → Core mechanism → Optimizations |
| System |
Architecture/engineering |
Single-node → Distributed → Production |
| Theory |
Theoretical analysis |
Problem → Theorem → Proof → Application |
Parameters
--audience
engineer: Implementation details, design patterns, edge cases
researcher: Technical depth, related work comparison, theory
manager: Problem context, decision rationale, risk assessment
--domain (optional)
Engineering domain for contextual mapping:
distributed-systems: Distributed systems, microservices
storage: Storage systems, file systems
database: Databases, data warehouses
network: Networks, CDN, load balancing
ml-system: ML systems, recommendation systems
Analysis Workflow
This skill processes papers in 6 stages using prompts in prompts/:
- Core Extraction (
extract_core.txt): Identify contributions and key decisions
- First Principles (
first_principles.txt): Trace problem essence and rationale
- Progressive Layers (
progressive_layers.txt): Organize by complexity
- Engineering Map (
engineering_map.txt): Map to software patterns (engineer audience only)
Output Templates
Templates in templates/ provide structure for each paper type:
system.md: System papers (infrastructure, architecture)
algorithm.md: Algorithm papers (models, methods)
theory.md: Theory papers (analysis, proofs)
Examples
See examples/attention_residuals.md for a complete example converting the Attention Residuals paper into an engineer-friendly analysis with distributed systems mappings.
Resource Loading Guide
Always load in this order:
- Parse paper → Extract core (use
prompts/extract_core.txt)
- First principles analysis (use
prompts/first_principles.txt)
- Progressive organization (use
prompts/progressive_layers.txt)
- Engineering mapping (if
--audience engineer, use prompts/engineering_map.txt)
- Generate output (use appropriate template from
templates/)
Constraints & Notes
- Paper quality matters: clear abstract and introduction required
- Output depth auto-adjusts based on
--audience
- Engineering mapping accuracy depends on
--domain setting
- Complex proofs may need manual verification
1---2name: paper-first-principles3description: Use when converting academic papers into engineer-friendly documentation, extracting design patterns from research, or preparing technical knowledge sharing4version: 1.05author: agent6tags: [research, learning, engineering]7metadata:8 source: https://skillmd.com/skills/dqz00116/paper-first-principles9---1011# Paper First Principles1213## Overview1415Convert academic papers into progressive, engineer-friendly documentation using first principles thinking.1617## When to Use1819**Use when:**20- You need to understand a research paper deeply from an engineering perspective21- Extracting design patterns, system architectures, or algorithms from academic literature22- Preparing technical knowledge sharing or documentation for engineering teams23- Mapping theoretical research to practical software engineering applications2425**Don't use for:**26- Papers without clear technical contributions (survey papers, opinion pieces)27- One-off reading without need for structured documentation28- Standard practices already well-documented elsewhere2930## Quick Start3132```bash33# Basic usage34kimi paper-first-principles https://arxiv.org/abs/xxxx.xxxxx3536# Engineer perspective with domain focus37kimi paper-first-principles paper.pdf --audience engineer --domain distributed-systems3839# Output to file40kimi paper-first-principles paper.pdf --output ./docs/analysis.md41```4243## Output Structure4445Generated documents contain 8 standard sections:4647| Section | Content | Audience |48|---------|---------|----------|49| **Opening** | One-sentence core insight | All |50| **Mechanism Breakdown** | Comparative analysis tables | Engineers, Researchers |51| **First Principles** | Problem essence and design rationale | All |52| **Progressive Deep Dive** | Layered complexity (simple → complex) | Engineers, Researchers |53| **Edge Cases** | Common pitfalls and misconceptions | Engineers |54| **Decision Tree** | When/how to apply | Engineers, Managers |55| **Engineering Checklist** | Actionable verification items | Engineers |56| **Summary** | Reusable design patterns | All |5758## Paper Types & Progressive Paths5960| Type | Characteristics | Progressive Path |61|------|-----------------|------------------|62| **Algorithm** | New algorithms/models | Example → Core mechanism → Optimizations |63| **System** | Architecture/engineering | Single-node → Distributed → Production |64| **Theory** | Theoretical analysis | Problem → Theorem → Proof → Application |6566## Parameters6768### `--audience`6970- `engineer`: Implementation details, design patterns, edge cases71- `researcher`: Technical depth, related work comparison, theory72- `manager`: Problem context, decision rationale, risk assessment7374### `--domain` (optional)7576Engineering domain for contextual mapping:77- `distributed-systems`: Distributed systems, microservices78- `storage`: Storage systems, file systems 79- `database`: Databases, data warehouses80- `network`: Networks, CDN, load balancing81- `ml-system`: ML systems, recommendation systems8283## Analysis Workflow8485This skill processes papers in 6 stages using prompts in `prompts/`:86871. **Core Extraction** (`extract_core.txt`): Identify contributions and key decisions882. **First Principles** (`first_principles.txt`): Trace problem essence and rationale893. **Progressive Layers** (`progressive_layers.txt`): Organize by complexity904. **Engineering Map** (`engineering_map.txt`): Map to software patterns (engineer audience only)9192## Output Templates9394Templates in `templates/` provide structure for each paper type:95- `system.md`: System papers (infrastructure, architecture)96- `algorithm.md`: Algorithm papers (models, methods)97- `theory.md`: Theory papers (analysis, proofs)9899## Examples100101See `examples/attention_residuals.md` for a complete example converting the Attention Residuals paper into an engineer-friendly analysis with distributed systems mappings.102103## Resource Loading Guide104105**Always load in this order:**1061071. **Parse paper** → **Extract core** (use `prompts/extract_core.txt`)1082. **First principles analysis** (use `prompts/first_principles.txt`)1093. **Progressive organization** (use `prompts/progressive_layers.txt`)1104. **Engineering mapping** (if `--audience engineer`, use `prompts/engineering_map.txt`)1115. **Generate output** (use appropriate template from `templates/`)112113## Constraints & Notes114115- Paper quality matters: clear abstract and introduction required116- Output depth auto-adjusts based on `--audience`117- Engineering mapping accuracy depends on `--domain` setting118- Complex proofs may need manual verification