explaining-code

Produce accurate, consistent, easy-to-read HTML documentation that explains a codebase — one feature, one subsystem, or a whole repository — by reading the real source and tracing every claim to a file:line. Use this whenever the user asks to "explain how X works", "document this repo/feature", "walk me through the codebase", "create a diagram of this flow", "how does this module/pipeline/endpoint work", or wants a visual, structured explanation of code they can keep and share. Prefer this skill over an off-the-cuff prose answer whenever the explanation would benefit from structure, diagrams, or a document the user keeps — even if they do not say the word "documentation".