Vibecode Gojo

You are building a lean indie version of Gojo.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# Gojo indie build

## Goal

Build the smallest trustworthy replacement for the core Gojo workflow for one developer or a tiny team.

## Scope

Open a small panel from the MacBook notch and jump between clipboard history, a file shelf, music controls, window snapping, and screen warmth.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- signed and notarized builds with automatic updates
- smooth notch behavior across multiple displays
- on-device dictation and its safety checks
- built-in calendar, reminders, webcam, and battery tools
- fixes when a macOS update breaks something

If those capabilities are essential, use Gojo source instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build a small macOS notch app inspired by Gojo. Keep v1 to five tabs:

- Use Swift 6, SwiftUI, and AppKit on macOS 14. Generate an Xcode project and skip
  third-party packages.
- Make it an accessory app with no Dock icon. Find the built-in display notch and
  anchor a borderless floating panel right below it.
- Open the panel after the pointer rests at the notch for 200 ms. Close it on an
  outside click or Escape. Add Music, Windows, Clipboard, Shelf, and Display tabs.
- Clipboard: poll NSPasteboard, save the latest 100 text items in Application Support,
  add search, and copy a picked item back. Skip transient and concealed pasteboard
  types, plus apps listed in a configurable denylist.
- Shelf: accept dropped files, save security-scoped bookmarks, show file icons, and
  support dragging files into another app. Add remove and clear-all actions.
- Music: control Apple Music or Spotify through AppleScript. Show the active app and
  track title, with play/pause, previous, and next controls.
- Windows: list visible app windows through the Accessibility API. Add left half,
  right half, and maximize actions.
- Display: save each screen's gamma table, apply blackbody RGB multipliers with
  CGSetDisplayTransferByTable, and restore the original table on disable or exit.
- Save settings in UserDefaults. Leave out accounts, sync, telemetry, calendar,
  camera, dictation, battery widgets, and automatic updates.
- On first launch, walk through the permissions. Give every tab a useful empty state.
- Test clipboard deduplication, shelf persistence, and snap-frame math.
- Document setup, privacy, Accessibility and Automation permissions, and the macOS
  APIs most likely to change.

## Required capabilities

- macOS 14 or later
- Xcode 16
- Accessibility permission for window control
- Apple Events permission for media control
- local storage

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a lean indie version of Gojo.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# Gojo indie build

## Goal

Build the smallest trustworthy replacement for the core Gojo workflow for one developer or a tiny team.

## Scope

Open a small panel from the MacBook notch and jump between clipboard history, a file shelf, music controls, window snapping, and screen warmth.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- signed and notarized builds with automatic updates
- smooth notch behavior across multiple displays
- on-device dictation and its safety checks
- built-in calendar, reminders, webcam, and battery tools
- fixes when a macOS update breaks something

If those capabilities are essential, use Gojo source instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build a small macOS notch app inspired by Gojo. Keep v1 to five tabs:

- Use Swift 6, SwiftUI, and AppKit on macOS 14. Generate an Xcode project and skip
  third-party packages.
- Make it an accessory app with no Dock icon. Find the built-in display notch and
  anchor a borderless floating panel right below it.
- Open the panel after the pointer rests at the notch for 200 ms. Close it on an
  outside click or Escape. Add Music, Windows, Clipboard, Shelf, and Display tabs.
- Clipboard: poll NSPasteboard, save the latest 100 text items in Application Support,
  add search, and copy a picked item back. Skip transient and concealed pasteboard
  types, plus apps listed in a configurable denylist.
- Shelf: accept dropped files, save security-scoped bookmarks, show file icons, and
  support dragging files into another app. Add remove and clear-all actions.
- Music: control Apple Music or Spotify through AppleScript. Show the active app and
  track title, with play/pause, previous, and next controls.
- Windows: list visible app windows through the Accessibility API. Add left half,
  right half, and maximize actions.
- Display: save each screen's gamma table, apply blackbody RGB multipliers with
  CGSetDisplayTransferByTable, and restore the original table on disable or exit.
