explain-my-applisted

# Explain My App Use this skill for people who vibe-coded an app and don't understand it. The output is not a chat answer — it is a **doc-set committed into their repo** (`docs/explained/` by default, configurable), written about THEIR code, linked together with `[[wikilinks]]`, and tracked by a git-SHA manifest so later runs can re-explain only what changed and quiz them on what they should know by now. Three modes share one doc-set: **explain** builds it, **re-explain** patches it, **quiz** tests it. ## Definition of Done - The doc-set exists in `docs/explained/` (or the directory the user chose). - A hub page `00-start-here.md` plus **8–20 depth pages**, sized to the repo (see sizing table). - **Every page passes the pedagogy checklist** (the table below). One failing row on one page = not done. - Exactly **one end-to-end walkthrough page** traces a single real user action through every layer with `path:line` at each hop. - Every generated page carries the frontmatter convention (`title:` + `source_files:`) so re-explain can map diffs to pages. - The manifest exists at `<docs-dir>/.manifest.json`, written with the repo's **current git SHA** via `manifest.py init` (or `update`). - All `[[wikilinks]]` resolve to existing pages in the doc-set. Zero dead links. - Every code snippet's `path:line` re-checked against the working tree before finishing. ## Core Principle **Explain THEIR code, not the technology.** Every primitive definition must be followed within ~10 lines b