What problem does it solve? Developers often ask "why" and "how" questions about concepts, tools, errors, or architecture decisions and get generic answers disconnected from their actual project. This Skill delivers conceptual explanations grounded in the project's own documentation, stack, and business rules, closing knowledge gaps without turning the answer into an implementation task. ## Core Features & Use Cases - Project-Aware Explanations: Selectively loads only relevant docs (backend-standards.md, data-model.md, api-spec.yml, OpenSpec config) based on the topic instead of reading the entire repository. - Structured Teaching Format: Provides a concept summary, mental model, practical project example, alternatives with trade-offs, common mistakes, and an optional quiz. - Clear Boundaries: Strictly educational—it never edits files, writes code, creates commits, or runs commands, deferring action requests to the appropriate workflow skill. - Use Case: A developer asks "Why do we separate CustomerOrder and SupplierOrder?" and receives an explanation tied to the supplier-fulfilled ecommerce domain model, including a mental model, a real workflow example, and common misconceptions to avoid. ## Quick Start Ask the explain skill why this project separates CustomerOrder and SupplierOrder in the data model.
