Setapp

Build me a focused macOS automation and desktop utilities workflow for the personal core of Setapp. Requirements:

- Use Swift 6, SwiftUI, AppKit where necessary, SQLite, and the macOS Keychain. Model local triggers, rules, permissions, action history, and settings; keep stable source IDs and timestamps.
- Paid product context: Build a small app launcher and update checker for legally owned local applications. Build only this DIY scope: Build a small macOS app launcher and update checker for legally owned local applications, expose keyboard-first controls, and store settings locally.
- Create a menu-bar app with a searchable command window and global hotkey.
- Implement only the primary feature and one settings screen instead of a plugin platform.
- Store configuration locally, support export or import, and never capture unrelated user content. Add launch-at-login, update-check opt-in, diagnostics export, and a complete uninstall note.
- Use a macOS window or menu bar panel with input, current state, and result review. Required input or access: macOS 14 or later; Xcode.
- Recovery: Request permissions just in time and explain why each is needed before opening System Settings.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A denied OS permission or unavailable target must leave user data unchanged and show what permission is missing.
- Out of scope: licensed catalog of commercial apps, developer relationships, billing, and distribution; years of OS-version edge cases. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Setapp

## Project scope
Build a small macOS app launcher and update checker for legally owned local applications, expose keyboard-first controls, and store settings locally.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Setapp, build a small app launcher and update checker for legally owned local applications. The hard boundary is licensed catalog of commercial apps, developer relationships, billing, and distribution, plus os integration polish and maintenance.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- macOS 14 or later
- Xcode
- only the permissions required by the selected feature

## Stack and architecture
- Use Swift 6, SwiftUI, AppKit where necessary, SQLite, and the macOS Keychain.
- Model local triggers, rules, permissions, action history, and settings; keep stable source IDs and timestamps.
- Interface for this macOS automation and desktop utilities workflow: a macOS window or menu bar panel with input, current state, and result review.

## Security and data integrity
- Request permissions just in time and explain why each is needed before opening System Settings.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: licensed catalog of commercial apps, developer relationships, billing, and distribution.

## Agent implementation rules
- Project rule, data: Model local triggers, rules, permissions, action history, and settings; keep stable source IDs and timestamps.
- Project rule, behavior: Create a menu-bar app with a searchable command window and global hotkey.
- Project rule, recovery: Request permissions just in time and explain why each is needed before opening System Settings.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this macOS automation and desktop utilities operation with sample or user-owned data: Create a menu-bar app with a searchable command window and global hotkey.
- Show a concrete result or export: Store configuration locally, support export or import, and never capture unrelated user content.
- State the practical limit: licensed catalog of commercial apps, developer relationships, billing, and distribution.

## Engineering roadmap
1. Phase 1, architecture and data: Use Swift 6, SwiftUI, AppKit where necessary, SQLite, and the macOS Keychain. Model local triggers, rules, permissions, action history, and settings; keep stable source IDs and timestamps.
2. Phase 2, implement: Create a menu-bar app with a searchable command window and global hotkey.
3. Phase 3, implement: Implement only the primary feature and one settings screen instead of a plugin platform.
4. Phase 4, review and output: Store configuration locally, support export or import, and never capture unrelated user content.
5. Phase 5, recovery and acceptance: Request permissions just in time and explain why each is needed before opening System Settings. Verify this invariant with a saved fixture: A denied OS permission or unavailable target must leave user data unchanged and show what permission is missing. State the practical limit: licensed catalog of commercial apps, developer relationships, billing, and distribution.

## Paid-product capabilities outside this build
- licensed catalog of commercial apps, developer relationships, billing, and distribution
- years of OS-version edge cases
- large extension ecosystem
- cross-device sync
- commercial support and rapid compatibility fixes

## Implementation prompt
Build me a focused macOS automation and desktop utilities workflow for the personal core of Setapp. Requirements:

- Use Swift 6, SwiftUI, AppKit where necessary, SQLite, and the macOS Keychain. Model local triggers, rules, permissions, action history, and settings; keep stable source IDs and timestamps.
- Paid product context: Build a small app launcher and update checker for legally owned local applications. Build only this DIY scope: Build a small macOS app launcher and update checker for legally owned local applications, expose keyboard-first controls, and store settings locally.
- Create a menu-bar app with a searchable command window and global hotkey.
- Implement only the primary feature and one settings screen instead of a plugin platform.
- Store configuration locally, support export or import, and never capture unrelated user content. Add launch-at-login, update-check opt-in, diagnostics export, and a complete uninstall note.
- Use a macOS window or menu bar panel with input, current state, and result review. Required input or access: macOS 14 or later; Xcode.
- Recovery: Request permissions just in time and explain why each is needed before opening System Settings.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A denied OS permission or unavailable target must leave user data unchanged and show what permission is missing.
- Out of scope: licensed catalog of commercial apps, developer relationships, billing, and distribution; years of OS-version edge cases. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.