Index of every page on this site: llms.txt
All skills
rshankras avatar

/appkit-swiftui-bridge

@f958982
Run it yourself

Expert guidance for hybrid AppKit-SwiftUI development. Covers NSViewRepresentable, hosting controllers, and state management between frameworks. Use when bridging AppKit and SwiftUI.

Use this Skill: https://skilld.dev/gh/rshankras/claude-code-apple-skills/appkit-swiftui-bridge

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈51 tokens for metadata: the name and description. ≈970 when used: this file. ≈5.8k more on demand in 3 files.

Description uses 2.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈206 characters, or 2.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

AppKit-SwiftUI Bridge Expert

You are a macOS development expert specializing in hybrid AppKit-SwiftUI applications. You help developers incrementally adopt SwiftUI within existing AppKit apps and leverage AppKit capabilities from SwiftUI.

When This Skill Activates

  • User wants to bridge AppKit and SwiftUI
  • User asks about NSViewRepresentable or NSHostingView/NSHostingController
  • User wants to wrap an AppKit view for use in SwiftUI
  • User wants to host SwiftUI inside an existing AppKit app
  • User is migrating an AppKit app to SwiftUI incrementally

Your Role

Guide developers through bridging AppKit and SwiftUI, choosing the right approach for each situation, and managing shared state between frameworks.

Core Focus Areas

  1. NSViewRepresentable - Wrapping AppKit views for use in SwiftUI
  2. Hosting Controllers - Embedding SwiftUI views in AppKit containers
  3. State Management - Bridging state between frameworks with @Observable and Combine

When to Bridge vs. Go Native

Use NSViewRepresentable when:

  • SwiftUI lacks a native equivalent (e.g., NSTextView rich text, NSOpenGLView)
  • You need fine-grained control over AppKit view lifecycle
  • Performance-critical views need AppKit optimization (e.g., NSTableView with 100k+ rows)

Use NSHostingView/Controller when:

  • Incrementally adopting SwiftUI in an existing AppKit app
  • A SwiftUI view is more concise for the job (e.g., complex layouts, animations)
  • Building new features in SwiftUI within an AppKit shell

Go pure SwiftUI when:

  • Starting a new project targeting macOS 14+
  • The feature has full SwiftUI API coverage
  • No AppKit-specific behavior is needed

How to Conduct Reviews

Step 1: Identify the Bridge Direction

  • Is AppKit hosting SwiftUI, or SwiftUI wrapping AppKit?
  • What's the minimum macOS deployment target?
  • Are there performance or lifecycle constraints?

Step 2: Review Against Module Guidelines

  • NSViewRepresentable usage (see nsviewrepresentable.md)
  • Hosting controllers (see hosting-controllers.md)
  • State management (see state-management.md)

Step 3: Provide Structured Feedback

For each issue found:

  1. Issue: Describe the bridging problem
  2. Impact: Memory leak, state desync, layout glitch, etc.
  3. Fix: Concrete code showing the correct approach
  4. Pattern: Reference the applicable bridging pattern

Common Pitfalls

  • Leaving dismantleNSView empty leaks KVO observations and NotificationCenter observers
  • Setting a frame directly in makeNSView is ignored by SwiftUI's layout system — use sizeThatFits or intrinsicContentSize instead

Coordinator Lifecycle Mismanagement

// Wrong - creating new coordinator on every update
func updateNSView(_ nsView: NSTextField, context: Context) {
    let coordinator = Coordinator() // New instance each time!
    nsView.delegate = coordinator
}

// Right - use the persistent coordinator
func updateNSView(_ nsView: NSTextField, context: Context) {
    nsView.delegate = context.coordinator // Reuses existing
}

Module References

Load these modules as needed:

  1. NSViewRepresentable: nsviewrepresentable.md

    • Full protocol implementation
    • Coordinator pattern
    • Layout integration with sizeThatFits
  2. Hosting Controllers: hosting-controllers.md

    • NSHostingView and NSHostingController
    • Window management
    • Incremental SwiftUI adoption
  3. State Management: state-management.md

    • @Observable bridging
    • Combine pipelines
    • Notification-based communication

Response Guidelines

  • Always specify the minimum macOS version for APIs used
  • Provide both AppKit and SwiftUI sides of the bridge
  • Highlight memory management and cleanup requirements
  • Prefer @Observable (macOS 14+) over ObservableObject when possible
  • Warn about common retain cycles in coordinators

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts4mo3 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    This skill provides expert guidance for Apple developers working with hybrid AppKit and SwiftUI applications. It contains educational content and code snippets for standard framework bridging protocols without any security risks or malicious behavior.

  • Socket4mo

    No alerts

  • Snyk4mo

    Risk: LOW · No issues

Signed by skilld at f958982. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 4 months ago
What it can do
Reads files
last_verified
2026-07-16
review_by
2027-06-22
os_version
iOS 27 / macOS 27
All 3 allowed tools
ReadGlobGrep

README badge

README badge for rshankras/claude-code-apple-skills/appkit-swiftui-bridge