What problem does it solve? macOS SwiftUI codebases often accumulate unnecessary AppKit bridges (NSViewRepresentable wrappers, NSStatusItem, NSOpenPanel) when a native SwiftUI API already covers the same case, adding maintenance liability, responder-chain edges, and Swift 6 isolation boundaries. This Skill audits a project to decide whether each bridge should exist at all. ## Core Features & Use Cases - Overuse detection: Flags seven defect classes (over-01 to over-07), from representables wrapping 1:1 native controls like NSButton or NSSwitch, to NSStatusItem where MenuBarExtra fits, to NSGlassEffectView where SwiftUI glass applies. - Justified escape-hatch confirmation: Confirms warranted bridges (rich-text NSTextView below macOS 26, NSOutlineView, behind-window NSVisualEffectView) with a status: justified record so they are not churned away by later refactors. - Hybrid lint engine: Runs tier-1 grep tells plus a tier-2 ast-grep structural rule that proves a makeNSView actually constructs a native control, emitting unified JSON and SARIF. - Use Case: Point it at a macOS SwiftUI project and receive per-bridge findings written to swiftui-audits/appkit-overuse/, each with the native SwiftUI replacement, a real GitHub permalink example, and a Sosumi doc citation. ## Quick Start Audit my macOS SwiftUI project for unnecessary AppKit bridges and report which ones native SwiftUI APIs can replace.
