macos-menubar-tuist-app

To structure a macOS menubar app using Tuist and SwiftUI, this Skill standardizes project manifests to prevent Xcode configuration drift and enforces a layered architecture separating model, client, and store components for predictable state management.

Managing state in a SwiftUI menubar app without configuration drift is achieved by enforcing a clean separation between networking, domain models, and view logic through a Tuist-first architecture, ensuring predictable state management across model, client, and store layers.

Reliable local build and execution cycles for a macOS menubar app are established using canonical shell scripts, bypassing unreliable IDE-based run commands to provide consistent local development and testing workflows.

Yes, you can use Tuist manifests to avoid Xcode-generated configuration issues; this Skill implements a Tuist-first workflow that standardizes project manifests, directly addressing the complexity of managing macOS menubar applications and ensuring architectural integrity.

Xcode-based launch workflows break for macOS menubar apps due to configuration drift and unreliable IDE run commands; replacing them with validated shell-based launch workflows ensures consistent local development and reliable execution cycles.

Separating networking and domain models when building a macOS menubar app is required to enforce a clean layered architecture; this separation between client, model, and store components guarantees predictable state management and SwiftUI view logic integrity.