app-implement-feature

To implement a feature with TDD and Clean Architecture, this skill enforces an architecture-first design phase for domain and infrastructure layers, followed by Chicago-style TDD to build rich domain models and protocol-based dependencies before writing SwiftUI views.

Yes, you can consume rich domain models directly in SwiftUI views without a ViewModel. This approach leverages Swift 6.2 patterns to eliminate the intermediate ViewModel layer, allowing views to interact directly with domain behavior.

The best way to design architecture before testing is to create component diagrams and document interactions across domain, infrastructure, and app layers. This skill mandates user approval of this design phase before proceeding to TDD implementation.

Yes, Domain-Driven Design works seamlessly with protocol-based dependency injection in Swift. This combination allows you to define clear boundaries for infrastructure layers while maintaining rich domain models that encapsulate behavior aligned with the user's mental model.

To write domain model tests using Chicago-style TDD, you focus on testing the behavior of the entire domain object from the outside. This skill guides you through writing these tests to ensure your rich domain models function correctly before integrating infrastructure components.

You need to create a component diagram for a Swift feature during the mandatory architecture design phase before any coding begins. This ensures that interactions across domain, infrastructure, and app layers are documented and approved prior to TDD implementation.