neo-swift
Skill7 starsChanged 6 months agoMITView on GitHub
Use this skill when writing, reviewing, debugging, or modernizing Swift code for iOS, macOS, server-side Swift, or shared packages. Trigger for Swift 5+ language features, structured concurrency, memory safety, protocols/generics, SwiftUI integration, and performance-sensitive code.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- generate-skillSkill
- neo-azure-pipelinesSkill
- neo-clarificationSkill
- neo-clean-architectureSkill
- neo-code-reviewSkill
- neo-csharp-interface-generatorSkill
- neo-csharpSkill
- neo-dotnet-ef-coreSkill
- neo-dotnet-minimal-apisSkill
- neo-dotnet-mvcSkill
- neo-dotnetSkill
- neo-dotnet-tag-helperSkill
- neo-dotnet-webapiSkill
- neo-harness-projectSkill
- neo-harnessSkill
- neo-javascriptSkill
- neo-opentelemetrySkill
- neo-prSkill
- neo-python-managerSkill
- neo-pythonSkill
- neo-rabbitmqSkill
- neo-rustSkill
- neo-stop-slopSkill
- neo-sub-agentSkill
- neo-swift-uiSkill
- neo-typescriptSkill
- neo-vueSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Write swifty, concise code following Apple's API Design Guidelines.
- Distinctive: line 36
Check for memory leaks (retain cycles) using capture lists.
- Distinctive: line 37
Verify Swift 6 concurrency safety (data race detection).
- Very specific: line 38
Ensure naming conventions follow the standard lowercamelCase for members and PascalCase for types.
- Distinctive: line 60
Conciseness: Use trailing closures and shorthand argument names where appropriate.
- Very specific: line 61
Safety: Prefer if let or guard let over force unwrapping (!).
- Very specific: line 62
Purity: Prefer struct (Value Types) over class (Reference Types) for data models.
- Very specific: line 63
Concurrency: Avoid Thread.sleep or legacy completion handlers.
- Distinctive: line 71
Ensure code compiles without warnings in the target Swift version.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Modern Swift (5.0+) Expert Skill
Trigger On
- The user asks to write, debug, refactor, or review Swift code.
- The project directory contains
*.swift,Package.swift, or*.xcodeproj. - Development involves iOS (SwiftUI/UIKit), macOS, or Server-side Swift (Vapor).
- Code modernization is needed (e.g., migrating to Structured Concurrency or Swift 6 language mode).
Workflow
- Perceive (Version Awareness):
- Identify the Swift version (e.g., check
Package.swiftor build settings). - Determine the platform (SwiftUI vs UIKit, Server vs App).
- Assess dependency management (Swift Package Manager, CocoaPods).
- Identify the Swift version (e.g., check
- Reason (Planning Phase):
- Evaluate the use of modern syntax (e.g.,
async/await,Result,@propertyWrapper). - Decide on memory management strategies (ARC,
weak/unowned). - For UI tasks, prioritize SwiftUI for modern apps or UIKit for legacy support.
- Evaluate the use of modern syntax (e.g.,
- Act (Execution Phase):
- Write swifty, concise code following Apple's API Design Guidelines.
- Implement type-safe and protocol-oriented solutions.
- Leverage Structured Concurrency (
Task,async let) for asynchronous operations.
- Validate (Standard Validation):
- Check for memory leaks (retain cycles) using capture lists.
- Verify Swift 6 concurrency safety (data race detection).
- Ensure naming conventions follow the standard
lowercamelCasefor members andPascalCasefor types.
Feature Roadmap (Swift 5.0 - 6+)
Swift 5.0 - 5.4 (Foundation)
- Result Type: Standardized error handling.
- Property Wrappers: Encapsulating property logic (e.g.,
@Published). - Opaque Types: Hiding implementation details (
some View). - Result Builders: DSL support for SwiftUI.
Swift 5.5 - 5.10 (Modern Concurrency)
- Async/Await: Linear asynchronous code.
- Actors: Thread-safe state isolation.
- Distributed Actors: Communicating across processes.
- Non-copyable Types: Explicit control over object ownership.
Swift 6+ (Safety & Performance)
- Full Data Isolation: Compile-time data race prevention.
- Typed Throws: Explicitly defining error types.
- Embedded Swift: Running Swift on restricted environments.
Coding Standards
- Conciseness: Use trailing closures and shorthand argument names where appropriate.
- Safety: Prefer
if letorguard letover force unwrapping (!). - Purity: Prefer
struct(Value Types) overclass(Reference Types) for data models. - Concurrency: Avoid
Thread.sleepor legacy completion handlers; use structured concurrency.
Deliver
- Version-Optimized Code: Provide code using the best features of the target Swift version.
- SwiftUI/UIKit Insights: Recommend patterns based on the UI framework used.
- Concurrency Migration: Provide strategies for moving to Swift 6 strict concurrency checks.
Validate
- Ensure code compiles without warnings in the target Swift version.
- Validate that closure capture lists correctly handle object lifecycles.
- Confirm that error handling uses the
do-catchorthrowspatterns correctly.
Documentation
Official References
Internal References
- Swift Coding Style and Naming Conventions
- Swift Anti-Patterns and Best Practices
- Modern Swift Patterns Guide
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
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.

