convention-learner

To detect project conventions before generating .NET code, collect six signals: naming suffixes, src folder architecture, dependency injection patterns, test assertion styles, DTO shapes, and error-handling approaches. This prevents inconsistent naming and architectural mismatch when creating new files.

The best way to ensure generated code matches existing repository style is to perform mandatory convention discovery before writing new code. This structured detection explicitly identifies and applies existing naming, folder structure, DI wiring, and test layout conventions to new code generation.

Newly generated code drifts from unfamiliar codebase conventions because naming, structure, and error-handling patterns are not explicitly specified by the user. Forcing convention discovery before writing code prevents this drift by reproducing existing handler suffixes and architectural layouts.

To override detected conventions when generating code, provide explicit user instructions. The convention-driven code generation guidance applies detected patterns by default, but includes a clear rule that user-specified overrides take precedence over discovered repository style.

Yes, you can use convention detection for adding features to unfamiliar code areas. It applies to first-time file creation and extending features by forcing discovery of DI registration patterns, test frameworks, and error-handling approaches before new code is written.

No, you do not need to specify naming and structure when creating new .NET files if convention detection is used. It automatically gathers naming suffixes and src folder architecture styles, ensuring newly generated code matches repository style without manual specification.