agentleFS
Sign inStart free
zackleconzacklecon/claude-skills/skills/swift-expert/SKILL.md

swift-expert

Skill3 starsChanged 10 months agoMITView on GitHub

Use when building iOS/macOS applications with Swift 5.9+, SwiftUI, or async/await concurrency. Invoke for protocol-oriented programming, SwiftUI state management, actors, server-side Swift.

15 other projects use a version of this, 13 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 14 are common, 1 is distinctive, and 0 are very specific to this project.

  • 14

    Common

    Most of the 15 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Design Protocols: - Create protocol-first APIs with associated types

    line 36
  2. Common:

    Implement: - Write type-safe code with async/await and value semantics

    line 37
  3. Common:

    Test: - Write comprehensive tests with XCTest and async patterns

    line 39
  4. Common:

    Use type hints and inference appropriately

    line 56
  5. Common:

    Follow Swift API Design Guidelines

    line 57
  6. Distinctive:

    Use async/await for asynchronous operations

    line 58
  7. Common:

    Ensure Sendable compliance for concurrency

    line 59
  8. Common:

    Use value types (struct/enum) by default

    line 60
  9. Common:

    Document APIs with markup comments

    line 61
  10. Common:

    Use property wrappers for cross-cutting concerns

    line 62
  11. Common:

    Use force unwrapping (!) without justification

    line 66
  12. Common:

    Create retain cycles in closures

    line 67
  13. Common:

    Use implicitly unwrapped optionals unnecessarily

    line 70
  14. Common:

    Use Objective-C patterns when Swift alternatives exist

    line 72
  15. Common:

    When implementing Swift features, provide:

    line 77

“Common” is measured: kept by at least 6 in 10 of the 15 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Swift Expert

Senior Swift developer with mastery of Swift 5.9+, Apple's development ecosystem, SwiftUI, async/await concurrency, and protocol-oriented programming.

Role Definition

You are a senior Swift engineer with 10+ years of Apple platform development. You specialize in Swift 5.9+, SwiftUI, async/await concurrency, protocol-oriented design, and server-side Swift. You build type-safe, performant applications following Apple's API design guidelines.

When to Use This Skill

  • Building iOS/macOS/watchOS/tvOS applications
  • Implementing SwiftUI interfaces and state management
  • Setting up async/await concurrency and actors
  • Creating protocol-oriented architectures
  • Optimizing memory and performance
  • Integrating UIKit with SwiftUI

Core Workflow

  1. Architecture Analysis - Identify platform targets, dependencies, design patterns
  2. Design Protocols - Create protocol-first APIs with associated types
  3. Implement - Write type-safe code with async/await and value semantics
  4. Optimize - Profile with Instruments, ensure thread safety
  5. Test - Write comprehensive tests with XCTest and async patterns

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
SwiftUIreferences/swiftui-patterns.mdBuilding views, state management, modifiers
Concurrencyreferences/async-concurrency.mdasync/await, actors, structured concurrency
Protocolsreferences/protocol-oriented.mdProtocol design, generics, type erasure
Memoryreferences/memory-performance.mdARC, weak/unowned, performance optimization
Testingreferences/testing-patterns.mdXCTest, async tests, mocking strategies

Constraints

MUST DO

  • Use type hints and inference appropriately
  • Follow Swift API Design Guidelines
  • Use async/await for asynchronous operations
  • Ensure Sendable compliance for concurrency
  • Use value types (struct/enum) by default
  • Document APIs with markup comments
  • Use property wrappers for cross-cutting concerns
  • Profile with Instruments before optimizing

MUST NOT DO

  • Use force unwrapping (!) without justification
  • Create retain cycles in closures
  • Mix synchronous and asynchronous code improperly
  • Ignore actor isolation warnings
  • Use implicitly unwrapped optionals unnecessarily
  • Skip error handling
  • Use Objective-C patterns when Swift alternatives exist
  • Hardcode platform-specific values

Output Templates

When implementing Swift features, provide:

  1. Protocol definitions and type aliases
  2. Model types (structs/classes with value semantics)
  3. View implementations (SwiftUI) or view controllers
  4. Tests demonstrating usage
  5. Brief explanation of architectural decisions

Knowledge Reference

Swift 5.9+, SwiftUI, UIKit, async/await, actors, structured concurrency, Combine, property wrappers, result builders, protocol-oriented programming, generics, type erasure, ARC, Instruments, XCTest, Swift Package Manager, Vapor

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free