- Save settings in UserDefaults. Leave out accounts, sync, telemetry, calendar,
  camera, dictation, battery widgets, and automatic updates.
- On first launch, walk through the permissions. Give every tab a useful empty state.
- Test clipboard deduplication, shelf persistence, and snap-frame math.
- Document setup, privacy, Accessibility and Automation permissions, and the macOS
  APIs most likely to change.

## Required capabilities

- macOS 14 or later
- Xcode 16
- Accessibility permission for window control
- Apple Events permission for media control
- local storage

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a production product version of Gojo.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== PRODUCT.md =====
# Gojo product brief

## Problem

A weekend is enough for the useful part: a notch panel with clipboard history, a file shelf, music controls, window snapping, and screen warmth. Getting it ready for daily use takes longer because macOS permissions, dictation, multiple displays, and tiny UI details add up fast.

## Product outcome

Open a small panel from the MacBook notch and jump between clipboard history, a file shelf, music controls, window snapping, and screen warmth.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- macOS 14 or later
- Xcode 16
- Accessibility permission for window control
- Apple Events permission for media control
- local storage

## Explicit non-goals for v1

- signed and notarized builds with automatic updates
- smooth notch behavior across multiple displays
- on-device dictation and its safety checks
- built-in calendar, reminders, webcam, and battery tools
- fixes when a macOS update breaks something

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

===== ARCHITECTURE.md =====
# Architecture

## Starting brief

Build a small macOS notch app inspired by Gojo. Keep v1 to five tabs:

- Use Swift 6, SwiftUI, and AppKit on macOS 14. Generate an Xcode project and skip
  third-party packages.
- Make it an accessory app with no Dock icon. Find the built-in display notch and
  anchor a borderless floating panel right below it.
- Open the panel after the pointer rests at the notch for 200 ms. Close it on an
  outside click or Escape. Add Music, Windows, Clipboard, Shelf, and Display tabs.
- Clipboard: poll NSPasteboard, save the latest 100 text items in Application Support,
  add search, and copy a picked item back. Skip transient and concealed pasteboard
  types, plus apps listed in a configurable denylist.
- Shelf: accept dropped files, save security-scoped bookmarks, show file icons, and
  support dragging files into another app. Add remove and clear-all actions.
- Music: control Apple Music or Spotify through AppleScript. Show the active app and
  track title, with play/pause, previous, and next controls.
- Windows: list visible app windows through the Accessibility API. Add left half,
  right half, and maximize actions.
- Display: save each screen's gamma table, apply blackbody RGB multipliers with
  CGSetDisplayTransferByTable, and restore the original table on disable or exit.
- Save settings in UserDefaults. Leave out accounts, sync, telemetry, calendar,
  camera, dictation, battery widgets, and automatic updates.
- On first launch, walk through the permissions. Give every tab a useful empty state.
- Test clipboard deduplication, shelf persistence, and snap-frame math.
- Document setup, privacy, Accessibility and Automation permissions, and the macOS
  APIs most likely to change.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

===== AGENTS.md =====
# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

===== MILESTONES.md =====
# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

===== OPERATIONS.md =====
# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted Gojo capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# Gojo indie build

## Goal

Build the smallest trustworthy replacement for the core Gojo workflow for one developer or a tiny team.

## Scope

Open a small panel from the MacBook notch and jump between clipboard history, a file shelf, music controls, window snapping, and screen warmth.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- signed and notarized builds with automatic updates
- smooth notch behavior across multiple displays
- on-device dictation and its safety checks
- built-in calendar, reminders, webcam, and battery tools
- fixes when a macOS update breaks something

If those capabilities are essential, use Gojo source instead of pretending the gap is solved.

# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

# Build plan

## Original build brief

Build a small macOS notch app inspired by Gojo. Keep v1 to five tabs:

- Use Swift 6, SwiftUI, and AppKit on macOS 14. Generate an Xcode project and skip
  third-party packages.
