[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETGWRBGFH39Z3AEGAV84WN":3,"skill-same:01M7ETGWRBGFH39Z3AEGAV84WN":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7ETGWRBGFH39Z3AEGAV84WN","macos-menubar-tuist-app",null,"Build, refactor, or review SwiftUI macOS menubar apps that use Tuist.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdesign\u002Fmacos-menubar-tuist-app\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ncategory: design\nname: macos-menubar-tuist-app\ndescription: Build, refactor, or review SwiftUI macOS menubar apps that use Tuist.\nrisk: safe\nsource: \"Dimillian\u002FSkills (MIT)\"\ndate_added: \"2026-03-25\"\n---\n\n# macos-menubar-tuist-app\n\nBuild 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.\n\n## When to Use\n- When working on LSUIElement menubar utilities built with Tuist and SwiftUI.\n- When you need Tuist manifests, launch scripts, or architecture guidance for a menubar app.\n\n## Core Rules\n\n- Keep the app menubar-only unless explicitly told otherwise. Use `LSUIElement = true` by default.\n- Keep transport and decoding logic outside views. Do not call networking from SwiftUI view bodies.\n- Keep state transitions in a store layer (`@Observable` or equivalent), not in row\u002Fview presentation code.\n- Keep model decoding resilient to API drift: optional fields, safe fallbacks, and defensive parsing.\n- Treat Tuist manifests as the source of truth. Do not rely on hand-edited generated Xcode artifacts.\n- Prefer script-based launch for local iteration when `tuist run` is unreliable for macOS target\u002Fdevice resolution.\n- Prefer `tuist xcodebuild build` over raw `xcodebuild` in local run scripts when building generated projects.\n\n## Expected File Shape\n\nUse this placement by default:\n\n- `Project.swift`: app target, settings, resources, `Info.plist` keys\n- `Sources\u002F*Model*.swift`: API\u002Fdomain models and decoding\n- `Sources\u002F*Client*.swift`: requests, response mapping, transport concerns\n- `Sources\u002F*Store*.swift`: observable state, refresh policy, filtering, caching\n- `Sources\u002F*Menu*View*.swift`: menu composition and top-level UI state\n- `Sources\u002F*Row*View*.swift`: row rendering and lightweight interactions\n- `run-menubar.sh`: canonical local restart\u002Fbuild\u002Flaunch path\n- `stop-menubar.sh`: explicit stop helper when needed\n\n## Workflow\n\n1. Confirm Tuist ownership\n- Verify `Tuist.swift` and `Project.swift` (or workspace manifests) exist.\n- Read existing run scripts before changing launch behavior.\n\n2. Probe backend behavior before coding assumptions\n- Use `curl` to verify endpoint shape, auth requirements, and pagination behavior.\n- If endpoint ignores `limit\u002Fpage`, implement full-list handling with local trimming in the store.\n\n3. Implement layers from bottom to top\n- Define\u002Fadjust models first.\n- Add or update client request\u002Fdecoding logic.\n- Update store refresh, filtering, and cache policy.\n- Wire views last.\n\n4. Keep app wiring minimal\n- Keep app entry focused on scene\u002Fmenu wiring and dependency injection.\n- Avoid embedding business logic in `App` or menu scene declarations.\n\n5. Standardize launch ergonomics\n- Ensure run script restarts an existing instance before relaunching.\n- Ensure run script does not open Xcode as a side effect.\n- Use `tuist generate --no-open` when generation is required.\n- When the run script builds the generated project, prefer `TUIST_SKIP_UPDATE_CHECK=1 tuist xcodebuild build ...` instead of invoking raw `xcodebuild` directly.\n\n## Validation Matrix\n\nRun validations after edits:\n\n```bash\nTUIST_SKIP_UPDATE_CHECK=1 tuist xcodebuild build -scheme \u003CTargetName> -configuration Debug\n```\n\nIf launch workflow changed:\n\n```bash\n.\u002Frun-menubar.sh\n```\n\nIf shell scripts changed:\n\n```bash\nbash -n run-menubar.sh\nbash -n stop-menubar.sh\n.\u002Frun-menubar.sh\n```\n\n## Failure Patterns and Fix Direction\n\n- `tuist run` cannot resolve the macOS destination:\nUse run\u002Fstop scripts as canonical local run path.\n\n- Menu UI is laggy or inconsistent after refresh:\nMove derived state and filtering into the store; keep views render-only.\n\n- API payload changes break decode:\nRelax model decoding with optional fields and defaults, then surface missing data safely in UI.\n\n- Feature asks for quick UI patch:\nTrace root cause in model\u002Fclient\u002Fstore before changing row\u002Fmenu presentation.\n\n## Completion Checklist\n\n- Preserve menubar-only behavior unless explicitly changed.\n- Keep network and state logic out of SwiftUI view bodies.\n- Keep Tuist manifests and run scripts aligned with actual build\u002Frun flow.\n- Run the validation matrix for touched areas.\n- Report concrete commands run and outcomes.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# macos-menubar-tuist-app\n\nBuild 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.\n\n## When to Use\n- When working on LSUIElement menubar utilities built with Tuist and SwiftUI.\n- When you need Tuist manifests, launch scripts, or architecture guidance for a menubar app.\n\n## Core Rules\n\n- Keep the app menubar-only unless explicitly told otherwise. Use `LSUIElement = true` by default.\n- Keep transport and decoding logic outside views. Do not call networking from SwiftUI view bodies.\n- Keep state transitions in a store layer (`@Observable` or equivalent), not in row\u002Fview presentation code.\n- Keep model decoding resilient to API drift: optional fields, safe fallbacks, and defensive parsing.\n- Treat Tuist manifests as the source of truth. Do not rely on hand-edited generated Xcode artifacts.\n- Prefer script-based launch for local iteration when `tuist run` is unreliable for macOS target\u002Fdevice resolution.\n- Prefer `tuist xcodebuild build` over raw `xcodebuild` in local run scripts when building generated projects.\n\n## Expected File Shape\n\nUse this placement by default:\n\n- `Project.swift`: app target, settings, resources, `Info.plist` keys\n- `Sources\u002F*Model*.swift`: API\u002Fdomain models and decoding\n- `Sources\u002F*Client*.swift`: requests, response mapping, transport concerns\n- `Sources\u002F*Store*.swift`: observable state, refresh policy, filtering, caching\n- `Sources\u002F*Menu*View*.swift`: menu composition and top-level UI state\n- `Sources\u002F*Row*View*.swift`: row rendering and lightweight interactions\n- `run-menubar.sh`: canonical local restart\u002Fbuild\u002Flaunch path\n- `stop-menubar.sh`: explicit stop helper when needed\n\n## Workflow\n\n1. Confirm Tuist ownership\n- Verify `Tuist.swift` and `Project.swift` (or workspace manifests) exist.\n- Read existing run scripts before changing launch behavior.\n\n2. Probe backend behavior before coding assumptions\n- Use `curl` to verify endpoint shape, auth requirements, and pagination behavior.\n- If endpoint ignores `limit\u002Fpage`, implement full-list handling with local trimming in the store.\n\n3. Implement layers from bottom to top\n- Define\u002Fadjust models first.\n- Add or update client request\u002Fdecoding logic.\n- Update store refresh, filtering, and cache policy.\n- Wire views last.\n\n4. Keep app wiring minimal\n- Keep app entry focused on scene\u002Fmenu wiring and dependency injection.\n- Avoid embedding business logic in `App` or menu scene declarations.\n\n5. Standardize launch ergonomics\n- Ensure run script restarts an existing instance before relaunching.\n- Ensure run script does not open Xcode as a side effect.\n- Use `tuist generate --no-open` when generation is required.\n- When the run script builds the generated project, prefer `TUIST_SKIP_UPDATE_CHECK=1 tuist xcodebuild build ...` instead of invoking raw `xcodebuild` directly.\n\n## Validation Matrix\n\nRun validations after edits:\n\n```bash\nTUIST_SKIP_UPDATE_CHECK=1 tuist xcodebuild build -scheme \u003CTargetName> -configuration Debug\n```\n\nIf launch workflow changed:\n\n```bash\n.\u002Frun-menubar.sh\n```\n\nIf shell scripts changed:\n\n```bash\nbash -n run-menubar.sh\nbash -n stop-menubar.sh\n.\u002Frun-menubar.sh\n```\n\n## Failure Patterns and Fix Direction\n\n- `tuist run` cannot resolve the macOS destination:\nUse run\u002Fstop scripts as canonical local run path.\n\n- Menu UI is laggy or inconsistent after refresh:\nMove derived state and filtering into the store; keep views render-only.\n\n- API payload changes break decode:\nRelax model decoding with optional fields and defaults, then surface missing data safely in UI.\n\n- Feature asks for quick UI patch:\nTrace root cause in model\u002Fclient\u002Fstore before changing row\u002Fmenu presentation.\n\n## Completion Checklist\n\n- Preserve menubar-only behavior unless explicitly changed.\n- Keep network and state logic out of SwiftUI view bodies.\n- Keep Tuist manifests and run scripts aligned with actual build\u002Frun flow.\n- Run the validation matrix for touched areas.\n- Report concrete commands run and outcomes.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"category":26,"date_added":27,"description":7},"safe","Dimillian\u002FSkills (MIT)","design","2026-03-25","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fdesign\u002Fmacos-menubar-tuist-app","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill macos-menubar-tuist-app",{"tool":40,"command":41},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill macos-menubar-tuist-app",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill macos-menubar-tuist-app","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdesign\u002Fmacos-menubar-tuist-app\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",299,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdesign\u002Fmacos-menubar-tuist-app\u002Fagents\u002Fopenai.yaml",[55,63,70,77,84,91],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":62},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":62},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":62},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":62},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":62},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":62},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]