domain-modeling

Primitive obsession is using built-in types like strings for domain concepts, which reduces code quality by allowing invalid states. It causes type safety issues where identifiers are interchangeable, leading to runtime bugs that type-safe domain modeling prevents.

To make invalid states unrepresentable in software design, use semantic types instead of primitives. This enforces domain modeling principles during TDD cycles and code reviews, ensuring type safety and preventing invalid data from being constructed.

Prevent accidental misuse of identifiers by creating distinct semantic types for AccountId and UserId. This domain modeling technique avoids primitive obsession, ensuring type safety and stopping invalid operations at compile time.

Apply domain modeling principles during code reviews and TDD cycles to ensure domain integrity. This type-safe design approach catches bugs at compile time rather than runtime, making it ideal when designing new features or refactoring existing software.

The best way to use semantic types is replacing primitives with domain-specific types that match business terminology. This type-safe domain modeling approach prevents primitive obsession and ensures code clearly communicates business rules.

No specific framework is required to build type-safe domain models. The Skill provides domain modeling principles applicable to any software design environment, focusing on semantic types and preventing primitive obsession without external dependencies.