> ios-chaos-monkey
Crash-hunter skill for iOS 26 / Swift 6.2 clinic-architecture codebases that finds and fixes concurrency, memory, and I/O bugs using TDD. Covers data races, actor isolation, retain cycles, SwiftData context misuse, and sync-related failures in Domain/Data/App boundaries. Use when debugging crashes or hard-to-reproduce failures in ios-* and swift-* clinic modules.
curl "https://skillshub.wtf/pproenca/dot-skills/ios-chaos-monkey?format=md"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+DesignSystemonly (neverData, never sibling features) - App target is the convergence point and owns
DependencyContainer, concrete coordinators, and Route Shell wiring Domainstays pure Swift and defines models plus repository,*Coordinating,ErrorRouting, andAppErrorcontractsDataowns 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)
When to Apply
Reference these guidelines when:
- Hunting data races, deadlocks, and concurrency crashes in Swift
- Auditing memory management for retain cycles and use-after-free
- Reviewing async/await code for cancellation and continuation leaks
- Stress-testing file I/O and CoreData/SwiftData persistence layers
- Writing proof-of-crash tests before implementing fixes
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Data Races & Thread Safety | CRITICAL | race- |
| 2 | Memory Corruption & Leaks | CRITICAL | mem- |
| 3 | Deadlocks & Thread Starvation | HIGH | dead- |
| 4 | Async/Await & Structured Concurrency | HIGH | async- |
| 5 | File I/O & Persistence Corruption | MEDIUM-HIGH | io- |
| 6 | Collection & State Mutation | MEDIUM | mut- |
| 7 | Resource Exhaustion | MEDIUM | exhaust- |
| 8 | Objective-C Interop Traps | LOW-MEDIUM | objc- |
Quick Reference
1. Data Races & Thread Safety (CRITICAL)
race-dictionary-concurrent-write- Concurrent Dictionary mutation crashes with EXC_BAD_ACCESSrace-array-concurrent-append- Concurrent Array append corrupts internal bufferrace-property-access- Unsynchronized property read-write across threadsrace-lazy-initialization- Lazy property double-initialization under concurrencyrace-singleton-initialization- Non-atomic singleton exposes partially constructed staterace-bool-flag- Non-atomic Bool flag creates check-then-act racerace-closure-capture-mutation- Closure captures mutable reference across threadsrace-delegate-nilification- Delegate set to nil during active callback
2. Memory Corruption & Leaks (CRITICAL)
mem-closure-retain-cycle- Strong self capture in escaping closures creates retain cyclemem-timer-retain-cycle- Timer retains target creating undiscoverable retain cyclemem-delegate-strong-reference- Strong delegate reference prevents deallocationmem-unowned-crash- Unowned reference crashes after owner deallocationmem-notification-observer-leak- NotificationCenter observer retains closure after removal neededmem-combine-sink-retain- Combine sink retains self without cancellable storagemem-async-task-self-capture- Task captures self extending lifetime beyond expected scope
3. Deadlocks & Thread Starvation (HIGH)
dead-sync-on-main- DispatchQueue.main.sync from main thread deadlocks instantlydead-recursive-lock- Recursive lock acquisition on same serial queuedead-actor-reentrancy- Actor reentrancy produces unexpected interleavingdead-semaphore-in-async- Semaphore.wait() inside async context deadlocks thread pooldead-queue-hierarchy- Dispatch queue target hierarchy inversion deadlocksdead-mainactor-blocking- Blocking MainActor with synchronous heavy work
4. Async/Await & Structured Concurrency (HIGH)
async-missing-cancellation- Missing Task.isCancelled check wastes resources after navigationasync-detached-task-leak- Detached task without cancellation handle leaks workasync-task-group-error- TaskGroup silently drops child task errorsasync-continuation-leak- CheckedContinuation never resumed leaks awaiting taskasync-actor-hop-starvation- Excessive MainActor hops in hot loop starve UI updatesasync-unsafe-sendable- @unchecked Sendable hides data race from compiler
5. File I/O & Persistence Corruption (MEDIUM-HIGH)
io-concurrent-file-write- Concurrent file writes corrupt data without coordinationio-coredata-cross-thread- CoreData NSManagedObject accessed from wrong threadio-swiftdata-background- SwiftData model accessed from wrong ModelContextio-plist-concurrent-mutation- UserDefaults concurrent read-write produces stale valuesio-filemanager-race- FileManager existence check then use is a TOCTOU raceio-keychain-thread-safety- Keychain access from multiple threads returns unexpected errors
6. Collection & State Mutation (MEDIUM)
mut-enumerate-and-mutate- Collection mutation during enumeration crashes at runtimemut-kvo-dealloc-crash- KVO observer not removed before deallocation crashesmut-index-out-of-bounds- Array index access without bounds check crashesmut-force-unwrap- Force unwrapping optional in production crashes on nilmut-enum-future-cases- Non-exhaustive switch crashes on unknown enum case
7. Resource Exhaustion (MEDIUM)
exhaust-unbounded-task-spawn- Unbounded task spawning in loop exhausts memoryexhaust-thread-explosion- GCD creates unbounded threads under concurrent loadexhaust-urlsession-leak- URLSession not invalidated leaks delegate and connectionsexhaust-file-descriptor-leak- File handle not closed leaks file descriptorsexhaust-memory-warning-ignored- Low memory warning ignored triggers Jetsam kill
8. Objective-C Interop Traps (LOW-MEDIUM)
objc-unrecognized-selector- Missing @objc annotation crashes with unrecognized selectorobjc-nsnull-in-json- NSNull in decoded JSON collection crashes on accessobjc-bridge-type-mismatch- Swift/ObjC bridge type mismatch crashes at runtimeobjc-dynamic-dispatch- Missing dynamic keyword breaks method swizzling
How to Use
Read individual reference files for detailed explanations and code examples:
- Section definitions - Category structure and impact levels
- Rule template - Template for adding new rules
Reference Files
| File | Description |
|---|---|
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for new rules |
| metadata.json | Version and reference information |
> related_skills --same-repo
> rust-write-tests
Skill for writing expert-level Rust tests. Teaches the "What Could Break?" framework, five transformations from superficial to expert tests, flake hunting protocol, intent-based assertions, naming conventions, and a mandatory self-review checklist. Triggers on writing Rust tests, designing test cases, improving test quality, or reviewing test coverage.
> rust-implement
Write production-grade Rust code using a multi-pass approach. Design types first, then implement, then simplify, then verify with automated lint. Use this skill whenever writing new Rust functions, structs, modules, or features. Triggers on Rust implementation, new Rust code, Rust functions, Rust modules, error handling in Rust, async Rust, or type design in Rust.
> valid-skill
A valid test skill with proper formatting. This skill should pass all validations and serves as a reference for the expected format.
> too-long-skill
This skill has more than 500 lines which should fail validation.