Ios Chaos Monkey

This is a crash-hunting checklist for Swift 6.2 and iOS 26 codebases built on the clinic MVVM-C architecture. It gives you 47 TDD-style rules across data races, memory leaks, deadlocks, async/await traps, and SwiftData misuse. Each rule follows the same pattern: show the dangerous code, write a test that proves the crash, then fix it. Reach for this when you're debugging EXC_BAD_ACCESS, hunting retain cycles in coordinators, or dealing with weird SwiftData context threading issues. The categories are prioritized by severity, so you can start with the critical stuff like concurrent dictionary writes and actor reentrancy before worrying about Objective-C interop edge cases.

skills.sh installs: 267
GitHub stars: 222
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add pproenca/dot-skills --skill ios-chaos-monkey --agent claude-code

Installs into .claude/skills of the current project.

Files

iOS Chaos Monkey — Crash-Hunter Best Practices

Adversarial crash-hunting guide for iOS and Swift applications. Contains 47 rules across 8 categories, prioritized by crash severity. Every rule follows TDD: dangerous code first, a failing test that proves the bug, then the fix that makes the test pass.

Clinic Architecture Contract (iOS 26 / Swift 6.2)

All guidance in this skill assumes the clinic modular MVVM-C architecture:

Feature modules import Domain + DesignSystem only (never Data, never sibling features)
App target is the convergence point and owns DependencyContainer, concrete coordinators, and Route Shell wiring
Domain stays pure Swift and defines models plus repository, *Coordinating, ErrorRouting, and AppError contracts
Data owns SwiftData/network/sync/retry/background I/O and implements Domain protocols
Read/write flow defaults to stale-while-revalidate reads and optimistic queued writes
ViewModels call repository protocols directly (no default use-case/interactor layer)