claude-swift-engineering

claude-swift-engineering

Claude Code plugin marketplace for modern Swift/SwiftUI development

A specialized AI toolkit for building professional iOS/macOS features with modern Swift 6.2, TCA (The Composable Architecture), and SwiftUI. This plugin provides ultra-specialized agents that orchestrate planning, implementation, testing, and deployment.

Swift Engineering Plugin

The swift-engineering plugin is a production-ready toolkit for professional Swift development:

• 12 Ultra-Specialized Agents — Planning (Opus), implementation (Inherit), utilities (Haiku) with clear handoffs
• TCA Support — Full workflow from architecture design to testing for The Composable Architecture
• Modern Swift 6.2 — iOS 26+ with strict concurrency, async/await, actors, Sendable
• Code Quality — Integrated code review, accessibility compliance, and performance checks
• Knowledge Skills — 18 specialized knowledge bases covering architecture patterns, frameworks, design, and development tools

Quick Start

Installation

Add the plugin to Claude Code:

# Add marketplace source
/plugin marketplace add https://github.com/johnrogers/claude-swift-engineering

# Install swift-engineering plugin
/plugin install swift-engineering

Hooks (Optional)

Enable skill/agent evaluation hooks for better workflow discipline:

# 1. Symlink hooks-scripts to ~/.claude
ln -s /path/to/claude-swift-engineering/plugins/swift-engineering/hooks-scripts ~/.claude/hooks-scripts

# 2. Add to ~/.claude/settings.json
{
  "hooks": {
    "UserPromptSubmit": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "cat ~/.claude/hooks-scripts/UserPromptSubmit/skill-forced-eval-hook.sh"
          },
          {
            "type": "command",
            "command": "cat ~/.claude/hooks-scripts/UserPromptSubmit/agent-forced-eval-hook.sh"
          }
        ]
      }
    ]
  }
}

See plugins/swift-engineering/hooks-scripts/README.md for complete hook documentation.

See plugins/swift-engineering/README.md for complete documentation on using agents and available workflows.

What's Included

12 Specialized Agents

Type	Agents	Responsibility
Planning	@swift-ui-design, @swift-architect, @tca-architect	Architecture decisions (Opus, read-only)
Implementation	@tca-engineer, @swift-engineer, @swiftui-specialist, @swift-test-creator, @documentation-generator, @swift-code-reviewer, @swift-modernizer	Code creation and review (Inherit)
Utilities	@swift-documenter, @search	API documentation and code search (Haiku)

18 Knowledge Skills

Architecture patterns (TCA, SwiftUI, modern Swift, advanced gestures), frameworks (SQLite, GRDB, StoreKit, networking), platform design (iOS 26, HIG, localization, haptics), and development tools (testing, style, diagnostics). Each skill provides deep guidance on modern patterns and best practices.

For Contributors

Repository Structure

claude-swift-engineering/
├── .claude-plugin/
│   └── marketplace.json                    # Marketplace configuration
├── .github/workflows/                      # CI/CD pipelines
├── plugins/
│   └── swift-engineering/                  # Main plugin
│       ├── agents/                         # 12 specialized agents
│       ├── skills/                         # 18 comprehensive skills
│       ├── hooks-scripts/                  # Hooks system
│       ├── scripts/                        # Helper utilities
│       ├── rules/                          # Development rules
│       └── README.md                       # Plugin documentation
└── worktrees/                              # Git worktrees for features

Development Workflow

Bumping Version

When making changes, increment the plugin version:

bash plugins/swift-engineering/scripts/bump-plugin-version.sh <new-version>

This updates version numbers across plugin.json, marketplace.json, and other metadata files.

Adding Agents or Skills

1. Create new agent or skill file following existing patterns (see examples in agents/ or skills/)
2. Update plugin.json if defining new tool capabilities
3. Run smoke tests to validate configuration
4. Update both README files (root and plugin)
5. Test integration with the workflow

Code Organization