agentleFS
Dqz00116Dqz00116/skill-lib/layered-first-principles-teaching/SKILL.md

layered-first-principles-teaching

Skill22 starsChanged 7 months agoMITView on GitHub

Use when explaining complex concepts to others, designing training materials, or preparing technical presentations with progressive disclosure

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When explaining a concept:

    line 87

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

# 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:

SectionContentPurpose
OpeningOne-sentence essence + intuitive analogyImmediate understanding
First PrinciplesProblem essence, why existing solutions failFoundation building
Progressive Layers3-4 layers from intuition to technical detailScaffolding learning
AnalogiesCross-domain comparisonsRelating to known concepts
VisualizationsASCII diagrams, mental modelsSpatial understanding
SummaryKey takeaways + further readingRetention & next steps

Audience Levels

LevelCharacteristicsApproach
BeginnerNo prior knowledgeHeavy analogies, minimal jargon, focus on "why"
IntermediateSome domain knowledgeBalance of intuition and technical detail
ExpertDeep domain knowledgeFocus 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)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.