vsa-implementation-guard

This Skill automatically forbids SaveChangesAsync in handlers during code generation, enforcing delegation to TransactionBehavior instead. It validates handler implementations to ensure database commits occur only through the configured transaction layer, eliminating accidental duplicate or misplaced saves.

The Skill detects business logic written directly in BoundaryService and redirects it to Entity methods like CanXxx(). During code modification, it validates that services remain thin, delegating authorization and state validation to domain entities, keeping concerns properly separated.

This Skill enforces Result<T> usage for error handling in handlers and validators, preventing exception propagation. It applies rules during generation to ensure handlers return structured results, catching validation and business logic failures without throwing unchecked exceptions.

The Skill validates Value Object equality implementations during code generation, enforcing proper comparison logic. It prevents common mistakes like reference equality, ensuring Value Objects use value-based comparison as domain-driven design requires.

No. This Skill restricts FluentValidation validators to format-only checks during code analysis, preventing business rule enforcement in validators. It directs complex validations to entities or handlers, maintaining clean separation between format validation and domain logic.

BoundaryService acts as a service boundary in VSA. The Skill enforces this by preventing business logic there, ensuring entities own authorization checks and state transitions. This keeps domain logic centralized and testable, preventing scattered business rules across the application layer.