Skip to content
TrustedSkillsbeta
Back to all skills

Composable Architecture

Checked
johnrogers·vlatest·backend·MIT

This skill helps organize complex applications into reusable components, boosting maintainability and accelerating development workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add johnrogers/claude-swift-engineering --skill composable-architecture -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

johnrogers

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned johnrogers/claude-swift-engineering at 1dc2cf4d02.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1dc2cf4d02
Manifest
plugins/swift-engineering/skills/composable-architecture/SKILL.md
Scanned
15 files, 3,282 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, Composable Architecture (TCA), provides a structured architecture for building complex and testable application features. It emphasizes predictable state evolution through composable reducers, centralized state management, and clear side effect handling. TCA promotes reusability by organizing applications into smaller, manageable components with well-defined dependencies, ultimately accelerating development workflows and improving maintainability.

When to use it

  • Developing complex user interfaces requiring robust state management.
  • Building features that need to be highly testable and predictable.
  • Creating reusable UI components across different parts of an application.
  • Implementing navigation flows with deep linking or recursive structures.
  • Sharing state between distinct, composable features within the app.

Key capabilities

  • Composable Reducers: Building features from smaller, reusable reducers.
  • Centralized State Management: Managing application state in a predictable and organized manner.
  • Side Effect Handling: Controlling asynchronous operations and external interactions.
  • Navigation Stack: Implementing navigation flows with pushing, popping, and programmatic dismissal.
  • Shared State: Sharing data between different features using mechanisms like @Shared and .appStorage.
  • Dependency Management: Defining and managing dependencies between components using @DependencyClient and @Dependency.
  • Testing Support: Providing tools and patterns for comprehensive unit testing, including TestStore, TestClock, and exhaustivity checking.

Example prompts

  • "Show me how to create a reducer with @Reducer, State, Action, and @ViewAction."
  • "How do I implement navigation using NavigationStack?"
  • "Explain how to share state between features using @Shared."
  • “Demonstrate setting up test dependencies for a feature.”

Tips & gotchas

  • Reference Files: Always load reference files when working with TCA, even if you think they might not be needed. This ensures access to necessary patterns and avoids potential errors.
  • Avoid Over-Modularization: Breaking features into too many small reducers can complicate state management; keep related logic together unless there’s a clear need for reuse.
  • Effect Lifecycles: Properly manage the lifecycles of effects, ensuring cancellation to prevent stale data or duplicate requests.