View Refactor
robinebers/openusage
Refactor macOS SwiftUI views and scenes with strong defaults for small dedicated subviews, stable sidebar and selection structure, explicit command and toolbar ownership, scene-aware state, and…
Testing practices for iOS 26 / Swift 6.2 clinic modular MVVM-C applications.
Install iOS Testing
$ npx skills add pproenca/dot-skills --skill ios-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pproenca/dot-skills ios-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.experimental/ios-testing .claude/skills/ios-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ios-testing" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/ios-testing into .claude/skills/ios-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ios-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/ios-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pproenca/dot-skills --skill ios-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pproenca/dot-skills ios-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.experimental/ios-testing .agents/skills/ios-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ios-testing" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/ios-testing into .agents/skills/ios-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ios-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill ios-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pproenca/dot-skills ios-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.experimental/ios-testing .cursor/skills/ios-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ios-testing" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/ios-testing into .cursor/skills/ios-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ios-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pproenca/dot-skills.git --path skills/.experimental/ios-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pproenca/dot-skills --skill ios-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pproenca/dot-skills ios-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.experimental/ios-testing .gemini/skills/ios-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ios-testing" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/ios-testing into .gemini/skills/ios-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ios-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pproenca/dot-skills ios-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pproenca/dot-skills --skill ios-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.experimental/ios-testing .github/skills/ios-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ios-testing" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/ios-testing into .github/skills/ios-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ios-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill ios-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pproenca/dot-skills ios-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.experimental/ios-testing .opencode/skills/ios-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ios-testing" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/ios-testing into .opencode/skills/ios-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ios-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ios-testing- GitHub stars
- 214
- Token cost
- ~2.1k tokens
- SKILL.md length
- 611 words
- Files
- 48 (incl. references, assets)
- Skills in repo
- 182
- Repo updated
- First seen
- Licence
- MIT
At a glance
Testing practices for iOS 26 / Swift 6.2 clinic modular MVVM-C applications.
- Works in 8 steps: Test Architecture & Testability (CRITICAL) → Unit Testing Fundamentals (CRITICAL) → Test Doubles & Isolation (HIGH) → …
- Refactoring tests for ios- and swift- clinic modules
- SKILL.md covers Clinic Architecture Contract…, When to Apply, Rule Categories by Priority and Quick Reference, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
iOS Testing is an agent skill from pproenca/dot-skills. Testing practices for iOS 26 / Swift 6.2 clinic modular MVVM-C applications. Covers unit/UI/snapshot testing, protocol-based mocks, async actor isolation, and dependency-injected test architecture aligned with Domain protocols, App-target composition, and Data-owned I/O boundaries. Use when writing, reviewing, or refactoring tests for ios- and swift- clinic modules.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 50 other files, including reference files and assets (for example `assets/templates/_template.md`, `metadata.json` and `references/_sections.md`).
It sits in Mobile, covering iOS development, Unit testing and Refactoring. It works with iOS, Swift and SwiftUI. The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.
When your agent uses it
- Refactoring tests for ios- and swift- clinic modules
- Tasks that involve iOS development
- Tasks that involve Unit testing
Example prompts
- “/ios-testing”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
iOS Testing loads about 2.1k tokens when it runs, and up to ~24k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 611 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 611 words, ~2,058 tokens.
Download SKILL.mdSave it as
.claude/skills/ios-testing/SKILL.md (or your agent's skills folder). This skill also uses 47 other files; get the full folder from GitHub.- name
- ios-testing
- description
- Testing practices for iOS 26 / Swift 6.2 clinic modular MVVM-C applications. Covers unit/UI/snapshot testing, protocol-based mocks, async actor isolation, and dependency-injected test architecture aligned with Domain protocols, App-target composition, and Data-owned I/O boundaries. Use when writing, reviewing, or refactoring tests for ios-* and swift-* clinic modules.
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+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:
- Writing new unit tests or UI tests for iOS apps
- Designing testable architecture with dependency injection
- Testing async/await, actors, and Combine publishers
- Setting up snapshot testing or visual regression suites
- Configuring CI pipelines, test plans, and parallel execution
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Test Architecture & Testability | CRITICAL | arch- |
| 2 | Unit Testing Fundamentals | CRITICAL | unit- |
| 3 | Test Doubles & Isolation | HIGH | mock- |
| 4 | Async & Concurrency Testing | HIGH | async- |
| 5 | SwiftUI Testing | MEDIUM-HIGH | swiftui- |
| 6 | UI & Acceptance Testing | MEDIUM | ui- |
| 7 | Snapshot & Visual Testing | MEDIUM | snap- |
| 8 | Test Reliability & CI | LOW-MEDIUM | ci- |
Quick Reference
1. Test Architecture & Testability (CRITICAL)
arch-protocol-dependencies- Depend on protocols, not concrete typesarch-constructor-injection- Use constructor injection over service locatorsarch-test-target-separation- Separate unit and UI test targetsarch-testable-import- Use @testable import sparinglyarch-single-responsibility-tests- One assertion concept per testarch-arrange-act-assert- Structure tests as Arrange-Act-Assert
2. Unit Testing Fundamentals (CRITICAL)
unit-swift-testing-framework- Use Swift Testing over XCTest for new testsunit-parameterized-tests- Use parameterized tests for input variationsunit-descriptive-test-names- Name tests after the behavior they verifyunit-expect-over-assert- Use #expect and #require over XCTAssertunit-require-preconditions- Use #require for test preconditionsunit-test-suites- Organize related tests into suitesunit-test-tags- Use tags to categorize cross-cutting tests
3. Test Doubles & Isolation (HIGH)
mock-protocol-based-mocks- Create mocks from protocols, not subclassesmock-spy-for-verification- Use spies to verify interactionsmock-stub-return-values- Use stubs for deterministic return valuesmock-avoid-over-mocking- Avoid mocking value types and simple logicmock-fake-for-integration- Use in-memory fakes for integration testsmock-dependency-container- Use a dependency container for test configuration
Show full SKILL.md (242 more words)Show less
4. Async & Concurrency Testing (HIGH)
async-await-directly- Await async functions directly in testsasync-confirmation- Use confirmation() for callback-based APIsasync-mainactor-isolation- Test MainActor-isolated code on MainActorasync-actor-testing- Test actor state through async interfaceasync-task-cancellation- Test task cancellation paths explicitly
5. SwiftUI Testing (MEDIUM-HIGH)
swiftui-test-observable-models- Test @Observable models as plain objectsswiftui-environment-injection- Inject environment dependencies for testsswiftui-preview-as-test- Use previews as visual smoke testsswiftui-view-model-extraction- Extract logic from views into testable modelsswiftui-binding-testing- Test binding behavior with @Bindable
6. UI & Acceptance Testing (MEDIUM)
ui-accessibility-identifiers- Use accessibility identifiers for element queriesui-page-object-pattern- Encapsulate screens in page objectsui-launch-arguments- Configure test state via launch argumentsui-wait-for-elements- Wait for elements instead of using sleep()ui-test-user-journeys- Test complete user journeys, not individual screensui-reset-state-between-tests- Reset app state between UI tests
7. Snapshot & Visual Testing (MEDIUM)
snap-swift-snapshot-testing- Use swift-snapshot-testing for visual regressionsnap-device-matrix- Snapshot across device sizes and traitssnap-named-references- Use named snapshot references for claritysnap-inline-snapshots- Use inline snapshots for non-image assertions
8. Test Reliability & CI (LOW-MEDIUM)
ci-test-plans- Use Xcode Test Plans for environment configurationsci-parallel-execution- Enable parallel test executionci-flaky-test-quarantine- Quarantine flaky tests instead of disabling themci-deterministic-test-data- Use deterministic test data over random generationci-coverage-thresholds- Set coverage thresholds for critical paths
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 |
© pproenca, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 47 other files (references, assets) in skills/.experimental/ios-testing of pproenca/dot-skills.
- SKILL.md
- assets/templates/_template.md
- metadata.json
- references/_sections.md
- references/arch-arrange-act-assert.md
- references/arch-constructor-injection.md
- references/arch-protocol-dependencies.md
- references/arch-single-responsibility-tests.md
- references/arch-test-target-separation.md
- references/arch-testable-import.md
- references/async-actor-testing.md
- references/async-await-directly.md
- references/async-confirmation.md
- references/async-mainactor-isolation.md
- references/async-task-cancellation.md
- references/ci-coverage-thresholds.md
- references/ci-deterministic-test-data.md
- references/ci-flaky-test-quarantine.md
- … and 30 more
Open the folder on GitHubat commit cf93c57
Compare with similar skills
iOS Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| iOS Testing this skillpproenca/dot-skills | 214 | — | ~2.1k | Automated safety check: Pass | MIT | |
| View Refactorrobinebers/openusage | 4.3k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Swiftui Expert SkillAFK-surf/OpenBridge | 430 | 2 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Dep Validateblokadaorg/blokada | 3.3k | — | ~5.7k | Automated safety check: Notes | MPL-2.0 | |
| Swiftui AnimationAstraFoundry/KumoApp | 290 | — | ~4.1k | Automated safety check: Pass | AGPL-3.0 | |
| Snapshot Testsmicrosoft/SwiftStreamingMarkdown | 377 | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
Swiftui Expert Skill
AFK-surf/OpenBridge
Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption.
Dep Validate
blokadaorg/blokada
A skill your agent uses to validate risky dependency bumps end to end as a local or cloud-launched agent.
Swiftui Animation
AstraFoundry/KumoApp
Implement, review, or improve SwiftUI animations and transitions.
- Official
Snapshot Tests
microsoft/SwiftStreamingMarkdown
Record and validate swift-snapshot-testing snapshots in the SwiftStreamingMarkdown package: regenerate reference PNGs, run snapshot tests, and diff failed snapshots.
Bootstrap iOS
RayFernando1337/rayfernando-skills
Bootstrap agents for iOS, iPadOS, macOS, Swift, SwiftUI, SwiftData/Core Data, Swift Testing, Xcode build/test/debug, Simulator, App Intents, or XcodeBuildMCP work.
More from pproenca/dot-skills
All 182 skills in this repoAudio Voice Recovery
pproenca/dot-skills
Audio forensics and voice recovery guidelines for CSI-level audio analysis.
Codemod React Pipeline
pproenca/dot-skills
Guided, scripted pipeline for running JSX/TSX/React codemods safely across large legacy codebases.
Dev Rfc
pproenca/dot-skills
Create well-structured RFCs and technical proposals for software projects.
Dx Harness
pproenca/dot-skills
Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.
Language Spec Author
pproenca/dot-skills
Turn a rough idea for a language into a complete, implementable specification — a DSL, query, config/data, template, or protocol language — by interviewing the author dimension by dimension until…
Python Pep Author
pproenca/dot-skills
Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python…
Related
Categories
Questions about iOS Testing
What does iOS Testing do?
Testing practices for iOS 26 / Swift 6.2 clinic modular MVVM-C applications. iOS Testing is an agent skill from pproenca/dot-skills.2 clinic modular MVVM-C applications.
When should I use iOS Testing?
iOS Testing fits situations like: refactoring tests for ios- and swift- clinic modules; tasks that involve iOS development; tasks that involve Unit testing.
How do I install iOS Testing in Claude Code?
Run `npx skills add pproenca/dot-skills --skill ios-testing -a claude-code`. Or copy the skill folder (skills/.experimental/ios-testing in pproenca/dot-skills) into .claude/skills/ios-testing in your project. Claude Code loads it when a task matches its description.
How do I install iOS Testing in Codex?
Run `npx skills add pproenca/dot-skills --skill ios-testing -a codex`. Or copy the skill folder (skills/.experimental/ios-testing in pproenca/dot-skills) into .agents/skills/ios-testing in your project. Codex loads it when a task matches its description.
Can I use iOS Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pproenca/dot-skills --skill ios-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ios-testing, .gemini/skills/ios-testing, .github/skills/ios-testing and .opencode/skills/ios-testing in your project.
What does iOS Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: iOS Testing is instructions for the agent only.
Does iOS Testing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is iOS Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does iOS Testing use?
iOS Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does iOS Testing use?
About 2.1k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 22k tokens, read only when the agent opens those files.
What are the alternatives to iOS Testing?
Skills that share tags, products or a category with iOS Testing: View Refactor (robinebers/openusage, 4.3k stars), Swiftui Expert Skill (AFK-surf/OpenBridge, 430 stars), Dep Validate (blokadaorg/blokada, 3.3k stars) and Swiftui Animation (AstraFoundry/KumoApp, 290 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains iOS Testing?
pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 214 GitHub stars. The repository holds 182 skills in this directory. The repository was last updated on August 15, 2026.
Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.