What problem does it solve? Adding a technical or research note beside an existing study requires following strict repository conventions: correct file placement, naming prefixes, author/date metadata, SVG and Mermaid validation, and regenerating the companion inventory. This Skill walks through that entire workflow so the note is discoverable and its HTML/PDF outputs match what CI produces. ## Core Features & Use Cases - Companion note authoring: Places Technical-Note-* or Research-Note-* Markdown files as direct children of an existing study directory with correct author and IST date metadata. - Build and verification: Runs the same _regenerate_pdf.py pipeline as CI, checking SVG validity, Mermaid rendering, fenced-code completeness, KaTeX fonts, and PDF outline. - Inventory refresh: Updates the My Submissions registry, generated-PDF keys, and search/offline data so the new note is discoverable. - Use Case: A contributor wants to publish a technical note extending a Draft study. The Skill guides them to author the note, stage it in Git, regenerate its HTML/PDF, and open a study-update PR. ## Quick Start Add a technical note named Technical-Note-Formalization under the Studies/MyStudy directory and generate its HTML and PDF outputs.
