project-standards

Consolidate coding rules by inferring patterns from existing repository configurations or manually adding explicit standards into a centralized markdown document. This approach captures organizational practices and stores them centrally for team governance and project-management reference.

Auto-detecting codebase standards is achieved by scanning the repository to synthesize a baseline of engineering governance rules from existing configurations and code patterns. This inference process identifies documented practices and formats them into a centralized standards file.

Manually adding a coding rule involves capturing the explicit standard and appending it directly to your centralized project-management documentation. This ensures the new governance rule is stored alongside inferred practices within your single source of truth.

Project standards are stored in the `.chalk/docs/engineering/project-standards.md` file within the codebase. This markdown file outlines both inferred configurations and explicitly added coding rules with categorizations for governance documentation.

Yes, documenting engineering standards works for any repository by inferring existing configurations or accepting explicit rules to add. It requires no external dependencies and generates a centralized governance document outlining your coding rules.