SwiftUI Autotest Skill

Open-source Agent Skills for automated visual testing and accessibility setup of iOS/SwiftUI applications using Claude Code's computer use.

Build, launch in the Simulator, visually test every screen, detect crashes, analyze memory leaks, and add accessibility identifiers — all from the terminal, in a single command.

Quick Start

Install both skills:

npx skills add https://github.com/yusufkaran/swiftui-autotest-skill

Then open your SwiftUI project in Claude Code and say:

Use the /ios-test skill to build the app, launch it in the Simulator, and test all screens.

The agent will find your .xcodeproj, select a Simulator, build and install the app, navigate through every screen with computer use, screenshot each state, and produce a test report. No code is modified unless you explicitly approve changes.

Prerequisites: Enable Computer Use

/ios-test requires Claude Code's computer use feature to see and interact with your screen. This is a one-time setup:

1. Enable the MCP server — In Claude Code, run:

   hljs language-bash

   Copy

   /mcp
   

   Find computer-use in the list and select Enable.

2. Grant macOS permissions — The first time computer use runs, macOS will ask for two permissions:

   • Accessibility — lets Claude click, type, and scroll
   • Screen Recording — lets Claude see your screen

   Grant both in System Settings > Privacy & Security. You may need to restart Claude Code after granting Screen Recording.

3. Requirements:

   • macOS only (not available on Linux/Windows)
   • Claude Code v2.1.85 or later (claude --version to check)
   • Pro or Max plan (not available on free, Team, or Enterprise plans)
   • Interactive session (not available with the -p flag)

Note: /add-accessibility does not require computer use — it only reads and edits source files.

Why Visual Testing Matters

Unit tests verify logic. UI tests verify layouts, navigation, and user flows — but writing them takes time and maintaining them takes more. Computer use lets Claude see and interact with your app the way a real user would, without a single line of test code.

Accessibility identifiers make this faster and more reliable — and they also make your app work with VoiceOver, which is a requirement for many App Store categories.

How It Works

/ios-test                          /add-accessibility
   │                                      │
   ├─ Find .xcodeproj/.xcworkspace        ├─ Scan all SwiftUI files
   ├─ Select Simulator (smart logic)      ├─ Find interactive elements
   ├─ Build with xcodebuild               ├─ Skip elements that already
   ├─ Install & launch app                │  have identifiers
   ├─ Computer use: navigate & test       ├─ Generate {screen}-{type}-{name}
   ├─ Screenshot each screen              ├─ Add .accessibilityIdentifier()
   ├─ Check crash logs                    ├─ Flag Dynamic Type issues
   ├─ (optional) State testing            └─ Summary report
   ├─ (optional) Performance analysis
   └─ Test report

The recommended workflow: run /add-accessibility first to make your views identifiable, then run /ios-test to test them.

What It Checks

Included Skills

Usage

/ios-test

# Test all screens (default)
/ios-test

# Test a specific user flow
/ios-test --flow=onboarding

# Test a specific screen
/ios-test --screen=LoginView

# Choose a Simulator device
/ios-test --device="iPhone 16"

# Specify Xcode scheme
/ios-test --scheme=MyApp

# Test empty, error, and loading states via launch arguments
/ios-test --states

# Measure RAM per screen and check for memory leaks
/ios-test --performance

# Screenshot every step
/ios-test --screenshot-all

# Combine options
/ios-test --flow=checkout --states --performance --screenshot-all

Simulator selection is automatic:

• One booted Simulator → uses it directly, no questions asked
• Multiple booted → lists them and asks which one to use
• None booted → suggests the most recent iPhone device, asks for confirmation

Natural language also works — just say "test the app", "run it in the Simulator", "check for crashes", or "test the onboarding flow".

/add-accessibility

# Scan entire project and add identifiers
/add-accessibility

# Preview changes without modifying files
/add-accessibility --dry-run

# Scan a specific directory
/add-accessibility --path=Sources/Features/Login

# Verbose output for each identifier added
/add-accessibility --verbose

Natural language also works — "add accessibility identifiers", "make views testable", "add VoiceOver support".

Naming Convention

All identifiers follow {screen}-{type}-{name}:

Screen name is derived from the filename (LoginView.swift → login). Elements that already have identifiers are skipped — existing code is never modified.

Installation

Option A: Using skills.sh (recommended)

npx skills add https://github.com/yusufkaran/swiftui-autotest-skill

Then register the slash commands so /ios-test and /add-accessibility work directly:

bash .agents/skills/swiftui-autotest-skill/postinstall.sh

This creates symlinks in .claude/commands/ pointing to the installed skill files. You only need to run this once after installation.

Option B: Claude Code Plugin

1. Add the marketplace:

/plugin marketplace add yusufkaran/swiftui-autotest-skill

2. Install the plugin:

/plugin install swiftui-autotest-skill@swiftui-autotest-skill

To enable for everyone in a repository, add to .claude/settings.json:

{
  "enabledPlugins": {
    "swiftui-autotest-skill@swiftui-autotest-skill": true
  },
  "extraKnownMarketplaces": {
    "swiftui-autotest-skill": {
      "source": {
        "source": "github",
        "repo": "yusufkaran/swiftui-autotest-skill"
      }
    }
  }
}

When team members open the project, Claude Code will prompt them to install the skill.

Option C: Manual Install

git clone https://github.com/yusufkaran/swiftui-autotest-skill.git

Copy files based on your preferred scope:

# User scope — available in all your projects
cp swiftui-autotest-skill/commands/*.md ~/.claude/commands/

# Project scope — shared with your team via git
mkdir -p .claude/commands
cp swiftui-autotest-skill/commands/*.md .claude/commands/

# Local scope — this project only, not committed
mkdir -p .claude/commands
cp swiftui-autotest-skill/commands/*.md .claude/commands/
echo ".claude/commands/ios-test.md" >> .gitignore
echo ".claude/commands/add-accessibility.md" >> .gitignore

Requirements

/ios-test

• macOS
• Xcode + iOS Simulator
• Claude Code v2.1.85+ (computer use support)
• Pro or Max plan (required for computer use)
• computer-use MCP server enabled (run /mcp to enable)

/add-accessibility

• Any SwiftUI project (no additional dependencies)

Skill Structure

swiftui-autotest-skill/
  README.md
  LICENSE
  .claude-plugin/
    plugin.json
    marketplace.json
  commands/                          ← Claude Code native format
    ios-test.md
    add-accessibility.md
  skills/                            ← skills.sh / npx format
    ios-test/
      SKILL.md
    add-accessibility/
      SKILL.md

Who This Is For

• iOS developers who want to test their SwiftUI apps visually without writing XCUITest
• Solo developers who don't have a QA team
• Teams that want consistent, repeatable test runs across projects
• Developers preparing for App Store review and need accessibility compliance
• Anyone who wants to catch layout bugs, crashes, and memory leaks before users do

Which Scope Should I Choose?

Contributing

Contributions are welcome! Open an issue or submit a pull request.

License

This project is available under the MIT License. See LICENSE for details.