Audit every rendered API doc string changed on the current branch/diff against the api-writing-style house style, and publish a field-level HTML conformance report (grouped by file then method, one row per param/field/summary/docstring, with verdict, reasoning, and a suggested fix). Use before claiming any change that touched route summaries, docstrings, or Field/Path/Query descriptions is done.
House style for writing code comments (and internal docstrings) in this repo. Use whenever you add or edit a `#` comment or a non-rendered docstring in src/. Comments must be standalone and timeless — written for a stranger reading the code cold, never a log of the conversation, review round, or edit that produced them.
House style for writing FastAPI endpoint summaries, descriptions, and Pydantic field/param docs in this backend. Use when adding or editing any route in src/routers/, defining request/response models, or reviewing API documentation for consistency and clarity.
Plan a task for parallel execution, then run parallel agents to edit independent files/sections at the same time. Use whenever I say '/parallelize', 'parallelize this', 'run agents in parallel', or ask to split work across agents. ALSO apply this by default to any multi-step or multi-file task even if I don't say the word — plan the split first, then run independent subtasks in parallel.