/swift-core
Use when implementing Swift 6 fundamentals — concurrency, architecture, testing, i18n, or performance — across any Apple platform.
$ npx -y skills add fusengine/agents --skill swift-core --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/swift-core
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when implementing Swift 6 fundamentals — concurrency, architecture, testing, i18n, or performance — across any Apple platform.
SKILL.md
swift-core.SKILL.mdname: swift-core
description: Use when implementing Swift 6 fundamentals — concurrency, architecture, testing, i18n, or performance — across any Apple platform.
versions:
swift: 6.2
ios: 26
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, use `TeamCreate` to spawn 3 agents:
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
Read more
name: swift-core description: Use when implementing Swift 6 fundamentals — concurrency, architecture, testing, i18n, or performance — across any Apple platform. versions: swift: 6.2 ios: 26 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, use `TeamCreate` to spawn 3 agents:
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
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Other skills on fusengine-agents.
- /agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Open skill - /apex-methodology
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
Open skill - /brainstorming
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
Open skill - /challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).
Open skill - /code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
Open skill - /elicitation
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
Open skill

