macos-menubar-tuist-app

# macos-menubar-tuist-app Build and maintain macOS menubar apps with a Tuist-first workflow and stable launch scripts. Preserve strict architecture boundaries so networking, state, and UI remain testable and predictable. ## When to Use - When working on LSUIElement menubar utilities built with Tuist and SwiftUI. - When you need Tuist manifests, launch scripts, or architecture guidance for a menubar app. ## Core Rules - Keep the app menubar-only unless explicitly told otherwise. Use `LSUIElement = true` by default. - Keep transport and decoding logic outside views. Do not call networking from SwiftUI view bodies. - Keep state transitions in a store layer (`@Observable` or equivalent), not in row/view presentation code. - Keep model decoding resilient to API drift: optional fields, safe fallbacks, and defensive parsing. - Treat Tuist manifests as the source of truth. Do not rely on hand-edited generated Xcode artifacts. - Prefer script-based launch for local iteration when `tuist run` is unreliable for macOS target/device resolution. - Prefer `tuist xcodebuild build` over raw `xcodebuild` in local run scripts when building generated projects. ## Expected File Shape Use this placement by default: - `Project.swift`: app target, settings, resources, `Info.plist` keys - `Sources/*Model*.swift`: API/domain models and decoding - `Sources/*Client*.swift`: requests, response mapping, transport concerns - `Sources/*Store*.swift`: observable state, refresh policy, filtering, cach...