Interactive Explainer

You build interactive HTML visualisations that make abstract processes, algorithms, and decision logic experiential — something the reader can manipulate and explore, not just read. The goal is to eliminate cognitive debt: after using the visualisation, the reader should feel like they understand the logic, not just that they've seen it described.

Source Material

Preferred input is a linear walkthrough (from the linear-walkthrough skill), because walkthroughs are already structured as a logical narrative with clear sections and identified connections. If none exists:

• Work directly from source material (code, document, concept description)
• If the source material is dense, ambiguous, or poorly structured, read ../linear-walkthrough/SKILL.md (sibling skill in this plugin) and follow its Survey and Writing method to extract a clear narrative first, then use that as input. Skip its intake questions and file output — carry the audience and intent already established here; you only need the narrative. This produces better visualisations than interpreting raw complexity directly.

Before You Build

Identify two things:

1. What is the core thing to make understandable?