What problem does it solve? It keeps every chapter of the fluidpy project consistent by codifying file naming, docstring contracts, units and notation rules, validation vocabulary, curation tiers, and the definition of done for chapter work. ## Core Features & Use Cases - Project conventions: Defines chapter IDs, module/test/notebook/explainer file naming, and the role of core primitives and knowledge files. - Docstring and validation contract: Requires every function to cite book equations, list units, state assumptions, and declare a validation level (analytic, symbolic, converged, conserved, benchmark). - Curation tiers and done criteria: Specifies CORE/NOTE/RECAP/SKILL tiers for exhaustive book coverage and a six-step checklist for chapter completion. - Use Case: When implementing Chapter 7 gravity waves, load this Skill to name files correctly, write compliant docstrings, and know exactly what must pass before the chapter is done. ## Quick Start Load the fluids-book conventions before implementing or reviewing any chapter module, test, notebook, or explainer in this repository.
