axiom-macos

Other Community

Repo stars 0
Author updated Aug 25, 2026, 02:29 AM
Author repo Axiom

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Use when building ANY macOS app — windows, menus, sandboxing, distribution, AppKit bridging or modernization (control events, st…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Quick Reference”, “Cross-Suite Routes”, “Conflict Resolution”, “Decision Tree”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name axiom-macos directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Quick Reference / Cross-Suite Routes / Conflict Resolution” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

macOS Development

You MUST use this skill for ANY macOS-specific development including windows, menus, sandboxing, distribution, AppKit bridging, and macOS SwiftUI differences.

Quick Reference

Symptom / Task	Reference
Window management (WindowGroup, Window, MenuBarExtra, DocumentGroup)	See `skills/windows.md`
Menu bar, commands, keyboard shortcuts	See `skills/menus-and-commands.md`
Table, Inspector, NavigationSplitView, focus	See `skills/swiftui-differences.md`
App Sandbox, file access, security-scoped bookmarks	See `skills/sandbox-and-file-access.md`
Developer ID, notarization, Sparkle auto-updates	See `skills/direct-distribution.md`
NSViewRepresentable, NSHostingController, AppKit bridging, @Observable in AppKit, NSHostingMenu, SwiftUI scenes from AppKit	See `skills/appkit-interop.md`
Modernizing AppKit: mouseDown replacement, control events, status-item sessions, state restoration, concentric corners, touch (`OS27`)	See `skills/appkit-modernization.md`
Screen recording, sharing, or capture (ScreenCaptureKit)	See `skills/screencapturekit.md`
SCStream / SCContentFilter / screenshots / file recording API	See `skills/screencapturekit-ref.md`
Bring an iOS app to Mac: Catalyst adoption, Designed for iPad, Mac availability opt-out	See `skills/ios-apps-on-mac.md`
Apple Pay on Mac / Catalyst	See `axiom-payments/skills/apple-pay.md` (Catalyst section)

Cross-Suite Routes

These topics overlap with macOS development but live in separate suites:

SwiftUI (shared iOS/macOS)

View state, data flow, @Observable → See axiom-swiftui
Navigation (NavigationStack basics) → See axiom-swiftui (skills/nav.md)
Layout (ViewThatFits, AnyLayout) → See axiom-swiftui (skills/layout.md)
Animations → See axiom-swiftui (skills/animation-ref.md)

Data & persistence

SwiftData, Core Data, GRDB → See axiom-data
CloudKit sync → See axiom-data

Concurrency

Swift 6 concurrency, actors, Sendable → See axiom-concurrency

Other

Accessibility (VoiceOver, Dynamic Type) → See axiom-accessibility
Networking (URLSession, Network.framework) → See axiom-networking
Security (Keychain, passkeys, encryption) → See axiom-security

Conflict Resolution

axiom-macos vs axiom-swiftui: When working on a macOS SwiftUI app:

Use axiom-macos for macOS-only concerns: windows, menus, commands, sandboxing, distribution, Table, Inspector, AppKit bridging
Use axiom-swiftui for cross-platform SwiftUI: navigation, layout, state management, animations
Both may apply: A macOS app using NavigationSplitView with Table needs axiom-macos for Table specifics and axiom-swiftui for NavigationSplitView basics

axiom-macos vs axiom-security: For sandbox and code signing:

Use axiom-macos for macOS App Sandbox, security-scoped bookmarks, file access entitlements, Developer ID signing
Use axiom-security for Keychain storage, encryption, passkeys, certificate management

Decision Tree

digraph macos {
    start [label="macOS development task" shape=ellipse];
    what [label="What area?" shape=diamond];

    start -> what;
    what -> "skills/windows.md" [label="windows/scenes"];
    what -> "skills/menus-and-commands.md" [label="menus/commands/shortcuts"];
    what -> "skills/swiftui-differences.md" [label="Table/Inspector/focus/macOS SwiftUI"];
    what -> "skills/sandbox-and-file-access.md" [label="sandbox/file access"];
    what -> "skills/direct-distribution.md" [label="distribution/notarization/updates"];
    what -> "skills/appkit-interop.md" [label="AppKit bridging"];
    what -> "skills/appkit-modernization.md" [label="modernize AppKit\n(input/restoration/27 look)"];
    what -> "skills/ios-apps-on-mac.md" [label="iOS app to Mac\n(Catalyst / Designed for iPad)"];
    what -> "skills/screencapturekit.md" [label="screen capture/\nrecording/sharing"];
    what -> "axiom-swiftui" [label="cross-platform SwiftUI"];
    what -> "axiom-security" [label="Keychain/encryption"];
}

iOS screen capture? ScreenCaptureKit is macOS-only. For iOS screen recording, use ReplayKit — see axiom-media.

Resources

WWDC: 2021-10062, 2022-10061, 2022-10075, 2023-10148, 2024-10149, 2026-272, 2026-289

Docs: /security/app-sandbox, /swiftui/windowgroup, /swiftui/table

Skills: axiom-swiftui, axiom-security, axiom-concurrency, axiom-uikit

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Other
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @CharlesWiltgen · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: macOS · Windows
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview axiom-macos-c483a6fb26.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# macOS Development

**You MUST use this skill for ANY macOS-specific development including windows, menus, sandboxing, distribution, AppKit bridging, and macOS SwiftUI differences.**

## Quick Reference

| Symptom / Task | Reference |
|----------------|-----------|
| Window management (WindowGroup, Window, MenuBarExtra, DocumentGroup) | See `skills/windows.md` |
| Menu bar, commands, keyboard shortcuts | See `skills/menus-and-commands.md` |
| Table, Inspector, NavigationSplitView, focus | See `skills/swiftui-differences.md` |
| App Sandbox, file access, security-scoped bookmarks | See `skills/sandbox-and-file-access.md` |
| Developer ID, notarization, Sparkle auto-updates | See `skills/direct-distribution.md` |
| NSViewRepresentable, NSHostingController, AppKit bridging, @Observable in AppKit, NSHostingMenu, SwiftUI scenes from AppKit | See `skills/appkit-interop.md` |
| Modernizing AppKit: mouseDown replacement, control events, status-item sessions, state restoration, concentric corners, touch (`OS27`) | See `skills/appkit-modernization.md` |
| Screen recording, sharing, or capture (ScreenCaptureKit) | See `skills/screencapturekit.md` |
| SCStream / SCContentFilter / screenshots / file recording API | See `skills/screencapturekit-ref.md` |
| Bring an iOS app to Mac: Catalyst adoption, Designed for iPad, Mac availability opt-out | See `skills/ios-apps-on-mac.md` |
| Apple Pay on Mac / Catalyst | See `axiom-payments/skills/apple-pay.md` (Catalyst section) |

## Cross-Suite Routes

These topics overlap with macOS development but live in separate suites:

#### SwiftUI (shared iOS/macOS)
- View state, data flow, @Observable → See axiom-swiftui
- Navigation (NavigationStack basics) → See axiom-swiftui (skills/nav.md)

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Quick Reference → Cross-Suite Routes → Conflict Resolution → Decision Tree → Resources
terms    -> axiom-macos vs axiom-swiftui · Use axiom-macos · Use axiom-swiftui · Both may apply · axiom-macos vs axiom-security · Use axiom-security · iOS screen capture? · WWDC
files/cmd -> skills/windows.md · skills/menus-and-commands.md · skills/swiftui-differences.md · skills/sandbox-and-file-access.md · skills/direct-distribution.md · skills/appkit-interop.md · OS27 · skills/appkit-modernization.md
body sha256 -> 2c3acebe260d