macos-menubar-tuist-app
Skill2 starsChanged 4 months agoMITView on GitHub
Build, refactor, or review macOS menubar apps that use Tuist and SwiftUI. Use when creating or maintaining LSUIElement menubar utilities, defining Tuist targets/manifests, implementing model-client-store-view architecture, adding script-based launch flows, or validating reliable local build/run behavior without Xcode-first workflows.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- aresbit/claude-skillsedited, first seen Jul 12, 2026
- Dimillian/Skillsword for word, first seen Mar 6, 2026
Other versions2 projects use a version of this.
Word for word · 1
- Dimillian/Skills★ 4k100% same
Edited · 1
- aresbit/claude-skills★ 098% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository383 other files it gives its agents.
- 37signals-waySkill
- ab-test-analysisSkill
- advisor-orchestrator-workerSkill
- ai-ml-engineeringSkill
- algorithmic-artSkill
- analyze-feature-requestsSkill
- animation-vocabularySkill
- apple-designSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- improve-animationsSkill
- pick-ui-librarySkill
- prototypeSkill
- review-animationsSkill
- ansoff-matrixSkill
- api-and-interface-designSkill
- api-design-best-practicesSkill
- app-store-changelogSkill
- auth-authorizationSkill
- beachhead-segmentSkill
- blue-ocean-strategySkill
- brainstorm-experiments-existingSkill
- brainstorm-experiments-newSkill
- brainstorm-ideas-existingSkill
- brainstorm-ideas-newSkill
- brainstorm-okrsSkill
- brand-guidelinesSkill
- browser-testing-with-devtoolsSkill
- bug-hunt-swarmSkill
- business-modelSkill
- canvas-designSkill
- ci-cd-and-automationSkill
- claude-apiSkill
- clean-architectureSkill
- clean-codeSkill
- cli-creatorSkill
- code-review-and-qualitySkill
- code-review-skillSkill
- code-simplificationSkill
- cohort-analysisSkill
- cold-start-problemSkill
- commit-archaeologistSkill
- competitive-battlecardSkill
- competitor-analysisSkill
- contagiousSkill
- context-engineeringSkill
- continuous-discoverySkill
- architecture-blueprint-generatorSkill
- azure-architecture-autopilotSkill
- cli-masterySkill
- codeqlSkill
- conventional-commitSkill
- create-implementation-planSkill
- csharp-asyncSkill
- diagnoseSkill
- dotnet-best-practicesSkill
- draw-io-diagram-generatorSkill
- git-commitSkill
- github-actions-efficiencySkill
- java-springbootSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
28 rules. About 0 are common, 18 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈18
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Keep the app menubar-only unless explicitly told otherwise.
- Distinctive: line 13
Keep transport and decoding logic outside views.
- Very specific: line 14
Keep state transitions in a store layer (@Observable or equivalent), not in row/view presentation code.
- Distinctive: line 15
Keep model decoding resilient to API drift: optional fields, safe fallbacks, and defensive parsing.
- Distinctive: line 16
Treat Tuist manifests as the source of truth.
- Very specific: line 17
Prefer script-based launch for local iteration when tuist run is unreliable for macOS target/device resolution.
- Very specific: line 18
Prefer tuist xcodebuild build over raw xcodebuild in local run scripts when building generated projects.
- Distinctive: line 22
Use this placement by default:
- Very specific: line 36
Verify Tuist.swift and Project.swift (or workspace manifests) exist.
- Distinctive: line 37
Read existing run scripts before changing launch behavior.
- Very specific: line 40
Use curl to verify endpoint shape, auth requirements, and pagination behavior.
- Very specific: line 41
If endpoint ignores limit/page, implement full-list handling with local trimming in the store.
- Distinctive: line 45
Add or update client request/decoding logic.
- Distinctive: line 46
Update store refresh, filtering, and cache policy.
- Distinctive: line 49
Keep app wiring minimal
- Distinctive: line 50
Keep app entry focused on scene/menu wiring and dependency injection.
- Very specific: line 51
Avoid embedding business logic in App or menu scene declarations.
- Distinctive: line 54
Ensure run script restarts an existing instance before relaunching.
- Distinctive: line 55
Ensure run script does not open Xcode as a side effect.
- Very specific: line 56
Use tuist generate --no-open when generation is required.
- Very specific: line 57
When the run script builds the generated project, prefer TUIST_SKIP_UPDATE_CHECK=1 tuist xcodebuild build ...
- Distinctive: line 61
Run validations after edits:
- Distinctive: line 67
If launch workflow changed:
- Distinctive: line 73
If shell scripts changed:
- Distinctive: line 84
Use run/stop scripts as canonical local run path.
- Distinctive: line 98
Keep network and state logic out of SwiftUI view bodies.
- Distinctive: line 99
Keep Tuist manifests and run scripts aligned with actual build/run flow.
- Distinctive: line 100
Run the validation matrix for touched areas.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Core Rules
- Keep the app menubar-only unless explicitly told otherwise. Use
LSUIElement = trueby default. - Keep transport and decoding logic outside views. Do not call networking from SwiftUI view bodies.
- Keep state transitions in a store layer (
@Observableor 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 runis unreliable for macOS target/device resolution. - Prefer
tuist xcodebuild buildover rawxcodebuildin local run scripts when building generated projects.
Expected File Shape
Use this placement by default:
Project.swift: app target, settings, resources,Info.plistkeysSources/*Model*.swift: API/domain models and decodingSources/*Client*.swift: requests, response mapping, transport concernsSources/*Store*.swift: observable state, refresh policy, filtering, cachingSources/*Menu*View*.swift: menu composition and top-level UI stateSources/*Row*View*.swift: row rendering and lightweight interactionsrun-menubar.sh: canonical local restart/build/launch pathstop-menubar.sh: explicit stop helper when needed
Workflow
- Confirm Tuist ownership
- Verify
Tuist.swiftandProject.swift(or workspace manifests) exist. - Read existing run scripts before changing launch behavior.
- Probe backend behavior before coding assumptions
- Use
curlto verify endpoint shape, auth requirements, and pagination behavior. - If endpoint ignores
limit/page, implement full-list handling with local trimming in the store.
- Implement layers from bottom to top
- Define/adjust models first.
- Add or update client request/decoding logic.
- Update store refresh, filtering, and cache policy.
- Wire views last.
- Keep app wiring minimal
- Keep app entry focused on scene/menu wiring and dependency injection.
- Avoid embedding business logic in
Appor menu scene declarations.
- Standardize launch ergonomics
- Ensure run script restarts an existing instance before relaunching.
- Ensure run script does not open Xcode as a side effect.
- Use
tuist generate --no-openwhen generation is required. - When the run script builds the generated project, prefer
TUIST_SKIP_UPDATE_CHECK=1 tuist xcodebuild build ...instead of invoking rawxcodebuilddirectly.
Validation Matrix
Run validations after edits:
TUIST_SKIP_UPDATE_CHECK=1 tuist xcodebuild build -scheme <TargetName> -configuration DebugIf launch workflow changed:
./run-menubar.shIf shell scripts changed:
bash -n run-menubar.sh
bash -n stop-menubar.sh
./run-menubar.shFailure Patterns and Fix Direction
tuist runcannot resolve the macOS destination: Use run/stop scripts as canonical local run path.- Menu UI is laggy or inconsistent after refresh: Move derived state and filtering into the store; keep views render-only.
- API payload changes break decode: Relax model decoding with optional fields and defaults, then surface missing data safely in UI.
- Feature asks for quick UI patch: Trace root cause in model/client/store before changing row/menu presentation.
Completion Checklist
- Preserve menubar-only behavior unless explicitly changed.
- Keep network and state logic out of SwiftUI view bodies.
- Keep Tuist manifests and run scripts aligned with actual build/run flow.
- Run the validation matrix for touched areas.
- Report concrete commands run and outcomes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

