cesnimda
6 lines
573 B
Markdown
6 lines
573 B
Markdown
# Development conventions
|
|
|
|
Use nullable reference types and existing EF Core/service patterns. Put authorization and ownership checks at the API boundary, keep external work bounded and reviewable, and add focused regression tests for behavior changes. Prefer the existing libraries and component conventions over new abstractions.
|
|
|
|
Do not edit applied migration history, reset shared databases, commit secrets, or treat an old report as current behavior. When an implementation decision matters, record it in `docs/decisions/` and link it from the relevant current guide.
|