composable-architecture

Name: composable-architecture
Author: johnrogers

222stars19forks

How to install composable-architecture?

johnrogers/claude-swift-engineering/composable-architecture

$npx -y skills add johnrogers/claude-swift-engineering --skill composable-architecture

Installs into the current project.

Summary

Use when building features with TCA (The Composable Architecture), structuring reducers, managing state, handling effects, navigation, or testing TCA features. Covers @Reducer, Store, Effect, TestStore, reducer composition, and TCA patterns.

Files · 1

View on GitHub

SKILL.md

1	# The Composable Architecture (TCA)
2
3	TCA provides architecture for building complex, testable features through composable reducers, centralized state management, and side effect handling. The core principle: predictable state evolution with clear dependencies and testable effects.
4
5	## Reference Loading Guide
6
7	ALWAYS load reference files if there is even a small chance the content may be required. It's better to have the context than to miss a pattern or make a mistake.
8
9	\| Reference \| Load When \|
10	\|-----------\|-----------\|
11	\| [Reducer Structure](references/reducer-structure.md) \| Creating new reducers, setting up `@Reducer`, `State`, `Action`, or `@ViewAction` \|
12	\| [Views - Binding](references/views-binding.md) \| Using `@Bindable`, two-way bindings, `store.send()`, or `.onAppear`/`.task` \|
13	\| [Views - Composition](references/views-composition.md) \| Using `ForEach` with stores, scoping to child features, or optional children \|
14	\| [Navigation - Basics](references/navigation-basics.md) \| Setting up `NavigationStack`, path reducers, pushing/popping, or programmatic dismiss \|
15	\| [Navigation - Advanced](references/navigation-advanced.md) \| Deep linking, recursive navigation, or combining NavigationStack with sheets \|
16	\| [Shared State](references/shared-state.md) \| Using `@Shared`, `.appStorage`, `.withLock`, or sharing state between features \|
17	\| [Dependencies](references/dependencies.md) \| Creating `@DependencyClient`, using `@Dependency`, or setting up test dependencies \|
18	\| [Effects](references/effects.md) \| Using `.run`, `.send`, `.merge`, timers, effect cancellation, or async work \|
19	\| [Presentation](references/presentation.md) \| Using `@Presents`, `AlertState`, sheets, popovers, or the Destination pattern \|
20	\| [Testing - Fundamentals](references/testing-fundamentals.md) \| Setting up test suites, `makeStore` helpers, or understanding Equatable requirements \|
21	\| [Testing - Patterns](references/testing-patterns.md) \| Testing actions, state changes, dependencies, errors, or presentations \|
22	\| [Testing - Advanced](references/testing-advanced.md) \| Using `TestClock`, keypath matching, `exhaustivity = .off`, or time-based tests \|
23	\| [Testing - Utilities](references/testing-utilities.md) \| Test data factories, `LockIsolated`, `ConfirmationDialogState` testing, or `@Shared` testing \|
24	\| [Performance](references/performance.md) \| Optimizing state updates, high-frequency actions, memory, or store scoping \|
25
26	## Common Mistakes
27
28	1. Over-modularizing features — Breaking features into too many small reducers makes state management harder and adds composition overhead. Keep related state and actions together unless there's genuine reuse.
29
30	2. Mismanaging effect lifetimes — Forgetting to cancel effects when state changes leads to stale data, duplicate requests, or race conditions. Use `.concatenate` for sequential effects and `.cancel` when appropriate.
31
32	3. Navigation state in wrong places — Putting navigation state in child reducers instead of parent causes unnecessary view reloads and state inconsistencies. Navigation state belongs in the feature that owns the navigation structure.
33
34	4. Testing without TestStore exhaustivity — Skipping TestStore assertions for "simple" effects or "obvious" state changes means you miss bugs. Use exhaustivity checking religiously; it catches regressions early.
35
36	5. Mixing async/await with Effects incorrectly — Converting async/await to `.run` effects without proper cancellation or error handling loses isolation guarantees. Wrap async operations carefully in `.run` with `yield` statements.

