implement-feature

To implement a feature using architecture-first design, draft an ASCII diagram of components for user approval, then define rich domain models in the Domain layer, infrastructure in the Infrastructure layer, and SwiftUI views in the App layer.

Chicago School TDD for domain modeling uses state-based testing to shape robust domain models, ensuring reliable integrations by writing tests that verify state transitions rather than interaction behavior.

Yes, you can build SwiftUI views without a ViewModel layer by directly consuming rich domain models in your views, utilizing protocol-based dependency injection and @Mockable protocols for testability.

The best way to structure a feature across layers is to define domain models in Sources/Domain, infrastructure in Sources/Infrastructure, and app views in Sources/App, ensuring clear boundaries and phased implementation from prototyping to verification.

Yes, architecture-first design requires a clear architecture design to be reviewed and approved during Phase 0 before any coding begins, ensuring component interactions are documented and validated.

You use @Mockable protocols for Swift feature implementation to enable protocol-based dependency injection, allowing direct consumption of domain models in SwiftUI views while maintaining robust mockable testing capabilities.