axiom-swiftui-architecture

Codify SwiftUI architecture guidance for separating concerns and improving testability.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/pradeepmouli/swift-template --skill axiom-swiftui-architecture-pradeepmouli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-swiftui-architecture
Source: https://github.com/pradeepmouli/swift-template/tree/main/.agents/skills/axiom-swiftui-architecture
Command: npx skills add https://github.com/pradeepmouli/swift-template --skill axiom-swiftui-architecture-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams architect SwiftUI apps by choosing appropriate patterns (Apple-native, MVVM, TCA, Coordinator) and by guiding the separation of concerns to improve testability and maintainability.

Core Features & Use Cases

  • Guidance on when to apply Apple-native patterns vs MVVM, TCA, or Coordinator.
  • Practical refactoring workflows for moving logic from SwiftUI views into models, view models, or reducers.
  • Clear navigation architecture guidance, including coordinating with Coordinators and testable navigation flows.

Quick Start

Provide a concise refactoring plan that moves UI logic from views into models and view models for a small feature.

Frequently Asked Questions about axiom-swiftui-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to separate concerns in SwiftUI apps?

Refactoring SwiftUI views involves moving UI logic into models, view models, or reducers to improve testability. A concise refactoring plan extracts state and side effects from views into structured layers for better separation of concerns.

How do I refactor SwiftUI views to move logic into view models?

Refactoring SwiftUI views involves moving UI logic into models, view models, or reducers to improve testability. A concise refactoring plan extracts state and side effects from views into structured layers for better separation of concerns.

When should I use TCA versus MVVM in SwiftUI?

Choose TCA over MVVM in SwiftUI when you need structured concurrency and centralized state reducers for complex testability. MVVM suits simpler feature flows, while TCA provides stricter unidirectional data flow and navigation handling.

Can I use the Coordinator pattern for SwiftUI navigation flows?

Yes, the Coordinator pattern can be used with SwiftUI to manage clear navigation architecture and testable navigation flows. It helps decouple navigation logic from views, ensuring modularization and safer routing in iOS and macOS apps.

Does this SwiftUI architecture guidance apply to macOS apps?

Yes, this SwiftUI architecture guidance is applicable to both iOS and macOS apps. It provides decision criteria for separating concerns and improving testability across Apple platforms using MVVM, TCA, and Coordinators.

Why are my SwiftUI views difficult to test and maintain?

SwiftUI views become difficult to test when business and navigation logic are tightly coupled to the view layer. Applying architectural patterns like MVVM or Coordinators extracts this logic into testable, modular components.