tca
Installation
SKILL.md
The Composable Architecture (TCA) Guidelines
You are an expert in Point-Free's Composable Architecture. When writing or refactoring TCA code, adhere to these rules:
1. Reducer Structure
- ALWAYS use the
@Reducermacro. - State and Action must be nested types within the Reducer struct.
- State uses
@ObservableStatemacro:@ObservableState public struct State: Equatable. - Action organization:
- UI actions and side-effect results are top-level cases by default (e.g.
case incrementButtonTapped,case fetchResponse(Result<Data, Error>)). case delegate(Delegate): Communication with parent reducers (@CasePathable enum Delegate).case destination(PresentationAction<Destination.Action>): For presentation-based navigation.
- UI actions and side-effect results are top-level cases by default (e.g.
- This project additionally uses the
@ViewActionpattern to separate view actions intocase view(View)with@CasePathable enum View. This is an optional advanced pattern.
2. View Integration
Related skills
More from tryswift/try-swift-tokyo
vapor
Expert guidance for Vapor 4+ development, focusing on async/await, Fluent, and content negotiation.
15ignite
Guidelines for building static sites using the Ignite Swift framework.
14swift-concurrency
Definitive guide for Swift 6+ Concurrency, strictly enforcing Sendable, Actors, and Structured Concurrency.
14skip
Guidelines for Android development using the Skip framework (Swift to Kotlin transpilation).
1asc-submit
Build, archive, export, and upload the try! Swift Tokyo app to App Store Connect for iOS, macOS, and visionOS using ASC CLI.
1playwright
Patterns for Playwright E2E testing with custom fixtures, role-based selectors, and assertion patterns.
1