ui-scan

Automates UI test environment setup and accessibility scanning for iOS apps.

49|9|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/Terryc21/xcode-workflow-skills --skill ui-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-scan
Source: https://github.com/Terryc21/xcode-workflow-skills/tree/main/skills/ui-scan
Command: npx skills add https://github.com/Terryc21/xcode-workflow-skills --skill ui-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps teams prepare a deterministic UI test environment and conduct accessibility scans, with recommendations to bypass splash/onboarding during tests.

Core Features & Use Cases

  • Setup of UI test environment with launch arguments to bypass splash/onboarding
  • Accessibility and identifier checks, including element discovery strategies
  • Guidance for stable test execution and issue diagnosis across views and modules

Quick Start

Run the UI scan workflow to set up the test environment and perform an accessibility scan.

Frequently Asked Questions about ui-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up an iOS UI test environment to bypass onboarding screens?

Set up the iOS UI test environment by configuring launch arguments to bypass splash and onboarding screens. This ensures deterministic test execution by skipping initial flows and directly accessing target views.

How can I run accessibility scans for iOS apps in Xcode Simulator?

Run accessibility scans for iOS apps by applying element discovery strategies and identifier checks across views. This validates accessibility compliance and diagnoses UI issues directly within the Xcode Simulator environment.

What is the best way to ensure stable UI test execution across multiple iOS modules?

Stable UI test execution across iOS modules requires a deterministic environment using launch arguments and robust element discovery. This approach minimizes flakiness by bypassing onboarding and standardizing identifier checks across views.

Why are my iOS UI tests failing to find elements after the splash screen?

iOS UI tests fail to find elements after the splash screen due to unconfigured onboarding bypass logic. Resolve this by setting specific launch arguments to skip splash screens and implement robust element discovery strategies.

Do I need specific dependencies to perform accessibility compliance checks for iOS?

No specific dependencies are required to perform accessibility compliance checks for iOS. The workflow operates directly within the existing Xcode and Simulator environment to automate setup and execute identifier checks.

Can I automate onboarding bypass logic for deterministic iOS UI testing?

Yes, you can automate onboarding bypass logic for deterministic iOS UI testing by configuring launch arguments during test environment setup. This skips splash screens and ensures modules load directly for scanning.