Use when implementing Swift 6 fundamentals — concurrency, architecture, testing, i18n, or performance — across any Apple platform.
Pro scans all 6 files and shows the line behind each finding
Scanned 9/29/2026
npx -y skills add fusengine/agents --skill swift-core --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Swift Core?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/fusengine-swift-core)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: swift-core
description: Use when implementing Swift 6 fundamentals — concurrency, architecture, testing, i18n, or performance — across any Apple platform.
versions:
swift: 6.4
ios: 27
user-invocable: false
references: references/concurrency.md, references/architecture.md, references/testing.md, references/i18n.md, references/performance.md
related-skills: swiftui-core, solid-swift, ios, macos, ipados, watchos, visionos
---
<objective>
Covers Swift 6 language and platform fundamentals shared across iOS, macOS, iPadOS, watchOS, and visionOS: async/await and actors with strict concurrency checking, Sendable typing, app architecture (MVVM with @Observable as the recommended default, Clean Architecture for complex apps), async testing with XCTest, String Catalog-based localization, and performance profiling with Instruments.
References cover each area in depth: concurrency, architecture/DI, testing, i18n, and performance.
Best practices: prefer actors over classes with locks for shared state, @Observable over ObservableObject, structured concurrency over completion handlers, String Catalogs for all user-facing text, profiling in Release (-O) builds, and value types (structs) over classes where possible.
</objective>
# Swift Core
Swift 6 fundamentals shared across all Apple platforms.
## Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one `Agent` call each with a `name`:
1. **fuse-ai-pilot:explore-codebase** - Analyze existing Swift patterns
2. **fuse-ai-pilot:research-expert** - Verify latest Swift 6 docs via Context7/Exa
3. **mcp__apple-docs__search_apple_docs** - Check Swift concurrency patterns
After implementation, run **fuse-ai-pilot:sniper** for validation.
---
## Overview
### When to Use
- Implementing async/await, actors, Sendable
- Designing app architecture (MVVM, Clean Architecture)
- Writing async tests with XCTest
- Localizing with String Catalogs
- Profiling with Instruments
### Why Swift Core
| Feature | Benefit |
|---------|---------|
| Actors | Thread-safe shared state without locks |
| @Observable | Simple reactive state (replaces ObservableObject) |
| String Catalogs | Automatic localization with Xcode 15+ |
| Instruments | Built-in performance profiling |
---
## Key Concepts
### Concurrency (Swift 6)
Modern async/await with strict concurrency checking. Actors provide thread-safe state, Sendable marks safe types.
### Architecture
MVVM with @Observable is the recommended pattern. Clean Architecture for complex apps with domain separation.
### Testing
XCTest with native async/await support. No need for expectations with async tests.
### Internationalization
String Catalogs are mandatory. All user-facing text must be localized.
### Performance
Profile with Instruments. Use lazy loading, avoid heavy work in view body.
---
## Reference Guide
| Need | Reference |
|------|-----------|
| Async/await, actors, Sendable | [concurrency.md](references/concurrency.md) |
| MVVM, Clean Architecture, DI | [architecture.md](references/architecture.md) |
| XCTest, async tests, mocking | [testing.md](references/testing.md) |
| String Catalogs, localization | [i18n.md](references/i18n.md) |
| Instruments, optimization | [performance.md](references/performance.md) |
---
## Best Practices
1. **Actors for shared state** - Prefer actors over classes with locks
2. **@Observable over ObservableObject** - Simpler, better performance
3. **Structured concurrency** - async/await, no completion handlers
4. **String Catalogs** - ALL user-facing text must be localized
5. **Profile in Release** - Always profile with `-O` optimization
6. **Value types** - Prefer structs over classes
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!