Modern Swift
CheckedGenerates clean, modern Swift code snippets for SwiftUI views and related frontend tasks, optimized for performance.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add johnrogers/claude-swift-engineering --skill modern-swift -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
johnrogers
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned johnrogers/claude-swift-engineering at 1dc2cf4d02.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1dc2cf4d02
- Scanned
- 9 files, 1,212 lines
About this skill
What it does
This skill generates clean, modern Swift code snippets for SwiftUI views and related frontend tasks, optimized for performance using Swift 6.2+ features. It focuses on utilizing new concurrency patterns like async/await, @MainActor, and actor to replace older approaches (completion handlers, DispatchQueue, locks) and ensure compile-time safety against data races. The skill emphasizes leveraging these modern techniques for thread-safe code and efficient asynchronous operations.
When to use it
- When needing to convert existing completion handler based code to Swift's new
async/awaitsyntax. - For implementing UI updates that require execution on the main thread using
@MainActor. - When dealing with shared mutable state, replacing locks or serial queues with actors for safer concurrency.
- To run multiple asynchronous operations in parallel utilizing
TaskGroup. - When migrating legacy code to incorporate modern Swift attributes like
@preconcurrencyand@backDeployed.
Key capabilities
- Generates code using
async/awaitfor asynchronous operations. - Utilizes
@MainActorfor UI updates on the main thread. - Employs
actorfor managing shared mutable state safely. - Supports the use of
TaskGroupfor parallel task execution. - Provides guidance on implementing task cancellation with
Task.isCancelledandTask.checkCancellation().
Example prompts
- "Generate a SwiftUI view that fetches data asynchronously using
async/await." - "Show me how to update a UI element safely using
@MainActor." - "How do I use an actor to manage shared state in Swift?"
Tips & gotchas
- Reference Loading: Always load reference files, especially when dealing with concurrency patterns. This ensures the skill has access to necessary context and best practices.
- Avoid
@unchecked Sendable: Using this as a quick fix silences compiler errors but can mask potential data races; address the underlying issue instead. - Task Cancellation is Crucial: Remember to check
Task.isCancelledor callTask.checkCancellation()within loops for long-running operations to ensure cancellation signals are processed correctly.