app-tester

Build and maintain a navigable graph of iOS/macOS app screens.

3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/markgravity/app-tester-skill --skill app-tester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-tester
Source: https://github.com/markgravity/app-tester-skill/tree/main
Command: npx skills add https://github.com/markgravity/app-tester-skill --skill app-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates building and maintaining a navigable graph of iOS/macOS app screens from the project's navigation source, enabling reproducible flows and easier debugging.

Core Features & Use Cases

  • Auto-discovers screens and builds a .claude/app-flow-graph.json at the project root.
  • Instruments screens with .accessibilityIdentifier() and structured logs, to verify screen appearances and transitions.
  • Drives flows by tapping accessibility IDs and validating transitions, with inline recovery for failed steps and graph updates.

Quick Start

Clone this skill into Claude Code skills directory and run the discovery, instrumentation, and graph-testing phases to build your app-flow graph.

Frequently Asked Questions about app-tester

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

FAQPage Schema
How do I automate iOS navigation graph building from source?

Automate iOS navigation graph building by running a discovery phase that auto-discovers app screens from navigation source and generates a navigable graph at the project root. This process parses screen definitions and extracts transitions to create a reproducible flow map.

How do I instrument iOS screens for automated flow testing?

Instrument iOS screens for automated flow testing by injecting accessibilityIdentifier tags and structured logs into source code. This verifies screen appearances and transitions during end-to-end navigation workflows.

Can I validate macOS app navigation workflows automatically?

You can validate macOS app navigation workflows automatically by driving flows that tap accessibility IDs and validate transitions. The process applies to debugging complex navigation across devices and platforms with inline recovery for failed steps.

What is the best way to debug complex iOS navigation workflows across devices?

The best way to debug complex iOS navigation workflows is to build a navigable graph of app screens with auto-instrumentation. This enables reproducible flows, easier debugging, and end-to-end flow testing across platforms.

Does navigation graph testing work without adding accessibility identifiers?

Navigation graph testing requires accessibility identifiers to drive flows by tapping accessibility IDs. The instrumentation phase adds these tags and structured logs to verify screen appearances and transitions during validation.

How do I maintain an app navigation graph when source changes?

Maintain an app navigation graph by re-running the discovery and instrumentation phases to update the graph. Inline recovery for failed steps automatically updates the navigable graph when navigation source changes.