What problem does it solve? Writing educational content for fluid mechanics notebooks and HTML explainers risks inconsistency: unexplained symbols, skipped derivation steps, uncommented code, and figures left uninterpreted. This Skill enforces a single, detailed teaching style so every notebook cell, derivation, and explainer walkthrough follows the same reader-first rules. ## Core Features & Use Cases - Structured logic chain: Enforces the problem → idea → maths → tiny example → code → output-interpretation sequence for every core concept, with plain words before symbols. - Full derivations: Requires one algebraic move per step, each with what-we-did, why-allowed, and in-words annotations, plus checks, unit verification, and sympy validation for hard derivations. - Self-contained explanations: Mandates primers and recaps so no term, symbol, math tool, or Python idiom is used before it is explained. - Use Case: When drafting a new chapter notebook on gravity waves, load this Skill so every section uses the standard headings ("What does the code above do?", "What you see / How to read it"), novice-grade code comments with units and equation citations, and walkthrough steps under 45 words for the interactive explainer. ## Quick Start Use the teaching-style skill to review this notebook cell and rewrite it following the fluidpy teaching conventions.
