neo-swift

Solid

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.

Code & Development 7 stars 2 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
30
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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 1. **Perceive (Version Awareness):** - Identify the Swift version (e.g., check `Package.swift` or build settings). - Determine the platform (SwiftUI vs UIKit, Server vs App). - Assess dependency management (Swift Package Manager, CocoaPods). 2. **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. 3. **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. 4. **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 `lowercamelCase` for members and `PascalCase` for types. ## Feature Roadmap (Swift 5.0 - 6+) ### Swift 5.0 - 5.4 (...

Details

Author
Benknightdark
Repository
Benknightdark/neo-skills
Created
6 months ago
Last Updated
today
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

neo-swift-ui

Use this skill when building, debugging, refactoring, or reviewing SwiftUI apps or views for iOS 16+ and related Apple platforms. Trigger for NavigationStack, Observation/state flow, view composition, previews, performance, accessibility, and SwiftUI architecture.

7 Updated today
Benknightdark
Code & Development Solid

neo-csharp

Use this skill when writing, reviewing, debugging, or modernizing C# code in .NET projects. Trigger for .cs/.csproj files, C# language-version questions, nullable reference types, records, pattern matching, async/cancellation, or version-appropriate syntax from C# 10+.

7 Updated today
Benknightdark
Code & Development Solid

swiftui-expert

This skill should be used when the user is building, reviewing, or debugging SwiftUI/Swift code for iOS, macOS, or visionOS apps. It detects the project's iOS and Swift version and covers MV architecture (no per-screen ViewModels by default), @Observable state, NavigationStack typed routes, view lifecycle, Approachable Concurrency, persistence (SwiftData / Core Data / SQLiteData / GRDB), design tokens, selective Liquid Glass adoption, iOS and macOS platform capabilities, accessibility, performance with Instruments SwiftUI, and Swift Testing. Trigger phrases include "review my SwiftUI code", "my @State isn't updating", "should I adopt Liquid Glass", "fix my Swift concurrency warning", "set up SwiftData", "what should App.swift own", "ObservableObject to @Observable", "should I use MVVM in SwiftUI", "do I need TCA", and "AppKit or SwiftUI for my Mac app". For driving/screenshotting a RUNNING app use the peekaboo validator; for dead-code hunts use the dead-code plugin.

11 Updated yesterday
johnkozaris