layered-first-principles-teaching
Use when explaining complex concepts to others, designing training materials, or preparing technical presentations with progressive disclosure
Best use case
layered-first-principles-teaching is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when explaining complex concepts to others, designing training materials, or preparing technical presentations with progressive disclosure
Teams using layered-first-principles-teaching should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/layered-first-principles-teaching/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How layered-first-principles-teaching Compares
| Feature / Agent | layered-first-principles-teaching | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when explaining complex concepts to others, designing training materials, or preparing technical presentations with progressive disclosure
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Layered First Principles Teaching ## Overview Transform complex concepts into progressive, first-principles explanations that build understanding layer by layer. ## When to Use **Use when:** - You need to explain a complex concept to someone with less domain knowledge - You're designing training materials, tutorials, or educational content - You're preparing a technical presentation and need progressive disclosure - A topic has multiple abstraction layers that require cognitive scaffolding - You need to bridge the gap between intuitive understanding and technical depth **Don't use when:** - The concept is simple and doesn't benefit from layered decomposition - You need quick reference documentation or a terse answer - The audience already has deep expertise and only needs edge cases or implementation details ## Quick Start ```bash # Explain a concept progressively kimi layered-first-principles-teaching "Explain blockchain" # Target specific audience kimi layered-first-principles-teaching "Explain transformers" --audience beginner # Output to file kimi layered-first-principles-teaching "Explain consensus algorithms" --output ./tutorial.md ``` ## Output Structure Generated explanations contain 6 standard sections: | Section | Content | Purpose | |---------|---------|---------| | **Opening** | One-sentence essence + intuitive analogy | Immediate understanding | | **First Principles** | Problem essence, why existing solutions fail | Foundation building | | **Progressive Layers** | 3-4 layers from intuition to technical detail | Scaffolding learning | | **Analogies** | Cross-domain comparisons | Relating to known concepts | | **Visualizations** | ASCII diagrams, mental models | Spatial understanding | | **Summary** | Key takeaways + further reading | Retention & next steps | ## Audience Levels | Level | Characteristics | Approach | |-------|-----------------|----------| | **Beginner** | No prior knowledge | Heavy analogies, minimal jargon, focus on "why" | | **Intermediate** | Some domain knowledge | Balance of intuition and technical detail | | **Expert** | Deep domain knowledge | Focus on nuances, edge cases, implementation | ## Teaching Patterns This skill uses progressive disclosure patterns from `prompts/`: 1. **First Principles Analysis** (`first_principles.txt`): Strip away abstractions, find root causes 2. **Layered Decomposition** (`layered_decomposition.txt`): Break into 3-4 cognitive layers 3. **Analogy Generation** (`analogy_generation.txt`): Find relatable comparisons 4. **Visualization Design** (`visualization_design.txt`): Create mental models and diagrams ## Templates Output templates in `templates/` provide structure for: - `concept.md`: General concept explanation - `algorithm.md`: Algorithm walkthrough - `system.md`: System architecture explanation ## Examples See `examples/` for completed explanations: - `blockchain_explained.md`: From "digital ledger" to Byzantine fault tolerance - `transformers_explained.md`: From "pattern matching" to attention mechanisms ## Workflow When explaining a concept: 1. **Load first principles prompt** → Identify core problem and breakthrough insight 2. **Load layered decomposition prompt** → Structure into 3-4 cognitive layers 3. **Load analogy generation prompt** → Find 2-3 cross-domain analogies 4. **Load visualization design prompt** → Create ASCII diagrams and mental models 5. **Apply appropriate template** → Generate final explanation ## Constraints - Maximum 4 layers to avoid cognitive overload - Each layer must build on previous without introducing new prerequisites - Analogies must be familiar to target audience - Visualizations should work in plain text (ASCII)
Related Skills
paper-first-principles
Use when converting academic papers into engineer-friendly documentation, extracting design patterns from research, or preparing technical knowledge sharing
unity-mcp
Use when controlling Unity editor via AI, automating scene operations, or programmatically generating Unity assets and scripts
ue5-umg
Use when building HUDs, menus, inventory screens, settings panels, or any widget-based interface in Unreal Engine 5. Also use when connecting C++ logic to UMG Blueprint visuals, handling gamepad or keyboard focus navigation, managing UI state, creating widget animations, or troubleshooting UMG performance issues like frame drops, hitches, or widget memory leaks.
taskmaster-skill
Use when managing complex project plans, tracking multi-phase task progress, or prioritizing development tasks
research-to-practice
Use when applying academic research to practical workflows, optimizing existing processes based on papers, or extracting actionable insights from research
requirement-clarification
Use when receiving ambiguous instructions, preparing for state-changing operations, or needing explicit user confirmation
mvp-design
Use when designing new modules from scratch, creating minimal viable prototypes, or establishing architectural decisions before implementation
msvc-build
Use when compiling MSVC C++ projects, debugging build errors, or performing clean and incremental builds
knowledge-base-cache
Use when managing large knowledge bases, reducing API costs, or implementing multi-tier caching for frequent queries
kimicode-vision-bridge
Use when the current Agent LLM cannot process images directly and visual analysis is needed — bridges images through KimiCode CLI print mode to a multimodal Kimi model for text description
hexo-blog-update
Use when creating, editing, or publishing Hexo blog posts
git-workflow
Use when committing code, pushing changes, or managing Git operations that require safety checks