Ios Testing

Covers testing for modular iOS 26/Swift 6.2 apps built on MVVM-C architecture with protocol-based dependency injection. You get 44 rules across unit, UI, snapshot, and async testing, organized by priority so you can focus on architecture decisions first (protocol dependencies, constructor injection) before diving into Swift Testing syntax or CI config. Everything assumes the clinic pattern where Domain defines contracts, Data owns I/O, and features stay isolated. Most useful when setting up tests for a new feature module or refactoring existing tests to work with actor isolation and stale-while-revalidate patterns. The priority system is helpful because it stops you from bikeshedding snapshot device matrices before nailing down your mock strategy.

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

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

iOS Testing Best Practices

Comprehensive testing guide for iOS and Swift applications, written at principal engineer level. Contains 44 rules across 8 categories, prioritized by impact to guide test architecture decisions, test authoring patterns, and CI infrastructure.

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)