style

Apply the style skill before drafting: it leads with the current behavior and conceptual fix in plain English, keeps the body to one page, and cuts anything readable straight from the diff. The pr-descriptions reference defines the full arc from problem through verification.

The tech-plans reference wins length through density, not omission: define terms inline at first use, open each section with one framing line, and include only current-behavior facts the design leans on. Decision history moves to PR history, replaced by one pointer line.

It enforces lean prose with short paragraphs, plain declarative wording, cold-reader definitions for every identifier, behavior-first framing of changes, and confidence stated with its assumption. Bold marks one load-bearing claim per paragraph; em-dashes are a last resort.

Yes, the voice stays constant but density changes per register. Slack messages are casual and conversational with one link and few identifiers, while PR descriptions are formal, behavior-first, and budgeted to one page. Each register has its own reference file.

Wording feedback goes into the artifact immediately, never noted for later. A dictated replacement lands verbatim, then its shape generalizes to the rest of the artifact. Design decisions are the opposite: discuss and confirm first, then apply.