macos-development

Guides macOS app development with SwiftUI, AppKit, SwiftData, and macOS 26 Tahoe APIs.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/RavitejaKarra24/dotfiles --skill macos-development-ravitejakarra24
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: macos-development
Source: https://github.com/RavitejaKarra24/dotfiles/tree/main/agents/.agents/skills/macos-development
Command: npx skills add https://github.com/RavitejaKarra24/dotfiles --skill macos-development-ravitejakarra24

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building native macOS apps requires navigating SwiftUI, AppKit, SwiftData, sandboxing, and fast-changing macOS 26 (Tahoe) APIs; this Skill consolidates expert guidance, code review checklists, and architecture patterns into one place. ## Core Features & Use Cases - Code Review: Reviews Swift 6+ code against SOLID principles, modern concurrency (async/await, actors, Sendable), and SwiftData best practices with prioritized feedback. - Architecture & Planning: Guides MVVM, repository, and modular SPM design, and generates planning documents for new apps or audits of existing projects. - Platform Features: Covers macOS 26 Tahoe APIs (FoundationModels, MLX, Continuity), sandboxing entitlements, menu bar apps, background execution, and AppKit-SwiftUI bridging. - UI/UX Review: Audits interfaces against Liquid Glass design, macOS HIG, and accessibility standards (VoiceOver, keyboard navigation, Dynamic Type). - Use Case: Ask for a review of your SwiftData schema and query performance, and receive concrete fixes for unique constraints, fetch limits, and background ModelContext usage. ## Quick Start Ask the assistant to review your macOS app's SwiftUI code for macOS 26 Tahoe HIG compliance and SwiftData best practices.

Frequently Asked Questions about macos-development

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

FAQPage Schema
How do I review Swift code for macOS best practices?

Request a code review and the skill checks Swift 6+ idioms, SOLID principles, concurrency safety with Sendable and MainActor, and SwiftData usage. Feedback is structured as critical, important, and nice-to-have issues with concrete fix examples.

Should I use SwiftData or Core Data for a new macOS app?

SwiftData is recommended for new projects targeting macOS 14 or later, using @Model classes, @Query in views, and FetchDescriptor in services. Core Data remains an option for legacy requirements or specific migration constraints.

How do I bridge AppKit and SwiftUI in one macOS app?

Use NSViewRepresentable to wrap AppKit views inside SwiftUI, and NSHostingView or NSHostingController to embed SwiftUI in AppKit. The skill covers coordinator lifecycle, state bridging with @Observable, and common pitfalls like leaking observers in dismantleNSView.

Does Apple Intelligence work on all Macs running macOS 26?

No, the FoundationModels framework requires Apple silicon; Intel Macs report deviceNotEligible. Always check SystemLanguageModel availability at launch and handle cases where the user has not enabled Apple Intelligence in System Settings.

What entitlements does a sandboxed macOS app need for file access?

Sandboxed apps need com.apple.security.files.user-selected.read-write for user-picked files and com.apple.security.files.bookmarks.app-scope to persist access via security-scoped bookmarks. Sandboxing is mandatory for Mac App Store distribution.

When should I not use SwiftUI for a macOS UI component?

Stay with AppKit for performance-critical views like NSTableView with very large datasets, rich text editing via NSTextView, or features lacking SwiftUI equivalents. Profile with Instruments before assuming SwiftUI List performance is insufficient.