appkit-app-architecture-workflowlisted

# AppKit App Architecture Workflow ## Purpose Provide a docs-first workflow for AppKit app-structure decisions in macOS apps. This skill owns ownership-boundary guidance for AppKit lifetimes, menu bar apps, menus, responder-chain action routing, windows, controllers, restoration, archiving, AppKit MVC, Observation interop, and mixed AppKit/SwiftUI composition. It is not the Apple-docs router, not the SwiftUI architecture workflow, not the accessibility workflow, and not the Xcode execution workflow. For Xcode app source layout, keep UIKit/AppKit controller support view-adjacent: `Sources/Views/Shared`, `Sources/Views/macOS`, and `Sources/Views/iOS` own view surfaces, and controller support files use concatenated prefixed names such as `GEAWhateverViewController.swift` beside their matching view. Do not collect ordinary app controller support in a root `Controllers/` directory. ## When To Use - Use this skill when the user wants help structuring an AppKit or mixed AppKit/SwiftUI macOS app. - Use this skill when the question involves `NSApplication`, `NSApplicationDelegate`, app activation policy, app reopen behavior, menu bar apps, `NSStatusItem`, status menus, popovers, panels, or quit behavior. - Use this skill when the question involves the main menu, contextual menus, toolbar actions, target/action, responder-chain action routing, or menu validation. - Use this skill when deciding whether app-level, window-level, controller-level, document-level, model-le