explain

Explain complex code, systems, or concepts with concrete examples and step-by-step walkthroughs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mickaelyoshua/dev --skill explain-mickaelyoshua
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/mickaelyoshua/dev/tree/main/.claude-skills/explain
Command: npx skills add https://github.com/mickaelyoshua/dev --skill explain-mickaelyoshua

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explain complex code, systems, or concepts in depth using concrete, real-world examples to reveal how and why they work.

Core Features & Use Cases

  • Start with WHY: establish the problem the thing solves before discussing how it works.
  • Use concrete examples: ground explanations with tangible, real-world scenarios.
  • Build incrementally: relate to what the user already knows and progressively expand the detail.
  • Show the flow: trace data and control flow through components or steps.
  • Name the tradeoffs: highlight design decisions, benefits, and compromises.
  • Scope large targets: provide high-level overviews first, then deep-dives into critical parts.

Quick Start

Provide a file or concept and I will explain it with WHY, concrete examples, and an incremental flow.

Frequently Asked Questions about explain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I explain complex code and systems step by step?

To explain complex code step by step, start with the problem being solved, use concrete examples, and build incrementally to trace data flow and key decisions. This makes the system mechanics clear.

Why does understanding data flow matter when explaining software architecture?

Understanding data flow matters because it illustrates how components interact and why specific design decisions were made. Tracing control flow through concrete examples grounds abstract architectures in tangible system behavior.

What is the best way to understand how an unfamiliar codebase works?

The best way to understand an unfamiliar codebase is to scope large targets with a high-level overview first, then deep-dive into critical parts. This establishes the problem context before examining implementation details.

Can I use this approach to explain abstract programming concepts?

Yes, you can explain abstract programming concepts by relating them to what the user already knows and progressively expanding detail. Grounding explanations in concrete scenarios clarifies abstract ideas without misleading conclusions.

How to highlight tradeoffs and design decisions when explaining systems?

To highlight tradeoffs when explaining systems, name the design decisions, benefits, and compromises explicitly. Start with why the architecture solves a specific problem, then show the flow to reveal its constraints.