sim-debug

Debug iOS/visionOS simulator issues with a hypothesis-driven four-phase workflow.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/shihwesley/shihwesleys-harness --skill sim-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sim-debug
Source: https://github.com/shihwesley/shihwesleys-harness/tree/main/commands/sim-debug
Command: npx skills add https://github.com/shihwesley/shihwesleys-harness --skill sim-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill provides a structured, hypothesis-driven debugging workflow for iOS/visionOS simulators, enabling engineers to observe, hypothesize, test, and fix issues while preserving session state across runs.

Core Features & Use Cases

  • Phase-driven debugging: Observe, Hypothesize, Test, and Fix with a clear, repeatable sequence.
  • Multi-tool support: Integrates XcodeBuildMCP and AXe CLI for build/run, UI inspection, and scripted reproduction.
  • State persistence: Tracks progress in .claude/cache/debug-state.md to allow resuming sessions after interruptions.
  • Reproduction tooling: Includes references and scripts to script deterministic bug repros.

Quick Start

Begin a new debugging session and follow the four-phase workflow to observe, hypothesize, test, and fix the simulator issue.

Frequently Asked Questions about sim-debug

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

FAQPage Schema
What is a hypothesis-driven workflow for debugging iOS simulator issues?

A hypothesis-driven iOS simulator debugging workflow systematically guides you through Observe, Hypothesize, Test, and Fix phases to identify and resolve UI or behavior anomalies using stateful tracking and scripted reproductions.

How do I debug an iOS simulator bug that is hard to reproduce?

You can debug hard-to-reproduce iOS simulator bugs by scripting deterministic reproductions using integrated tooling like XcodeBuildMCP and AXe CLI, while persisting debugging state to track progress across repeated runs.

Can I use LLDB to debug visionOS simulator behavior anomalies?

Yes, you can use LLDB workflows to debug visionOS simulator behavior anomalies, applying a structured debugging flow that includes UI snapshots and reference materials to guide resolution.

Does this simulator debugging workflow persist state across interrupted sessions?

Yes, the simulator debugging workflow persists state to a cache file, allowing you to resume debugging sessions after interruptions by tracking your progress through the Observe, Hypothesize, Test, and Fix phases.

What's the best way to systematically test UI bugs in an iOS simulator?

The best way to systematically test iOS simulator UI bugs is using a phase-driven workflow that integrates UI inspection tools like AXe CLI, enabling repeated runs and scripted reproductions for consistent resolution.

When do I need a structured debugging flow for iOS or visionOS simulators?

You need a structured debugging flow for iOS or visionOS simulators when encountering complex UI or behavior anomalies that require hypothesis-driven testing, stateful tracking, and multi-tool integration to resolve effectively.