Swift Verify

SkillSwiftSwiftUIiOSClaudeCodex

Let your agent prove new Swift features work by driving them in a simulator. Get visual confirmation through screenshots, screen text, and video without opening the app yourself.

An orange bird in flight on a white rounded tile, with a green check mark badge at its corner, on a dark green background.

Your agent might tell you a feature is finished because the code compiles, but you won't know if a button is broken or a sheet fails to close until you open the app yourself. This leads to manual verification and constant back-and-forth to fix things the agent missed. Additionally, every new session starts from zero, wasting tokens and time as the agent re-learns how to build, launch, and navigate your app.

Swift Verify lets your agent write an app-specific verify skill that lives in your project. This skill remembers how to launch the app and reach each feature, so later sessions can get straight to work. Instead of just taking the agent's word, you get visual proof: screenshots, screen text, and video of the agent actually driving the feature in a simulator.

Features

  • A persistent, app-specific skill. The agent creates a skill that knows how to build, launch, and navigate your app. Because it lives in your project, subsequent sessions can use it immediately instead of re-discovering your setup.
  • A growing map of your features. The agent maintains a file for each feature, recording how to reach it, how to drive it, and any traps it found during previous runs.
  • Visual proof you can see. Every step produces a screenshot and screen text. For flows with motion, the agent provides a video, allowing you to review the exact user experience without opening a simulator.
  • Clean, isolated simulators. Each project uses its own dedicated simulator copy. This ensures every run starts with no leftover data and keeps your personal simulators untouched.
  • No test code in your app. The agent drives your app exactly as it is without adding debug screens or extra labels.
  • Support for Mac apps and CLI tools. In Claude Code, the agent can drive Mac apps using computer use, after you approve it. It also handles command-line tools by using terminal output as proof.

How to use it

You can trigger the agent to create or run verifications using slash commands in Claude or prefixing with $ in Codex.

  • "/create-verification-skill verify the sign in flow"
  • "Verify the new search feature in the running app."
  • "Show me the add-book flow on the simulator, with a video."
  • "I just finished the settings screen. Check it in the app before I merge."
  • "Does the item I add still show up after I relaunch the app? Prove it."
  • "Add the new sharing feature to the verify map."

FAQs

Does this replace my UI tests?

No. Use XCUITest for core journeys that must always work. Use this skill to drive new flows and verify visual results quickly.

What can't it prove?

Since it runs in a simulator, it cannot prove behavior related to the camera, push notifications, iCloud, real network conditions, haptics, or the speed of a real device.

Which agents does it work with?

It is built for Claude and Codex. Driving a Mac app requires computer use.

What happens after you buy

  1. 1

    Download

    Click the download link to get the ZIP file. Extract it, then share the folder with your agent.

  2. 2

    Your Agent Guides You Through Setup

    Your agent will follow INSTALL.md to install the skill. You will need to manually add MobileBuildMCP and enable its UI automation tools for the agent to drive the simulator.

  3. 3

    Make it yours

    Ask your agent to create a new verify skill, run a specific feature check, or update the feature map as you add more functionality to your app.

Let your agent check if Swift Verify is right for you.

Just copy this prompt:

Read https://tools.natashatherobot.com/swift-verify.md, the page for Swift Verify. Based on what you know about my projects and workflow, assess whether Swift Verify would help me verify that my Swift app features actually work in a simulator before I merge them. Explain how receiving visual proof like screenshots and video would improve my workflow, how the persistent feature map avoids repetitive setup, and whether the simulator-based limitations matter for my work. Tell me if the benefit is worth the price. Ask me for more context if needed.

It is a starter tool

Swift Verify is a starter tool you can customize for your work.

NatashaTheRobot claims no rights to what you make with Swift Verify. Other people's work keeps its own license. Keep the included NOTICE file with any version of the tool you share or sell.

The full terms are in the LICENSE file of the download. Swift Verify comes without warranty.