- Make it an accessory app with no Dock icon. Find the built-in display notch and
  anchor a borderless floating panel right below it.
- Open the panel after the pointer rests at the notch for 200 ms. Close it on an
  outside click or Escape. Add Music, Windows, Clipboard, Shelf, and Display tabs.
- Clipboard: poll NSPasteboard, save the latest 100 text items in Application Support,
  add search, and copy a picked item back. Skip transient and concealed pasteboard
  types, plus apps listed in a configurable denylist.
- Shelf: accept dropped files, save security-scoped bookmarks, show file icons, and
  support dragging files into another app. Add remove and clear-all actions.
- Music: control Apple Music or Spotify through AppleScript. Show the active app and
  track title, with play/pause, previous, and next controls.
- Windows: list visible app windows through the Accessibility API. Add left half,
  right half, and maximize actions.
- Display: save each screen's gamma table, apply blackbody RGB multipliers with
  CGSetDisplayTransferByTable, and restore the original table on disable or exit.
- Save settings in UserDefaults. Leave out accounts, sync, telemetry, calendar,
  camera, dictation, battery widgets, and automatic updates.
- On first launch, walk through the permissions. Give every tab a useful empty state.
- Test clipboard deduplication, shelf persistence, and snap-frame math.
- Document setup, privacy, Accessibility and Automation permissions, and the macOS
  APIs most likely to change.

## Required capabilities

- macOS 14 or later
- Xcode 16
- Accessibility permission for window control
- Apple Events permission for media control
- local storage

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

# Gojo product brief

## Problem

A weekend is enough for the useful part: a notch panel with clipboard history, a file shelf, music controls, window snapping, and screen warmth. Getting it ready for daily use takes longer because macOS permissions, dictation, multiple displays, and tiny UI details add up fast.

## Product outcome

Open a small panel from the MacBook notch and jump between clipboard history, a file shelf, music controls, window snapping, and screen warmth.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- macOS 14 or later
- Xcode 16
- Accessibility permission for window control
- Apple Events permission for media control
- local storage

## Explicit non-goals for v1

- signed and notarized builds with automatic updates
- smooth notch behavior across multiple displays
- on-device dictation and its safety checks
- built-in calendar, reminders, webcam, and battery tools
- fixes when a macOS update breaks something

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

# Architecture

## Starting brief

Build a small macOS notch app inspired by Gojo. Keep v1 to five tabs:

- Use Swift 6, SwiftUI, and AppKit on macOS 14. Generate an Xcode project and skip
  third-party packages.
- Make it an accessory app with no Dock icon. Find the built-in display notch and
  anchor a borderless floating panel right below it.
- Open the panel after the pointer rests at the notch for 200 ms. Close it on an
  outside click or Escape. Add Music, Windows, Clipboard, Shelf, and Display tabs.
- Clipboard: poll NSPasteboard, save the latest 100 text items in Application Support,
  add search, and copy a picked item back. Skip transient and concealed pasteboard
  types, plus apps listed in a configurable denylist.
- Shelf: accept dropped files, save security-scoped bookmarks, show file icons, and
  support dragging files into another app. Add remove and clear-all actions.
- Music: control Apple Music or Spotify through AppleScript. Show the active app and
  track title, with play/pause, previous, and next controls.
- Windows: list visible app windows through the Accessibility API. Add left half,
  right half, and maximize actions.
- Display: save each screen's gamma table, apply blackbody RGB multipliers with
  CGSetDisplayTransferByTable, and restore the original table on disable or exit.
- Save settings in UserDefaults. Leave out accounts, sync, telemetry, calendar,
  camera, dictation, battery widgets, and automatic updates.
- On first launch, walk through the permissions. Give every tab a useful empty state.
- Test clipboard deduplication, shelf persistence, and snap-frame math.
- Document setup, privacy, Accessibility and Automation permissions, and the macOS
  APIs most likely to change.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted Gojo capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

$ choose a build depth, inspect the files, then open the complete pack in your agent