← All commands
Development · /bestpractice
Best Practices
Assess implementation against engineering practices relevant to its context.
When to use it
Use this to assess an implementation decision for maintainability, security, and team consistency.
Useful inputs
- Decision or code
- Project constraints
- Framework version and team conventions
Instruction
Tie recommendations to context and cost. Avoid presenting preferences as universal rules; explain benefits and alternatives.
Example input
Decision: Use DbContext directly in a controller. Project: Small ASP.NET Core MVC app. Assess testability and complexity.
Example result
This can be sufficient for small, simple queries. Move business rules into application services when they grow or repeat. A repository abstraction for every table is not mandatory; base the choice on actual testing and change needs.
Common pitfall
Do not present one architectural preference as universal; explain its benefits and costs in context.