swift-eng

Designs and reviews SwiftUI, iOS, macOS, and React Native apps with architecture and performance guidance.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/SkinnnyJay/simpill-utils --skill swift-eng-skinnnyjay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swift-eng
Source: https://github.com/SkinnnyJay/simpill-utils/tree/main/.claude/skills/swift-eng
Command: npx skills add https://github.com/SkinnnyJay/simpill-utils --skill swift-eng-skinnnyjay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building Apple platform apps requires balancing UX quality, accessibility, performance, and clean architecture, and teams often lack a senior-level reviewer to enforce these standards consistently across SwiftUI, UIKit, and React Native codebases. ## Core Features & Use Cases - Architecture Design: Produces layered, protocol-first architectures with typed interface contracts, component maps, and data flow diagrams for iOS and macOS features. - Code Review & Accessibility Audits: Reviews SwiftUI components for state management correctness, HIG compliance, Dynamic Type, contrast, and reduced motion support. - Performance Profiling: Guides Instruments tracing, signpost instrumentation, and regression hardening for launch time and interaction latency targets. - Use Case: Ask it to design a new offline-first feature for iOS 17, and receive a phased proposal covering view-model protocols, async/await concurrency boundaries, accessibility notes, and a measurement plan. ## Quick Start Ask the skill to design a specific feature for iOS or review an existing SwiftUI component for performance and accessibility issues.

Frequently Asked Questions about swift-eng

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a SwiftUI feature with clean architecture?▼

Structure the app in layers: SwiftUI views depend on view-model protocols, domain use cases stay pure Swift, and data clients sit behind protocols swapped via dependency injection. Keep state at the least-common ancestor using @State, @StateObject, and @Environment appropriately.

When should I use UIKit instead of SwiftUI?▼

Use SwiftUI by default for new UI. Choose UIKit or AppKit when a system component needs deeper control, performance or edge cases require it, or interoperability with existing code is necessary, keeping bridges thin and documented.

How do I profile SwiftUI performance issues in Xcode?▼

Capture Instruments traces for SwiftUI view updates and memory allocations, then add signposts with OSSignposter around hot paths to measure durations. Fix regressions and add benchmarks or tests where feasible to prevent recurrence.

Can I use React Native for macOS apps?▼

Yes, use react-native-macos, which is AppKit-backed, when the product needs shared React code across Apple platforms. Prefer the New Architecture with Fabric and Turbo Native Modules, keeping native boundaries typed and minimal.

How do I manage state correctly in SwiftUI?▼

Maintain a single source of truth and keep state at the least-common ancestor. Use @State for local view state, @Binding for child mutation, @StateObject for owned observable objects, and @Environment for shared dependencies.