implement-feature

Feature implementation with test-driven development follows an architecture-first design phase, then Chicago School TDD to guide domain model tests, infrastructure tests, and integration. Engineers outline architecture and domain models before writing any production code.

Chicago School TDD for domain modeling starts with writing failing domain model tests, then building rich domain models to pass them, followed by infrastructure tests and integration. It enforces protocol-based dependency injection using @Mockable for testability and isolation.

Yes, SwiftUI can consume domain models directly without a ViewModel layer. This approach reduces boilerplate by having the UI layer use domain-driven models explicitly, aligning feature work with the user's mental model while maintaining test-driven validation.

Protocol-based dependency injection with @Mockable works with Swift 6.2 patterns. It enables testability and isolation across Domain, Infrastructure, and App layers by using mockable protocols to inject dependencies during Chicago School TDD workflows.

Architecture-first feature work spans Domain, Infrastructure, and App layers with explicit user approvals at each phase. Engineers design the architecture, outline domain models, plan infrastructure integration, and compose SwiftUI views before implementation begins.

Test-driven feature implementation requires explicit user approvals to validate architecture design, domain modeling, and infrastructure integration before proceeding. This ensures changes align with the user's mental model and that domain-driven design principles are maintained across each phase.