Install
$ agentstack add skill-benknightdark-neo-skills-neo-swift ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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).
- 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.
- 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](reference/coding-style.md)
- [Swift Anti-Patterns and Best Practices](reference/anti-patterns.md)
- [Modern Swift Patterns Guide](reference/patterns.md)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Benknightdark
- Source: Benknightdark/neo-skills
- License: MIT
- Homepage: https://neo-blog-iota.vercel.app/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.