coding-standard
Coding Standard
Produce two documents for the current project, each a folder with one file per section. references/layout.md gives the file names.
docs/coding-standard/: the rules, each with a short rationale and a correct/incorrect example.docs/code-review-checklist/: a binary checklist a reviewer walks per PR, each item traceable to a rule.
The standards must describe this codebase, not a generic ideal. Infer what the project already does and write that down; only propose new rules where there's a real gap, and confirm those with the user before committing them. A standard nobody follows is worse than none.
Grill before writing. This document is central: lead-review enforces it verbatim, so a wrong or unowned rule propagates into every future review. Read the project first (section 1), then grill the user on every open decision (section 2) one question at a time, each with your recommended default and the trade-off, walking each branch until resolved. Do not write either document until the rules are settled.
1. Read the project first
Before writing anything: