What problem does it solve? Explaining complex systems, codebases, or incidents usually produces either oversimplified analogies or dense technical prose. This Skill turns a difficult system into a truthful, interactive visual story where every claim is labeled as verified, inferred, or analogy, and compiles it into a single self-contained HTML file that works fully offline. ## Core Features & Use Cases - Four story grammars: concept, repository module, engineering tradeoff, and incident, each with a dedicated summary view and semantic validator. - Evidence at the claim: every scene shows source status, core text, support scope, and a URL or explicit no-locator boundary, with a truth ladder separating analogy, mechanism, and caveats. - Interactive playback and reader workspace: global or scene-local traces animate real nodes and edges, with failure lens, teach-back questions, opt-in local history, favorites, and annotations. - Local export: PDF, scene PNG, all-scene PPTX, Pages-compatible DOCX, and optional verified native .pages conversion via a loopback helper. - Use Case: Ask your agent to explain how one queued job moves through a repository, citing real files, playing the request path, and showing what breaks when a lease expires; the result is a validated offline HTML explainer. ## Quick Start Ask your agent to explain how a request flows through this repository as an interactive visual story with cited evidence and a failure view, then open the generated HTML file in a browser.
