Help us improve
Share bugs, ideas, or general feedback.
From Build Swift Apps
Decides when and how to bridge SwiftUI into AppKit for macOS apps. Provides patterns for NSViewRepresentable, NSViewControllerRepresentable, window access, responder chain, panels, and menus.
npx claudepluginhub xopoko/build-swift-apps --plugin build-swift-appsHow this skill is triggered — by the user, by Claude, or both
Slash command
/build-swift-apps:macos-appkit-bridgeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when SwiftUI is close but not quite enough for native macOS behavior.
Guides building macOS SwiftUI apps with proper scene architecture, state ownership, and desktop UI patterns.
Bridges UIKit and SwiftUI via UIViewRepresentable, UIViewControllerRepresentable, and UIHostingController. Use for camera, maps, mail compose, document scanning, PDF rendering, text views, or migrating UIKit apps.
SwiftUI fundamentals for all Apple platforms. Use when building views, navigation, data persistence, or state management with SwiftUI across iOS, macOS, iPadOS, watchOS, visionOS.
Share bugs, ideas, or general feedback.
Use this skill when SwiftUI is close but not quite enough for native macOS behavior. Keep the bridge as small and explicit as possible. SwiftUI should usually remain the source of truth, while AppKit handles the imperative edge.
NSViewRepresentable when you need a specific AppKit view with lightweight lifecycle needs.NSViewControllerRepresentable when you need controller lifecycle, delegation, or presentation coordination.NSWindow, responder-chain, menu validation, panels, or app-level behavior.Name the capability gap precisely.
Pick the smallest boundary that solves it.
Keep ownership explicit.
Expose a narrow interface back to SwiftUI.
Validate lifecycle assumptions.
references/representables.md: choosing between view and view-controller wrappers, plus coordinator patterns.references/window-panels.md: window access, utility windows, and open/save panels.references/responder-menus.md: first responder, command routing, and menu validation.references/drag-drop-pasteboard.md: pasteboard, file URLs, and desktop drag/drop edges.Coordinator become an unstructured dumping ground.NSView or NSWindow instances globally without a strong ownership reason.macos-swiftui-architect, keep it there.Provide: