macos-patterns

Guidance for building Mac apps with standard window layouts, menu-bar commands, keyboard shortcuts, and settings screens.

In plain words
What is it for?
Use it when designing SwiftUI Mac app windows, document-based apps, utility windows, menu actions, shortcuts, or preferences.
Why use it?
It explains how Mac-specific parts of an app fit together, including how menu commands can use the currently focused view's state.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/abdullah4ai/apple-developer-toolkit/macos-patterns
Any agent
npx skills add Abdullah4AI/apple-developer-toolkit --skill macos-patterns
Clone the repo
git clone --depth 1 https://github.com/Abdullah4AI/apple-developer-toolkit

Made for: Claude Code, Codex.

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,702 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00068 $0.01702
Opus 5 $0.00034 $0.00851
Sonnet 5 $0.00014 $0.00340
Haiku 4.5 $0.00007 $0.00170

Measured 2d ago against content hash 47132caab8aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

macos-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

swiftship/internal/skills/data/always-macos/macos-patterns/SKILL.md · 245 lines

How it starts

The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.

macOS Platform Patterns

Window Management

Three scene types for Mac apps:

@main
struct MyApp: App {
    var body: some Scene {
        // Main window — users can open multiple instances
        WindowGroup {
            ContentView()
        }
        .defaultSize(width: 900, height: 600)

        // Single utility window
        Window("Inspector", id: "inspector") {
            InspectorView()
        }
        .defaultSize(width: 300, height: 400)

        // Document-based app
        DocumentGroup(newDocument: MyDocument()) { file in
            DocumentEditor(document: file.$document)
        }
    }
}

CommandMenu closures run at the App scene level — outside the view hierarchy. They CANNOT access view @State directly. Use @FocusedValue to bridge view state to menu actions.

// 1. Define a FocusedValue key using @Entry
extension FocusedValues {
    @Entry var activeDocument: DocumentViewModel?
}

// 2. ViewModel — @Observable only (NOT ObservableObject)
@Observable @MainActor
class DocumentViewModel {
    var content = ""
    func save() { /* persist */ }
    func togglePreview() { /* toggle */ }
}

// 3. Publish from active view using .focusedValue()
struct DocumentView: View {
    @State var viewModel = DocumentViewModel()
    var body: some View {
        EditorContent(viewModel: viewModel)
            .focusedValue(\.activeDocument, viewModel)  // REQUIRED — publish to menu bar
    }
}

// 4. Consume in App via @FocusedValue and wire ALL menu actions
@main
struct MyApp: App {
    @FocusedValue(\.activeDocument) private var document

    var body: some Scene {
        WindowGroup { DocumentView() }

        CommandMenu("Document") {
            Button("Save") { document?.save() }
                .keyboardShortcut("s", modifiers: .command)
                .disabled(document == nil)
            Button("Toggle Preview") { document?.togglePreview() }
                .keyboardShortcut("p", modifiers: [.command, .option])
                .disabled(document == nil)
        }

        CommandGroup(replacing: .newItem) {
            Button("New Document") { document?.createNew() }
                .keyboardShortcut("n", modifiers: .command)
                .disabled(document == nil)
        }
    }
}

Read the full file on GitHub · 245 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 245 lines · 68 tokens per session scan A 47132caab8aa

Subscribe to this mod's changes

macos-patterns is a skill published in the GitHub repository Abdullah4AI/apple-developer-toolkit (10 stars, last pushed 5d ago), licensed MIT. It adds 68 tokens to every session and 1,702 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens