appkit-interop

To access NSWindow from SwiftUI, you need an AppKit bridge that exposes native window controls SwiftUI lacks. This skill scaffolds a minimal boundary to retrieve and manipulate NSWindow instances while keeping SwiftUI ownership explicit.

AppKit menu validation requires responder-chain integration SwiftUI does not natively expose. This skill provides a lightweight bridge object to coordinate responder-chain actions and validate menu items across mixed SwiftUI and AppKit code.

Presenting AppKit panels from SwiftUI requires a well-scoped bridge handling cross-boundary presentation workflows. This skill coordinates lifecycle and data flow so you can trigger native panel presentations without leaking AppKit complexity into SwiftUI.

Yes, you can maintain a thin boundary between SwiftUI and AppKit by enforcing explicit SwiftUI ownership and using a bridge object for lifecycle coordination. This skill ensures AppKit complexity stays scoped to the bridge without leaking into SwiftUI views.

You need to bridge SwiftUI to AppKit when your macOS app requires native behaviors like NSWindow access, panel presentation, or responder-chain menu validation that SwiftUI cannot provide. It targets edge-case functionality in mixed-code apps.