What problem does it solve? When you encounter unfamiliar concepts, mechanisms, or flows in a codebase, generic explanations from documentation or tutorials do not tell you how they actually work in your project. This Skill reads your project's code and docs first, then explains each item grounded in real implementations with exact file and line references. ## Core Features & Use Cases - Project-grounded explanations: Each concept is covered in four parts—what it is, how it is implemented in this project, key code locations (file:line), and project-specific pitfalls and conventions. - No fabrication: Conclusions without code evidence are explicitly marked as unverified rather than guessed; line numbers are re-read before delivery. - Structured output: Delivers Markdown with a top-level title, itemized sections, a closing "what is this project" summary, and a reference table of cited locations. - Use Case: You join a legacy Java backend project and ask it to explain the permission-check flow and the caching mechanism; it traces the call chains, cites exact classes and lines, and flags conventions unique to this repo. ## Quick Start Explain how the authentication flow and the retry mechanism work in this project, citing the actual code locations.
