macos-menubar-tuist-app

Build and refactor macOS menubar apps with Tuist and SwiftUI.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/irchamaji/agents --skill macos-menubar-tuist-app-irchamaji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: macos-menubar-tuist-app
Source: https://github.com/irchamaji/agents/tree/main/skills/macos-menubar-tuist-app
Command: npx skills add https://github.com/irchamaji/agents --skill macos-menubar-tuist-app-irchamaji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the friction of building and maintaining reliable macOS menubar apps when Tuist-driven projects and SwiftUI architecture drift, especially when local iteration becomes flaky or Xcode-first workflows sneak in.

Core Features & Use Cases

  • Tuist-first project correctness: Treats Tuist manifests as the source of truth and avoids relying on hand-edited generated Xcode artifacts.
  • Clean architecture for testability: Keeps networking/decoding out of SwiftUI views, centralizes state transitions in store layers, and preserves model-client-store-view boundaries.
  • Resilient local build and launch: Uses canonical run/stop scripts for deterministic restart/build/launch behavior when tuist run or macOS device resolution is unreliable.

Quick Start

Use macos-menubar-tuist-app to scaffold a menubar-only LSUIElement Tuist + SwiftUI app and verify the Debug build and local run behavior using run-menubar.sh.

Frequently Asked Questions about macos-menubar-tuist-app

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a macOS menubar app with Tuist and SwiftUI?

To build a macOS menubar app with Tuist and SwiftUI, define Tuist manifests as the source of truth, implement a model-client-store-view architecture, configure LSUIElement defaults, and verify deterministic local iteration using run-menubar scripts.

Why does my Tuist menubar app show in the Dock instead of the menubar?

Your Tuist menubar app appears in the Dock instead of the menubar when LSUIElement defaults are not set to true in the project configuration. Applying LSUIElement ensures the app runs as a background menubar-only instance without a Dock icon.

What's the best way to separate networking logic from SwiftUI views in a Tuist app?

The best way to separate networking logic from SwiftUI views in a Tuist app is implementing a model-client-store-view architecture. This centralizes state transitions in store layers and keeps networking and decoding out of views for better testability.

Can I use run scripts instead of Xcode-first workflows for local Tuist app iteration?

Yes, you can use canonical run and stop scripts instead of Xcode-first workflows for local Tuist app iteration. Script-based launch flows provide deterministic restart, build, and launch behavior when tuist run or macOS device resolution becomes unreliable.

How do I validate a Tuist project build without relying on generated Xcode artifacts?

Validate a Tuist project build without relying on generated Xcode artifacts by treating Tuist manifests as the source of truth and running deterministic validation via tuist xcodebuild. This avoids hand-edited generated Xcode artifacts entirely.

How do I prevent flaky local builds when developing a SwiftUI menubar app?

Prevent flaky local builds when developing a SwiftUI menubar app by using canonical run-menubar and stop scripts for deterministic restart and launch behavior. This avoids unreliable tuist run commands and Xcode-first workflow drift.