composable-architecture — Claude Code skill: features and setup
This skill guides feature work with The Composable Architecture (TCA), from reducer structure and effects to navigation and tests. Use it while building or checking TCA features.
MIT ★ 233 updated 2026-01-18
/plugin marketplace add johnrogers/claude-swift-engineering
/plugin install swift-engineering@claude-swift-engineeringWhat composable-architecture does
The skill covers TCA building blocks such as @Reducer, Store, Effect, reducer composition, and dependencies. Its reference files address state, views, navigation, effects, and testing. For a task, it points to the relevant material to load.
Ask for help with TestStore, @Shared, effect cancellation, or navigation state. Tests should assert expected effects and state changes; skipping those checks can leave bugs unnoticed. Effects that keep running after state changes can return stale data or create duplicate requests and race conditions.
What it helps with
- set up a reducer with state and actions
- compose related child features
- handle asynchronous work and cancel an effect
- place navigation state in the feature that owns the navigation structure
- test state changes and effects with
TestStore
Example prompts for the agent
- Create a TCA reducer for this feature and identify the reference files it needs.
- Check this asynchronous effect for cancellation issues and suggest a test.
- Write a
TestStoretest for this feature’s actions and state changes.
How to install composable-architecture
1Plugin marketplace
/plugin marketplace add johnrogers/claude-swift-engineering/plugin install swift-engineering@claude-swift-engineeringThis installs the whole swift-engineering plugin with all its skills
2Skills CLI (Vercel)
npx skills add johnrogers/claude-swift-engineering --skill composable-architecture -a claude-code3Manually: put the files in place
~/.claude/skills/composable-architecture/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/composable-architecture/
1Skills CLI (Vercel)
npx skills add johnrogers/claude-swift-engineering --skill composable-architecture -a codex2Manually: put the files in place
.agents/skills/composable-architecture/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add johnrogers/claude-swift-engineering --skill composable-architecture -a cursor2Manually: put the files in place
.cursor/skills/composable-architecture/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install johnrogers/claude-swift-engineering plugins/swift-engineering/skills/composable-architecture2Manually: put the files in place
.github/skills/composable-architecture/SKILL.md1Skills CLI (Vercel)
npx skills add johnrogers/claude-swift-engineering --skill composable-architecture -a gemini-cli2Platform CLI
gemini skills install https://github.com/johnrogers/claude-swift-engineering --path plugins/swift-engineering/skills/composable-architectureManually: put the files in place
.devin/skills/composable-architecture/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about composable-architecture
How do I install composable-architecture in Claude Code?
Add the marketplace with /plugin marketplace add johnrogers/claude-swift-engineering, then install the plugin with /plugin install swift-engineering@claude-swift-engineering.
What does composable-architecture do?
It helps build and test TCA features, covering reducers, state, effects, dependencies, and navigation.
Why should effects be cancelled when state changes?
A running effect can return stale data or cause duplicate requests and race conditions. The skill covers .cancel and .concatenate for managing effect lifetimes.
Source text
SKILL.md · MIT
--- name: composable-architecture description: 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. --- # The Composable Architecture (TCA) 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. ## Reference Loading Guide **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. | Reference | Load When | |-----------|-----------| | **[Reducer Structure](references/reducer-structure.md)** | Creating new reducers, setting up `@Reducer`, `State`, `Action`, or `@ViewAction` | | **[Views - Binding](references/views-binding.md)** | Using `@Bindable`, two-way bindings, `store.send()`, or `.onAppear`/`.task` | | **[Views - Composition](references/views-composition.md)** | Using `ForEach` with stores, scoping to child features, or optional children | | **[Navigation - Basics](references/navigation-basics.md)** | Setting up `NavigationStack`, path reducers, pushing/popping, or programmatic dismiss | | **[Navigation - Advanced](references/navigation-advanced.md)** | Deep linking, recursive navigation, or combining NavigationStack with sheets | | **[Shared State](references/shared-state.md)** | Using `@Shared`, `.appStorage`, `.withLock`, or sharing state between features | | **[Dependencies](references/dependencies.md)** | Creating `@DependencyClient`, using `@Dependency`, or setting up test dependencies | | **[Effects](references/effects.md)** | Using `.run`, `.send`, `.merge`, timers, effect cancellation, or async work | | **[Presentation](references/presentation.md)** | Using `@Presents`, `AlertState`, sheets, popovers, or the Destination pattern | | **[Testing - Fundamentals](references/testing-fundamentals.md)** | Setting up test suites, `makeStore` helpers, or understanding Equatable requirements | | **[Testing - Patterns](references/testing-patterns.md)** | Testing actions, state changes, dependencies, errors, or presentations | | **[Testing - Advanced](references/testing-advanced.md)** | Using `TestClock`, keypath matching, `exhaustivity = .off`, or time-based tests | | **[Testing - Utilities](references/testing-utilities.md)** | Test data factories, `LockIsolated`, `ConfirmationDialogState` testing, or `@Shared` testing | | **[Performance](references/performance.md)** | Optimizing state updates, high-frequency actions, memory, or store scoping | ## Common Mistakes 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. 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. 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. 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. 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.
© John Rogers (@johnrogers) · MIT · johnrogers/claude-swift-engineering