Skip to content
Agentmart
Submit a tool

ios-debug-and-stabilize

Use when an iOS app is crashing, hanging, misrendering, failing tests, or showing warnings around SwiftUI state, SwiftData, concurrency, entitlements…

Skill by phrypy

IndexedMIT★ 7
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/phrypy-ios-debug-and-stabilize

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when an iOS app is crashing, hanging, misrendering, failing tests, or showing warnings around SwiftUI state, SwiftData, concurrency, entitlements, simulator/device differences, or App Store submission stability.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/ios-debug-and-stabilize

What's inside

Skill name
ios-debug-and-stabilize
Description
Use when an iOS app is crashing, hanging, misrendering, failing tests, or showing warnings around SwiftUI state, SwiftData, concurrency, entitlements, simulator/device differences, or App Store submission stability.
License
MIT
Instructions
50 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# iOS Debug And Stabilize

Treat debugging as evidence work, not guesswork.

## Order Of Operations

1. reproduce the issue
2. identify whether it is simulator-only, device-only, or both
3. narrow to the exact screen, interaction, or launch phase
4. inspect logs and crash signals
5. fix the smallest proven cause
6. verify the specific failure is gone

## High-Risk Areas

- SwiftUI body-time side effects
- mixed state ownership across views and singletons
- detached tasks touching UI or persistence
- CloudKit and shared-container startup paths
- extension-safe code paths
- capabilities that do not match runtime behavior

## Crash Triage Rules

- `EXC_BAD_ACCESS` in SwiftUI often means invalid ownership, stale objects, or unsafe cross-thread access
- `signal 9` is termination, not a normal Swift crash
- if CloudKit is involved, separate sync errors from UI crashes
- if the line highlighted is `body`, the bug is often upstream in state or side effects

## Warning Policy

Fix warnings that suggest:

- undefined concurrency behavior
- actor isolation violations
- deprecated platform paths tied to release code
- entitlement, capability, privacy, or review risk

Ignore only clear simulator noise after confirming it does not affect device or archive builds.

## Verification Standard

- the failing interaction now works
- the project builds cleanly
- the relevant tests pass
- if the bug was device-specific, confirm on device before claiming victory

Do not call something fixed just because the simulator stopped crashing once.

From phrypy/ios-app-playbook, MIT.

More from phrypy/ios-app-playbook

Signals

Stars
7
Forks
2
Open issues
0
Last commit (this folder)
Apr 20, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from phrypy

Cite this page

ios-debug-and-stabilize skill. Agent Mart. https://agentmart.dev/skills/phrypy-ios-debug-and-stabilize (last updated 2026-10-24)