People who liked this also viewed

6 picks

Type

composable-architecture

222stars19forks

View on GitHub

How to install composable-architecture?

johnrogers/claude-swift-engineering/composable-architecture

$npx -y skills add johnrogers/claude-swift-engineering --skill composable-architecture

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# The Composable Architecture (TCA)
2
3	TCA provides architecture for building complex, testable features through composable reducers, centralized state management, and side effect handling. The core principle: predictable state evolution with clear dependencies and testable effects.
4
5	## Reference Loading Guide
6
7	ALWAYS load reference files if there is even a small chance the content may be required. It's better to have the context than to miss a pattern or make a mistake.
8
9	\| Reference \| Load When \|
10	\|-----------\|-----------\|
11	\| [Reducer Structure](references/reducer-structure.md) \| Creating new reducers, setting up `@Reducer`, `State`, `Action`, or `@ViewAction` \|
12	\| [Views - Binding](references/views-binding.md) \| Using `@Bindable`, two-way bindings, `store.send()`, or `.onAppear`/`.task` \|
13	\| [Views - Composition](references/views-composition.md) \| Using `ForEach` with stores, scoping to child features, or optional children \|
14	\| [Navigation - Basics](references/navigation-basics.md) \| Setting up `NavigationStack`, path reducers, pushing/popping, or programmatic dismiss \|
15	\| [Navigation - Advanced](references/navigation-advanced.md) \| Deep linking, recursive navigation, or combining NavigationStack with sheets \|
16	\| [Shared State](references/shared-state.md) \| Using `@Shared`, `.appStorage`, `.withLock`, or sharing state between features \|
17	\| [Dependencies](references/dependencies.md) \| Creating `@DependencyClient`, using `@Dependency`, or setting up test dependencies \|
18	\| [Effects](references/effects.md) \| Using `.run`, `.send`, `.merge`, timers, effect cancellation, or async work \|
19	\| [Presentation](references/presentation.md) \| Using `@Presents`, `AlertState`, sheets, popovers, or the Destination pattern \|
20	\| [Testing - Fundamentals](references/testing-fundamentals.md) \| Setting up test suites, `makeStore` helpers, or understanding Equatable requirements \|
21	\| [Testing - Patterns](references/testing-patterns.md) \| Testing actions, state changes, dependencies, errors, or presentations \|
22	\| [Testing - Advanced](references/testing-advanced.md) \| Using `TestClock`, keypath matching, `exhaustivity = .off`, or time-based tests \|
23	\| [Testing - Utilities](references/testing-utilities.md) \| Test data factories, `LockIsolated`, `ConfirmationDialogState` testing, or `@Shared` testing \|
24	\| [Performance](references/performance.md) \| Optimizing state updates, high-frequency actions, memory, or store scoping \|
25
26	## Common Mistakes
27
28	1. Over-modularizing features — Breaking features into too many small reducers makes state management harder and adds composition overhead. Keep related state and actions together unless there's genuine reuse.
29
30	2. Mismanaging effect lifetimes — Forgetting to cancel effects when state changes leads to stale data, duplicate requests, or race conditions. Use `.concatenate` for sequential effects and `.cancel` when appropriate.
31
32	3. Navigation state in wrong places — Putting navigation state in child reducers instead of parent causes unnecessary view reloads and state inconsistencies. Navigation state belongs in the feature that owns the navigation structure.
33
34	4. Testing without TestStore exhaustivity — Skipping TestStore assertions for "simple" effects or "obvious" state changes means you miss bugs. Use exhaustivity checking religiously; it catches regressions early.
35
36	5. Mixing async/await with Effects incorrectly — Converting async/await to `.run` effects without proper cancellation or error handling loses isolation guarantees. Wrap async operations carefully in `.run` with `yield` statements.

People who liked this also viewed

6 picks

Type