macos-swiftui-dev

Included with Lifetime

$97 forever

Create macOS applications using SwiftUI. Use when building macOS apps from scratch, including window-based apps, menu bar apps, apps with sidebar navigation, or when adding macOS-specific features like keyboard shortcuts, toolbars, and native UI components. Triggers on requests like "Build me a macOS app", "Create a SwiftUI app for Mac", "Make a menu bar app", or "Add keyboard shortcuts to my macOS app".

Designassets

What this skill does


# macOS SwiftUI Development

## Overview

Create native macOS applications using SwiftUI with proper structure, navigation patterns, and macOS-specific UI components.

## Project Structure

Create files in the working directory with the following structure:

```
AppName/
├── AppName/
│   ├── AppNameApp.swift          # Main app entry point
│   ├── ContentView.swift         # Main content view
│   ├── Views/                    # Additional views
│   └── Models/                   # Data models
└── Info.plist                    # App configuration
```

## App Type Selection

Choose the appropriate template based on the user's request:

### Window-Based Apps
Use `assets/templates/BasicWindowApp.swift` when creating:
- Standard macOS applications with windows
- Apps with sidebar navigation
- Document-based applications
- Multi-window applications

### Menu Bar Apps
Use `assets/templates/MenuBarApp.swift` when creating:
- Apps that live in the menu bar
- Status bar utilities
- Background monitoring tools
- Quick-access tools

## Quick Start Workflows

### Creating a Basic Window App

1. Copy the BasicWindowApp.swift template from `assets/templates/`
2. Rename the struct and update app name references
3. Customize the ContentView with the desired layout
4. Add NavigationSplitView for sidebar navigation if needed
5. Include Info.plist from `assets/templates/Info.plist`

Example:
```swift
// Copy and modify BasicWindowApp.swift
@main
struct MyMacApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}
```

### Creating a Menu Bar App

1. Copy the MenuBarApp.swift template from `assets/templates/`
2. Update the app name and status bar icon
3. Customize the PopoverContentView with desired UI
4. Modify SettingsView for app preferences
5. Use Info-MenuBar.plist (with LSUIElement set to true)

Key components:
- `@NSApplicationDelegateAdaptor` for AppDelegate
- NSStatusItem for menu bar presence
- NSPopover for displaying UI
- Settings scene for preferences window

### Adding Keyboard Shortcuts

Add to the App struct:
```swift
.commands {
    CommandMenu("Actions") {
        Button("New Item") {
            createNewItem()
        }
        .keyboardShortcut("n", modifiers: .command)
        
        Button("Delete") {
            deleteItem()
        }
        .keyboardShortcut(.delete)
    }
}
```

## Reference Documentation

Consult these references for detailed patterns and examples:

- **`references/swiftui-patterns.md`**: Comprehensive SwiftUI patterns for macOS including navigation, windows, forms, tables, toolbars, and more
- **`references/menubar-apps.md`**: Complete guide for menu bar app development including popovers, menus, icons, and launch at login

## Common Patterns

### Navigation with Sidebar
```swift
NavigationSplitView {
    List {
        NavigationLink("Section 1", destination: Section1View())
        NavigationLink("Section 2", destination: Section2View())
    }
} detail: {
    Text("Select an item")
}
```

### Toolbar
```swift
.toolbar {
    ToolbarItem(placement: .primaryAction) {
        Button("Add") {
            addItem()
        }
    }
}
```

### Settings Window
```swift
Settings {
    SettingsView()
}
```

### Forms
```swift
Form {
    Section("General") {
        TextField("Name:", text: $name)
        Toggle("Enabled", isOn: $enabled)
    }
}
.formStyle(.grouped)
```

## macOS-Specific Considerations

1. **Window Sizing**: Always set minimum window sizes with `.frame(minWidth:minHeight:)`
2. **Menu Bar**: Use template images for automatic dark mode support
3. **Keyboard Navigation**: Ensure all interactive elements support keyboard access
4. **Settings**: Provide a Settings scene for user preferences
5. **Info.plist**: Use `LSUIElement: true` for menu bar-only apps
6. **SF Symbols**: Use system symbols for consistent iconography

## Workflow

1. Determine app type (window-based or menu bar)
2. Copy appropriate template from `assets/templates/`
3. Customize app name and bundle identifier
4. Build out UI using SwiftUI components
5. Add keyboard shortcuts and menus as needed
6. Consult reference files for specific patterns
7. Include proper Info.plist configuration

## Resources

### assets/templates/
- `BasicWindowApp.swift` - Standard window-based app with sidebar navigation
- `MenuBarApp.swift` - Complete menu bar app with popover and settings
- `Info.plist` - Standard app configuration
- `Info-MenuBar.plist` - Menu bar app configuration (LSUIElement: true)

### references/
- `swiftui-patterns.md` - Comprehensive SwiftUI patterns for macOS
- `menubar-apps.md` - Menu bar app development guide

Files: 7

Size: 22.0 KB

Complexity: 52/100

Category: Design

Source: https://github.com/fanthus/agent-skills/tree/main/macos-swiftui-dev

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts