swift-testing-expert
Skill7 starsChanged 16 days agoMITView on GitHub
Use when writing new Swift tests, modernizing XCTest suites, debugging flaky tests, or improving test quality and maintainability in Apple-platform or Swift server projects. Expert guidance for Swift Testing - test structure, expect/#require macros, traits and tags, parameterized tests, test…
7 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- uinaf/slopwakeedited, first seen Nov 3, 2026
- VelimirMueller/claude-skillsword for word, first seen Nov 1, 2026
- The-Artificer-of-Ciphers-LLC/skills-from-the-artificeredited, first seen Nov 1, 2026
- ramybarsoum/claude-skillsedited, first seen Oct 13, 2026
- AFK-surf/OpenBridgeedited, first seen Oct 9, 2026
- Provenance-Emu/Provenanceedited, first seen Oct 8, 2026
Used with
Projects with it also use swiftui-expert-skill.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
xfstudioSkillswiftui-expert-skill
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. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.
Also in 3 projects that use this
Other versions7 projects use a version of this.
Word for word · 1
- VelimirMueller/claude-skills★ 7100% same
Edited · 6
- Provenance-Emu/Provenance★ 6.4k97% same
- AvdLee/Swift-Testing-Agent-Skill★ 44497% same
- AFK-surf/OpenBridge★ 43097% same
- The-Artificer-of-Ciphers-LLC/skills-from-the-artificer★ 697% same
- ramybarsoum/claude-skills★ 097% same
- uinaf/slopwake★ 097% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository156 other files it gives its agents.
- skills/swift/swiftui-design-principles/AGENTS.mdAGENTS.md
- skills/swift/ios-code-audit/CLAUDE.mdCLAUDE.md
- skills/swift/swift-focusengine-pro/llms.txtllms.txt
- build-llm-seamSkill
- build-mcp-serverSkill
- build-rag-pipelineSkill
- secure-llm-featuresSkill
- set-up-llm-evalsSkill
- build-nextjs-backendSkill
- build-supabase-edge-functionSkill
- configure-backend-testsSkill
- design-http-apiSkill
- harden-backendSkill
- scaffold-fastapi-serviceSkill
- scaffold-go-serviceSkill
- scaffold-hono-serviceSkill
- secure-supabase-rlsSkill
- set-up-backend-authSkill
- set-up-background-jobsSkill
- set-up-databaseSkill
- set-up-nextjs-supabase-authSkill
- set-up-observabilitySkill
- set-up-supabaseSkill
- build-cliSkill
- release-cliSkill
- set-up-dev-toolchainSkill
- audit-securitySkill
- audit-toolchainSkill
- extend-skillsetSkill
- promote-releaseSkill
- set-up-stack-profileSkill
- write-commit-messagesSkill
- write-pull-requestsSkill
- analyze-complexitySkill
- apply-algorithmsSkill
- apply-design-patternsSkill
- apply-design-principlesSkill
- apply-solidSkill
- choose-data-structureSkill
- debug-systematicallySkill
- enforce-dependency-ruleSkill
- refactor-safelySkill
- slice-and-estimateSkill
- write-clean-testsSkill
- write-readable-codeSkill
- clean-frontend-scaffoldingSkill
- configure-accessibilitySkill
- configure-analyticsSkill
- configure-ciSkill
- configure-error-trackingSkill
- configure-lintingSkill
- configure-test-stackSkill
- configure-typescriptSkill
- create-moduleSkill
- optimize-performanceSkill
- scaffold-frontend-projectSkill
- set-up-authSkill
- set-up-design-systemSkill
- set-up-document-headSkill
- set-up-error-boundariesSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 3 are common, 0 are distinctive, and 10 are very specific to this project.
3
Common
Most of the 6 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 10
Use this skill to write, review, migrate, and debug Swift tests with modern Swift Testing APIs.
- Very specific: line 14
Prefer Swift Testing for Swift unit and integration tests, but keep XCTest for UI automation (XCUIApplication), performance metrics …
- Very specific: line 15
Treat #expect as the default assertion and use #require when subsequent lines depend on a prerequisite value.
- Very specific: line 16
Default to parallel-safe guidance.
- Very specific: line 17
Prefer traits for behavior and metadata (.enabled, .disabled, .timeLimit, .bug, tags) over naming conventions or ad-hoc comments.
- Very specific: line 19
Use @available on test functions for OS-gated behavior instead of runtime #available checks inside test bodies.
- Common: line 20
Keep migration advice incremental: convert assertions first, then organize suites, then introduce parameterization/traits.
- Very specific: line 21
Only import Testing in test targets, never in app/library/binary targets.
- Very specific: line 39
Test building blocks and suite organization -> references/fundamentals.md
- Very specific: line 43
Default parallel execution, .serialized, isolation strategy -> references/parallelization-and-isolation.md
- Very specific: line 44
Test speed, determinism, and flakiness prevention -> references/performance-and-best-practices.md
- Very specific: line 47
Test navigator/report workflows and diagnostics -> references/xcode-workflows.md
- Common: line 57
Test-plan include/exclude by names -> use tags and tag-based filters instead.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Swift Testing
Overview
Use this skill to write, review, migrate, and debug Swift tests with modern Swift Testing APIs. Prioritize readable tests, robust parallel execution, clear diagnostics, and incremental migration from XCTest where needed.
Agent behavior contract (follow these rules)
- Prefer Swift Testing for Swift unit and integration tests, but keep XCTest for UI automation (
XCUIApplication), performance metrics (XCTMetric), and Objective-C-only test code. - Treat
#expectas the default assertion and use#requirewhen subsequent lines depend on a prerequisite value. - Default to parallel-safe guidance. If tests are not isolated, first propose fixing shared state before applying
.serialized. - Prefer traits for behavior and metadata (
.enabled,.disabled,.timeLimit,.bug, tags) over naming conventions or ad-hoc comments. - Recommend parameterized tests when multiple tests share logic and differ only in input values.
- Use
@availableon test functions for OS-gated behavior instead of runtime#availablechecks inside test bodies; never annotate suite types with@available. - Keep migration advice incremental: convert assertions first, then organize suites, then introduce parameterization/traits.
- Only import
Testingin test targets, never in app/library/binary targets.
First 60 seconds (triage template)
- Clarify the goal: new tests, migration, flaky failures, performance, CI filtering, or async waiting.
- Collect minimal facts:
- Xcode/Swift version and platform targets
- Whether tests currently use XCTest, Swift Testing, or both
- Whether failures are deterministic or flaky
- Whether tests access shared resources (database, files, network, global state)
- Branch quickly:
- repetitive tests -> parameterized tests
- noisy or flaky failures -> known issue handling and test isolation
- migration questions -> XCTest mapping and coexistence strategy
- async callback complexity -> continuation/await patterns
Routing map (read the right reference fast)
- Test building blocks and suite organization ->
references/fundamentals.md #expect,#require, and throw expectations ->references/expectations.md- Traits, tags, and Xcode test-plan filtering ->
references/traits-and-tags.md - Parameterized test design and combinatorics ->
references/parameterized-testing.md - Default parallel execution,
.serialized, isolation strategy ->references/parallelization-and-isolation.md - Test speed, determinism, and flakiness prevention ->
references/performance-and-best-practices.md - Async waiting and callback bridging ->
references/async-testing-and-waiting.md - XCTest coexistence and migration workflow ->
references/migration-from-xctest.md - Test navigator/report workflows and diagnostics ->
references/xcode-workflows.md - Index and quick navigation ->
references/_index.md
Common pitfalls -> next best move
- Repetitive
testFooCaseA/testFooCaseB/...methods -> replace with one parameterized@Test(arguments:). - Failing optional preconditions hidden in later assertions ->
try #require(...)then assert on unwrapped value. - Flaky integration tests on shared database -> isolate dependencies or in-memory repositories; use
.serializedonly as a transition step. - Disabled tests that silently rot -> prefer
withKnownIssuefor temporary known failures to preserve signal. - Unclear failure values for complex types -> conform type to
CustomTestStringConvertiblefor focused test diagnostics. - Test-plan include/exclude by names -> use tags and tag-based filters instead.
Verification checklist
- Confirm each test has a single clear behavior and expressive display name when needed.
- Confirm prerequisites use
#requirewhere failure should stop the test. - Confirm repeated logic is parameterized instead of duplicated.
- Confirm tests are parallel-safe or intentionally serialized with rationale.
- Confirm async code is awaited and callback APIs are bridged safely.
- Confirm migration keeps unsupported XCTest-only scenarios on XCTest.
References
references/_index.mdreferences/fundamentals.mdreferences/expectations.mdreferences/traits-and-tags.mdreferences/parameterized-testing.mdreferences/parallelization-and-isolation.mdreferences/performance-and-best-practices.mdreferences/async-testing-and-waiting.mdreferences/migration-from-xctest.mdreferences/xcode-workflows.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

