Agent Skills
› fanfan-de/anybox
› appkit-interop
appkit-interop
GitHub指导在 macOS 开发中，当 SwiftUI 无法满足原生行为时，如何构建最小化的 AppKit 桥接。涵盖 Representables、窗口面板及响应链处理，强调保持 SwiftUI 为数据源并明确生命周期边界。
Trigger Scenarios
实现 SwiftUI 与 AppKit 互操作的 Representable
需要访问 NSWindow 或弹出面板
处理菜单栏验证或第一响应者链
Install
npx skills add fanfan-de/anybox --skill appkit-interop -g -y
SKILL.md
Frontmatter
{
"name": "appkit-interop",
"description": "Bridge macOS SwiftUI into AppKit narrowly. Use when implementing representables, reaching NSWindow or panels, handling menus, or using the responder chain."
}
AppKit Interop
Quick Start
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.
Choose The Smallest Bridge
- Use pure SwiftUI when the required behavior already exists in scenes, toolbars, commands, inspectors, or standard controls.
- Use
NSViewRepresentablewhen you need a specific AppKit view with lightweight lifecycle needs. - Use
NSViewControllerRepresentablewhen you need controller lifecycle, delegation, or presentation coordination. - Use direct AppKit window or app hooks when you need
NSWindow, responder-chain, menu validation, panels, or app-level behavior.
Workflow
-
Name the capability gap precisely.
- Window behavior
- Text system behavior
- Menu validation
- Drag and drop
- File open/save panels
- First responder control
-
Pick the smallest boundary that solves it.
- Avoid porting a whole screen to AppKit when one wrapped control or coordinator would do.
-
Keep ownership explicit.
- SwiftUI owns value state, selection, and observable models.
- AppKit objects stay inside the representable, coordinator, or bridge object.
-
Expose a narrow interface back to SwiftUI.
- Bindings for editable state
- Small callbacks for events
- Focused bridge services only when necessary
-
Validate lifecycle assumptions.
- SwiftUI may recreate representables.
- Coordinators exist to hold delegate and target-action glue, not as a second app architecture.
References
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.
Guardrails
- Do not duplicate the source of truth between SwiftUI and AppKit.
- Do not let
Coordinatorbecome an unstructured dumping ground. - Do not store long-lived
NSVieworNSWindowinstances globally without a strong ownership reason. - Prefer a tiny tested bridge over rewriting the feature in raw AppKit.
- If a pattern can remain entirely in
swiftui-patterns, keep it there.
Output Expectations
Provide:
- the exact SwiftUI limitation being crossed
- the smallest recommended bridge type
- the data-flow boundary between SwiftUI and AppKit
- the lifecycle or validation risks to watch
Version History
- 08dc189 Current 2026-07-05 18:55
