AppkitPro

Reviews and guides AppKit and AppKit-SwiftUI interop code on macOS.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Kaleb-Rupe/aurora --skill appkitpro-kaleb-rupe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: AppkitPro
Source: https://github.com/Kaleb-Rupe/aurora/tree/main/claude/skills/AppkitPro
Command: npx skills add https://github.com/Kaleb-Rupe/aurora --skill appkitpro-kaleb-rupe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Most macOS defects live at the AppKit-SwiftUI seam: coordinate spaces that disagree under magnification, layout systems that fight, input routed to the wrong layer, and accessibility elements double-voiced or silent. This Skill applies best-practice rules while writing AppKit code and runs a structured review pass to catch genuine seam defects with concrete fixes. ## Core Features & Use Cases - Structured Review Pass: Runs a focus-area-driven review across magnification, hosting/bridging, performance, input routing, and accessibility, reporting findings by file with before/after fixes. - Writing-Time Guidance: Loads targeted references while you write NSScrollView canvases, NSHostingView chrome, or NSViewRepresentable interop so the seam is built correctly the first time. - Use Case: You are building a zoomable canvas of terminal cards with SwiftUI chrome hosted over a live NSView. Ask for a review and get prioritized findings on coordinate conversion, gesture-end snapshot capture, hit-test routing, and accessibility ownership. ## Quick Start Ask the assistant to review your NSScrollView canvas and NSHostingView bridging code for AppKit best practices and seam defects.

Frequently Asked Questions about AppkitPro

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

FAQPage Schema
How do I review AppKit and SwiftUI interop code on macOS?

Run the structured review pass, which checks the AppKit-SwiftUI seam across five areas: magnification, hosting, performance, input, and accessibility. Findings are reported by file with the rule name and a before/after fix, prioritized with seam defects first.

How do I zoom an NSScrollView without breaking coordinate math?

Use setMagnification(_:centeredAt:) exactly once per tick, clamped between minMagnification and maxMagnification, and never mutate magnification directly mid-gesture. Convert event locations into the flipped document view's coordinate space before doing zoom-center or hit math.

When should I use NSHostingView versus NSViewRepresentable?

Use NSHostingView when SwiftUI chrome lives inside an AppKit hierarchy, updating it by reassigning rootView. Use NSViewRepresentable when an AppKit view lives inside SwiftUI, keeping updateNSView idempotent and routing callbacks through the Coordinator.

Why does my hosted SwiftUI overlay steal clicks from the AppKit content?

The hosting view forwards hits by default. Subclass NSHostingView and override hitTest to return nil so the overlay stays transparent to input, letting the AppKit container own routing for drag zones, resize edges, and content clicks.

How do I keep a zoomable canvas performant with many live views?

Use detach-and-snapshot: cards offscreen or below a zoom threshold show a cheap bitmap with the live view removed from the hierarchy. Re-render at 1:1 backing scale only at gesture-end, and batch mode transitions in one CATransaction with actions disabled.

What are the limitations of this AppKit review approach?

It covers the AppKit layer and the AppKit-SwiftUI seam only; pure SwiftUI views belong to a SwiftUI-focused review, and actor or Sendable design belongs to a concurrency-focused one. It reports genuine defects with concrete fixes rather than style preferences.