Back to catalog
Human reviewedDevelopment

Skill dossier

swift-expert

Source declaration

Builds iOS/macOS/watchOS/tvOS applications, implements SwiftUI views and state management, designs protocol-oriented architectures, handles async/await concurrency, implements actors for thread safety, and debugs Swift-specific issues. 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, UIKit integration, Combine, or Vapor.

The author's original description, preserved in English. It describes intent, not verified performance.

Builds iOS/macOS/watchOS/tvOS applications, implements SwiftUI views and state management, designs protocol-oriented architectures, handles async/await concurrency, implements actors for thread safety, and debugs Swift-specific issues. 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, UIKit integration, Combine, or Vapor.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

Guides Swift development for Apple platforms and server-side Swift, favoring protocol-oriented design, async/await, actors and SwiftUI with @Observable.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Analyzes platform targets, dependencies and design patterns.
  • Designs protocol-first APIs with associated types.
  • Implements async/await code and isolates shared state in actors.
  • Runs swift build and swift test at defined checkpoints.

Limitations & scope

  • Assumes Swift 5.9+ features such as @Observable.
  • Build and test checkpoints need a local Swift toolchain, and Instruments profiling needs Xcode.
  • Code samples are illustrative and not verified here.

Relevant for

  • iOS and macOS app developers
  • Developers adopting Swift concurrency
  • Server-side Swift teams

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
44.9 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/swift-expert/references/async-concurrency.mdReference8.3 KB
skills/swift-expert/references/memory-performance.mdReference8.1 KB
skills/swift-expert/references/protocol-oriented.mdReference7.2 KB
skills/swift-expert/references/swiftui-patterns.mdReference6.6 KB
skills/swift-expert/references/testing-patterns.mdReference8.8 KB
skills/swift-expert/SKILL.mdInstruction5.9 KB

SKILL.md frontmatter

{
  "name": "swift-expert",
  "description": "Builds iOS/macOS/watchOS/tvOS applications, implements SwiftUI views and state management, designs protocol-oriented architectures, handles async/await concurrency, implements actors for thread safety, and debugs Swift-specific issues. 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, UIKit integration, Combine, or Vapor.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "language",
    "triggers": "Swift, SwiftUI, iOS development, macOS development, async/await Swift, Combine, UIKit, Vapor",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": ""
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyze architecture

    Identify platform targets, dependencies and design patterns.

  2. 02
    Action

    Implement type-safe code

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

  3. 03
    Decision

    Run validation checkpoints

    Run swift build, swift build -warnings-as-errors and swift test at the stated steps.

  4. 04
    Output

    Deliver Swift output

    Provide protocol definitions, model types, views, tests and a short architecture explanation.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

114 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Note

File modification is described or implemented

95 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 95 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

19 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 19 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Check generated code for force unwraps and network calls to placeholder URLs before building or shipping it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/swift-expert # .claude/skills/swift-expert
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/swift-expert/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Confirm SKILL.md is discoverable at the destination, then ask Claude Code to use swift-expert on a small task.

Prerequisites

  • Assumes Swift 5.9+ features such as @Observable.
  • Build and test checkpoints need a local Swift toolchain, and Instruments profiling needs Xcode.
  • Code samples are illustrative and not verified here.

Example prompts

Representative task

Use the swift-expert skill to build a SwiftUI screen backed by an @Observable view model that loads users through an async Repository protocol, with an actor-based image cache and XCTest coverage.

Inspect before use

Read the swift-expert skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/swift-expert/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Paired DO and DON'T code samples make preferred patterns clear.
  • Explicit validation checkpoints after implementation, optimization and testing.

Considerations

  • Strong opinions, such as avoiding class inheritance, may not fit legacy UIKit code.
  • Requires Apple tooling to run the recommended checks.
Research conclusion

A solid guide for modern Swift code when you work with the Swift 5.9+ toolchain.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/swift-expert
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.