convention-learner

To detect coding conventions, analyze existing codebase patterns including public API structures, naming schemes, and folder organization. This process extracts evidence of project-specific styles to guide consistent code generation and review.

You can enforce .editorconfig rules by detecting and respecting explicit project configurations alongside Directory.Build.props. This ensures that your project's explicit style rules override generic defaults during code review and generation.

The best way to ensure code generation matches project conventions is to systematically analyze the project structure and existing public API patterns first. This evidence-based approach prevents inconsistent style changes by matching the codebase's naming and structure.

You document detected architecture patterns by summarizing the learned naming, structure, and style conventions. This summary provides actionable guidance that can be recorded in team continuity files like CLAUDE.md for new developer onboarding.

Static analysis works with record vs class usage patterns by examining representative public API code. It learns these specific structural choices and flags deviations to maintain consistency across the existing codebase.