Menu
Find production patterns for complete macOS SwiftUI features such as menu bar apps, settings, windows, and AppKit bridges.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit macOS SwiftUI accessibility for correctness, current APIs, and production conventions. Use for that domain or as part of a full audit.
Audit macOS SwiftUI animation motion for correctness, current APIs, and production conventions. Use for that domain or as part of a full audit.
Audit macOS SwiftUI api currency for correctness, current APIs, and production conventions. Use for that domain or as part of a full audit.
Audit macOS SwiftUI appearance color for correctness, current APIs, and production conventions. Use for that domain or as part of a full audit.
Audit macOS SwiftUI appkit interop for correctness, current APIs, and production conventions. Use for that domain or as part of a full audit.
Audit macOS SwiftUI appkit overuse for correctness, current APIs, and production conventions. Use for that domain or as part of a full audit.
| name | macos-app-patterns |
| description | Find production patterns for complete macOS SwiftUI features such as menu bar apps, settings, windows, and AppKit bridges. |
| license | MIT |
Let <swiftui-plugin-root> be the absolute plugin directory two levels above this SKILL.md. Resolve that path before running commands or opening shared references. When these instructions say swiftui-ctx, invoke <swiftui-plugin-root>/scripts/swiftui-ctx; do not assume the command is on PATH.
For building a whole feature, not one call. Each recipe is a canonical template plus real examples from shipping
macOS apps, served by swiftui-ctx. (One API → swiftui-examples. Deprecated cleanup → swiftui-modernize.)
swiftui-ctx = <swiftui-plugin-root>/scripts/swiftui-ctx (or swiftui-ctx on PATH). It self-builds + self-locates the catalog.
Don't reconstruct a macOS pattern from memory (menu-bar lifecycle, Settings scene, NSViewRepresentable wiring are exactly where memory fails). Pull the recipe, then open a real example. Announce: "Using macos-app-patterns."
swiftui-ctx recipes — list the patterns (or go straight to the one you need).swiftui-ctx recipe <name> — the template skeleton + the APIs + real examples.swiftui-ctx file <example.id> --smart (or the printed file <permalink>) — read the real, compilable code.swiftui-ctx lookup <api> if unsure.| Recipe | Use for |
|---|---|
menubar-app | a status-bar/menu-bar app with a Settings window (MenuBarExtra + Settings) |
settings-screen / settings-form | a preferences window (TabView of panes) / a grouped Form of controls |
master-detail | sidebar + detail (NavigationSplitView) — the macOS standard |
window-scene | custom window config (hidden title bar, fixed size, level) |
observable-model | modern state: @Observable model owned by a view |
nsview-bridge | wrap an AppKit NSView/NSViewController (the hardest thing to get right) |
charts-bar | a Swift Charts bar chart with axes |
searchable-list | a list with a search field (+ scopes) |
command-palette | a ⌘K quick-open/command overlay |
draggable-reorder | reorderable rows (onMove / draggable+dropDestination(for:isEnabled:action:)) |
cached-async-image | remote image with placeholder (+ caching note) |
Full index with the APIs each pulls in → references/recipes.md.
3 not-found (bad recipe name) → swiftui-ctx recipes to list them. 5 no catalog → STOP, tell the user, don't fabricate.
| File | Read when |
|---|---|
references/recipes.md | You want the recipe index with the APIs each one composes. |