Use when an agent needs to integrate the Inspector library into an app without focusing on the MCP bridge: startup wiring, configuration/customization, debug-only gating, and custom panel registration. Especially useful when patching another iOS app to call `Inspector.start()` correctly and optionally register custom Inspector libraries.
Use when an agent needs to implement or modify the Inspector library itself — panel UI, hierarchy/runtime behavior, custom property models, macros, or Example-app dogfooding. Especially useful when changing `Sources/Inspector/`, `Sources/InspectorInterface/`, or `Sources/InspectorMacros/` and you need the repo's architecture and verification workflow in one place.
Use when an agent needs to inspect a live iOS app through the Inspector MCP bridge, register or troubleshoot InspectorMCPServer for a consumer Xcode project, or query, resolve, and snapshot the live UIKit hierarchy on Simulator. Especially useful when Inspector is a SwiftPM dependency of another app and the Inspector package path must be derived from Xcode DerivedData instead of assumed from the current repo.
Use when an agent needs to patch a consumer iOS app so it exposes the Inspector MCP bridge, add or verify the app-side Inspector startup configuration, or choose the correct UIKit or SwiftUI lifecycle entry point for `enableMCPBridge`, `snapshotExpiration = 300`, and `snapshotMaxCount = 8`. Especially useful when preparing another app to be driven by `InspectorMCPServer` and then handed off to the `inspector-mcp` skill for live inspection.