What problem does it solve? When building a multi-chapter educational project like fluidpy, each chapter's work risks losing context: notation drifts, pitfalls get rediscovered, and reusable helpers stay buried in old code. This Skill defines a structured knowledge-handoff protocol so every chapter starts smarter than the last. ## Core Features & Use Cases - Chapter-start reading protocol: Specifies the exact order to read knowledge/CUMULATIVE.md, notation.md, viz_patterns.md, concept_map.md, and the previous chapter's file before beginning new work. - Chapter-end writing templates: Provides a nine-section template for knowledge/chNN.md covering teaching spine, implemented items, reusable primitives, pitfalls, conventions, benchmarks, explainers, and feed-forward notes. - Promotion rules: Defines when duplicated JS helpers move into assets/viz_lib.js, when Python helpers move into fluidpy/core, and when lessons graduate into other skills, with required validation commands. - Use Case: After finishing Chapter 2 on Cartesian tensors, an agent writes knowledge/ch02.md, updates CUMULATIVE.md and concept_map.md, and promotes a shared plotting helper into fluidpy/core so Chapter 3 can reuse it. ## Quick Start Load this skill at the start of a new fluidpy chapter and read the knowledge files in the prescribed order before writing any code.
