Explain any concept, system, codebase, technology, or process using a structured three-section format -- High-Level overview, Break-Down, and Glossary. Use this skill whenever the user asks you to explain, describe, walk through, or help them understand something -- whether it's a piece of code, an architecture, a protocol, a framework, a design pattern, an algorithm, a business process, or any technical or non-technical topic. Also use this skill when the user says things like "what is...", "how does...work", "can you break down...", "help me understand...", "ELI5", or "walk me through...". Even if the user doesn't explicitly say "explain", if the intent is clearly to understand something rather than to build or fix something, use this skill.
Coach a learner through hands-on coding practice in a tutorial repository. Use this skill whenever the user is working inside a tutorial repo (generated by the "tutorial" skill) and starts a milestone, picks up a TODO step, asks for a hint, thinks aloud about their approach, shares code they've written, or seems stuck. Also trigger when the user says "guide", "coach me", "I'm starting milestone", "next step", "I'm stuck", "what should I do", "is this right", or mentions working through practice steps. This skill acts as a patient senior-engineer mentor — it does NOT give answers unless explicitly asked; it gives feedback, asks guiding questions, and tracks what the learner struggles with.
Generate a structured learning repository for any software-development topic. Use this skill whenever the user says "tutorial", "teach me", "I want to learn", "create a learning project for", "help me study", or otherwise indicates they want to learn a new technology, framework, language, or software concept from scratch. Also trigger when the user wants to create a hands-on practice project with guided steps, or when they mention creating a beginner/intermediate/advanced course on a topic. This skill creates the repo — the companion "guide" skill coaches the learner through the practice.
Write a revealing architectural walkthrough as educational material — for a PR, design decision, code structure, or feature. Use when the user wants to create learning material for junior engineers, explain *why* decisions were made, or document the reasoning behind an architecture. Trigger on "walkthrough", "write a walkthrough", "educational material", "explain the decision", "why was this designed this way", or when asked to produce a document that teaches through re-experiencing a decision rather than summarising it.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Four Claude Code skills that cover the full learning loop — understand what exists, and learn what's new.
| Skill | What it does |
|---|---|
explain | Structures any explanation into three sections: High-Level, Break-Down, Glossary. Use for "what is…", "how does…work", "ELI5", or "walk me through…" questions. |
walkthrough | Writes a revealing architectural walkthrough — a document that re-creates the experience of making a design decision instead of summarising it. Built for junior engineers reading about a PR, refactor, or architecture. |
tutorial | Generates a self-contained learning repository for any software topic — theory with Mermaid diagrams plus a practice project with milestone-based TODOs the learner builds commit-by-commit. |
guide | Coaches the learner through a tutorial repo. Acts as a patient senior-engineer mentor — asks questions, escalates hints, tracks weak points. Does NOT give answers unless explicitly asked. |
explain and walkthrough help you understand code that already exists. tutorial and guide pair up to help you learn something new — one generates the material, the other coaches you through it without spoiling the answer.
Inside Claude Code:
/plugin marketplace add iannbing/skills-for-learning
/plugin install skills-for-learning@skills-for-learning
After install, the skills are available as /skills-for-learning:explain, /skills-for-learning:walkthrough, /skills-for-learning:tutorial, and /skills-for-learning:guide. They're also model-invoked — Claude will use them automatically when the request matches.
Update later with:
/plugin marketplace update skills-for-learning
npx skills add iannbing/skills-for-learning/explain
npx skills add iannbing/skills-for-learning/walkthrough
npx skills add iannbing/skills-for-learning/tutorial
npx skills add iannbing/skills-for-learning/guide
Clone the repo and either:
load as a plugin during development: claude --plugin-dir ./skills-for-learning
or copy individual skills into your user skills dir:
mkdir -p ~/.claude/skills
cp -r skills/explain ~/.claude/skills/
cp -r skills/walkthrough ~/.claude/skills/
cp -r skills/tutorial ~/.claude/skills/
cp -r skills/guide ~/.claude/skills/
Installed this way the skills have no namespace prefix — they're just /explain, /walkthrough, /tutorial, and /guide.
explain/skills-for-learning:explain how does OAuth 2.0 authorization code flow work
Produces:
API, HTTP, DNS filler).Calibrated for a junior engineer — the glossary skips general-computing basics and covers only terms specific to the topic.
walkthrough/skills-for-learning:walkthrough PR #482
/skills-for-learning:walkthrough src/auth/session.ts
/skills-for-learning:walkthrough why we moved from Redux to Zustand
Produces a markdown document at <git-repo-root>/personal/walkthrough-<slug>.md that:
Add personal/walkthrough-*.md to your .gitignore — these are personal study notes.
tutorialRun inside an empty directory where you want the learning repo to live.
/skills-for-learning:tutorial GraphQL
/skills-for-learning:tutorial teach me Kubernetes, intermediate level
/skills-for-learning:tutorial React Testing Library
Generates learn-<topic>/ containing:
npx claudepluginhub iannbing/skills-for-learning --plugin skills-for-learningMake your AI agent code with your project's architecture, rules, and decisions.
Access official Microsoft documentation, API references, and code samples for Azure, .NET, Windows, and more.
29 specialized Claude Code skills for building architecture. Core 18 skills cover design theory, building programming, concept design, building typology, spatial planning, envelope design, structural systems, MEP services, daylighting, materials, building codes, accessibility, fire safety, acoustics, building-scale sustainability, and construction documentation. Country-specific dossiers (v1.1.0) provide clause-level regulatory precision for 10 priority jurisdictions: India (NBC 2016, ECBC, IS codes, state DCRs), UAE (Dubai Building Code 2021, ADIBC, UAE FLS Code 2018, Estidama, Al Sa'fat), Saudi Arabia (SBC 201-1001, Mostadamah, NEOM/Royal Commission jurisdictions), USA (IBC 2024, IECC 2024, NFPA 101, ADA 2010, ASCE 7-22, state amendments incl. CA Title 24, NYC, FL HVHZ), UK (Building Regulations 2010 + Approved Documents A-S, Building Safety Act 2022, BSR/HRB, Scotland/Wales/NI), Germany (MBO + 16 LBOs, GEG 2023, DIN 18040/4109/4108, Eurocode NAs), Singapore (BCA Building Control Act, SCDF Fire Code 2018, Green Mark 2021, URA Master Plan), Japan (Building Standards Act, two-level seismic design, Sho-Energy Ho 2015, Heart Building Law, AIJ standards, BCJ evaluation), China (GB 50352-2019, GB 50016-2014, GB 50011-2010, JGJ residential energy codes, DB local supplements, sunlight rights), Australia (NCC 2022 Vol 1-3, AS/NZS 1170 series, AS 1428.1-2021, NatHERS 7-star, state planning systems). Geographic-foundations skill auto-detects jurisdiction and routes to the correct country dossier. References 50+ architects and theorists, IBC/Eurocodes/ASCE/ASHRAE/ADA/NFPA/ISO standards, sustainability frameworks (LEED, BREEAM, Passive House, DGNB, CASBEE, Green Mark, Green Star, NABERS, Mostadamah, Estidama, GRIHA, IGBC). Includes 7 Python calculators.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Comprehensive C4 architecture documentation workflow with bottom-up code analysis, component synthesis, container mapping, and context diagram generation
Build and maintain an LLM-curated personal knowledge base in your project — Andrej Karpathy's LLM Wiki pattern, designed to scale to thousands of pages without becoming a context bottleneck. Now with an optional compiled graph layer for typed, provenance-backed relationships.