go-create-validator

To generate a Go validator for modular architecture, automate the creation of a two-file pattern: a port interface in the ports directory and a concrete validator implementation in the validator directory. This enforces interface-first design and stateless validation.

The two-file pattern for Go domain validation separates interfaces from implementations. It places the port interface at internal/modules/<module>/ports/ and the concrete validator at internal/modules/<module>/validator/ to ensure clean dependency boundaries.

Yes, you can use Fx dependency injection with custom Go validators. The generated validator includes Fx wiring, ensuring the module is ready for dependency injection and modular wiring within the Fx framework.

To handle typed errors in Go email and password validation, the generated validator integrates with the module's errs package. This ensures domain-specific error handling by returning typed errors directly from the validation logic.

Yes, the generated Go validator supports context-based validation for I/O operations. It includes optional context-based validation features, allowing validators to handle I/O dependencies safely when required by the domain logic.

The best way to scaffold a validation layer for a new Go module is to generate the port interface and concrete implementation simultaneously. This enforces an interface assertion and ensures the constructor returns the correct pointer type.