vendor/skills/swift-testing-expert/SKILL.md
# Swift Testing Expert Use this skill when designing or reviewing modern Swift tests that should align with Swift Testing instead of legacy XCTest-only patterns. ## Focus areas - ✅ Prefer `import Testing` in unit and integration tests. - ✅ Use `#expect` and `#require` instead of `XCTAssert*` and `XCTUnwrap` in modern Swift tests. - ✅ Keep `XCTest` only for UI, performance, or unavoidable legacy compatibility targets. - ✅ Preserve repository-specific test contracts such as `makeSUT()` and memo
npx skillsauth add swiftenprofundidad/ast-intelligence-hooks vendor/skills/swift-testing-expertInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when designing or reviewing modern Swift tests that should align with Swift Testing instead of legacy XCTest-only patterns.
import Testing in unit and integration tests.#expect and #require instead of XCTAssert* and XCTUnwrap in modern Swift tests.XCTest only for UI, performance, or unavoidable legacy compatibility targets.makeSUT() and memory-leak tracking helpers when they are mandatory.@Test functions over test... methods when the target already supports Swift Testing.#expect(value == expected) over XCTAssertEqual(value, expected).let value = try #require(optionalValue) over let value = try XCTUnwrap(optionalValue).async and await.XCTAssert* in non-UI, non-performance tests that can use #expect.XCTUnwrap in tests that can use #require.development
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.
development
Expert guidance on Swift Concurrency best practices, patterns, and implementation. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) concurrent code architecture or performance optimization, (8) concurrency-related linter warnings (SwiftLint or similar; e.g. async_without_await, Sendable/actor isolation/MainActor lint).
tools
Reglas iOS/Swift/SwiftUI enterprise del proyecto. Alias canónico neutro.
development
Reglas frontend enterprise (React/Next.js/TypeScript) del proyecto. Alias canónico neutro.