package-layer

Validating shared Go package interface design involves auditing the `pkg/` directory to verify services are defined as interfaces and constructors return interface types. This enforces clean architecture principles for reusable infrastructure components.

Enforcing constructor patterns and error handling in Go packages requires auditing `New()` functions for interface return types and checking for consistent error wrapping. This validates context propagation and coding conventions across shared infrastructure and cloud integrations.

Yes, a clean architecture audit can detect hardcoded secrets in Go code by scanning the `pkg/` directory for direct environment variable access and embedded credentials. This security audit prevents sensitive data exposure in external API clients and utility packages.

The best way to audit context propagation in Go shared packages is to validate consistent context usage across core infrastructure and AI components. This ensures external API clients and queue producers handle requests correctly without breaking clean architecture conventions.

Yes, this package design audit works for cloud integrations and external API clients by validating their implementation within the `pkg/` directory. It checks interface design, error handling, and security standards to ensure adherence to clean architecture principles.

Shared Go packages should use interfaces for all services to ensure maintainability, reusability, and adherence to clean architecture. Defining services as interfaces with proper `New()` constructors allows infrastructure and utility packages to remain decoupled and testable.