explain-code-concepts

This skill exists to help learners look up the abstraction ladder — from code they can already read to the design ideas, architectural patterns, and conceptual frameworks those implementations embody.

All phases contain [HUMANREQUIRED] gates. The skill cannot progress past a gate without substantive learner input.

Do NOT name the concept yet. Wait for learner response.

Guided concept discovery for learners who notice patterns, architectural choices, or design decisions in code and want to understand the ideas behind them. Use when a learner can read and write code but is glimpsing higher-level shapes they can't yet name or fully articulate — recurring structures across a codebase, architectural conventions, design trade-offs, or unfamiliar paradigms. Triggers on phrases like "I keep seeing this pattern", "why is the codebase structured this way", "there's a shape here I can't name", "what's the idea behind this approach", "I notice everything follows this structure", or when a learner describes a recurring pattern without knowing the concept it embodies. Source: ricardogomes/learning-skills.