/macos-appkit-bridge
Decide when and how to bridge a macOS app from SwiftUI into AppKit. Use when implementing NSViewRepresentable or NSViewControllerRepresentable, accessing NSWindow or the responder chain, presenting panels, customizing menus, or handling desktop behaviors that SwiftUI does not
$ npx -y skills add Xopoko/plug-n-skills --skill macos-appkit-bridge --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/macos-appkit-bridge
Context preview
The summary Claude sees to decide when to auto-load this skill.
Decide when and how to bridge a macOS app from SwiftUI into AppKit. Use when implementing NSViewRepresentable or NSViewControllerRepresentable, accessing NSWindow or the responder chain, presenting panels, customizing menus, or handling desktop behaviors that SwiftUI does not
Ready-to-install skills and plugins that make coding agents better at real development work. Plug'n Skills is a library of plugin packs for Codex, Claude Code, Cursor, and other coding agents.
Repo: Xopoko/plug-n-skills
Other skills on plug-n-skills.
- /architecture-conformance
Use when intended architecture must be compared with implementation: dependency policies, ADRs, ownership rules, drift, erosion, recovered models, and conformance classifications.
Open skill - /architecture-decisions
Use when structural code choices need durable rationale: ADRs, tradeoffs, consequences, reversibility, ownership, review triggers, and validation plans.
Open skill - /architecture-fitness-functions
Use when architecture choices need executable guardrails: dependency rules, cycle checks, boundary tests, ownership review gates, ADR compliance, runtime/resilience checks, and CI fitness functions.
Open skill - /architecture-intelligence
Use whenever code work has structural consequences: project architecture, module boundaries, dependency direction, runtime topology, asynchronous state consistency, ownership, ADRs, fitness functions, or architecture refactoring.
Open skill - /architecture-ownership-topology
Use when architecture crosses ownership or review boundaries: CODEOWNERS/OWNERS, module coverage, cross-owned dependencies, socio-technical coordination, and governance paths.
Open skill - /architecture-refactoring-strategy
Use when code changes need staged structural design: boundary extraction, modularization, dependency inversion, migrations, anti-corruption layers, tests, rollout gates, and rollback.
Open skill