enforcing-dto-record

To enforce C# record usage for DTOs, apply this Skill to your classes to ensure they are declared as 'record', guaranteeing immutability and value-based equality. This standardizes Data Transfer Object implementations across .NET projects.

C# records provide built-in immutability and value-based equality, preventing data modification after creation. Using records for DTOs reduces bugs, improves code predictability, and simplifies maintenance compared to mutable classes.

Yes, you can use this in existing .NET projects to enforce coding standards. Apply the Skill to your next DTO class to verify it is implemented as a 'record', ensuring code quality and immutability without requiring additional dependencies.

The best way to standardize immutable DTO implementations is to enforce 'record' declarations over 'class'. This Skill forces all Data Transfer Objects to use records, providing immutability and value-based equality to improve overall code quality.

You should not use C# records for DTOs when your data objects require mutability or complex behavioral methods. Records are designed for immutable data models; enforcing them on mutable state objects may conflict with your application's functional requirements.