Vibecode Capture - Quick Notes

You are building a lean indie version of Capture - Quick Notes.

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 =====
# Capture - Quick Notes indie build

## Goal

Build the smallest trustworthy replacement for the core Capture - Quick Notes workflow for one developer or a tiny team.

## Scope

Catch text, links, images, and files on iPhone and Mac, sync them through your private iCloud, organize them into lists, then send each item on to the apps you actually use via destination-specific export actions.

## 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:
- App Store-ready polish across iPhone, iPad, Mac, Apple Watch, and Apple Vision Pro
- years of CloudKit migration, conflict, and offline-sync edge cases
- ongoing maintenance for more than 40 destination-specific export integrations
- the localization, accessibility, and device test matrix
- fast compatibility updates when Apple or a destination app changes behavior

If those capabilities are essential, use FSNotes 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 me a native quick-capture inbox for iPhone and Mac to replace Capture. Requirements:

- Swift 6 + SwiftUI, one Xcode project: an iOS app and a macOS menu bar app sharing a
  Swift package for the model, persistence, search, and export logic. SwiftData for
  storage, synced through my private CloudKit database.
- A capture is text, a URL, an image, or a file, with a list, archive state, and
  created/edited dates. Run NSDataDetector on text so URLs, phone numbers, and dates
  become tappable.
- iOS: a share extension so anything can be sent in from any app, plus a WidgetKit
  widget for one-tap capture. Mac: a menu bar item with a global hotkey opening a
  compact capture window.
- Inbox, Archive, and lists, with full-text search and undoable archive/delete. JSON
  export of everything so my notes are never trapped.
- Export actions for the destinations I actually use: Reminders and Calendar via
  EventKit, a Mail draft, Things and Bear via their URL schemes, and copy-as-Markdown.
  One small adapter file per destination so more are addable later.
- Offline-first: SwiftData writes locally and CloudKit retries when back online.
  Last-write-wins conflict handling is fine, say so in the README.
- No accounts, no telemetry, nothing leaves my devices except private iCloud sync and
  the exports I trigger.
- Out of scope: Apple Watch and Vision Pro apps, and Capture's 40+ destination catalog.
  Keeping that many exporters alive is the paid product's job, not mine.
- README: the entitlements to enable (App Groups, iCloud/CloudKit), and a plain warning
  that CloudKit sync needs a paid Apple Developer account.

## Required capabilities

- Xcode
- Apple Developer account for iCloud and App Group entitlements

## 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 Capture - Quick Notes.

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 =====
# Capture - Quick Notes indie build

## Goal

Build the smallest trustworthy replacement for the core Capture - Quick Notes workflow for one developer or a tiny team.

## Scope

Catch text, links, images, and files on iPhone and Mac, sync them through your private iCloud, organize them into lists, then send each item on to the apps you actually use via destination-specific export actions.

## 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:
- App Store-ready polish across iPhone, iPad, Mac, Apple Watch, and Apple Vision Pro
- years of CloudKit migration, conflict, and offline-sync edge cases
- ongoing maintenance for more than 40 destination-specific export integrations
- the localization, accessibility, and device test matrix
- fast compatibility updates when Apple or a destination app changes behavior

If those capabilities are essential, use FSNotes 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 me a native quick-capture inbox for iPhone and Mac to replace Capture. Requirements:

- Swift 6 + SwiftUI, one Xcode project: an iOS app and a macOS menu bar app sharing a
  Swift package for the model, persistence, search, and export logic. SwiftData for
  storage, synced through my private CloudKit database.
- A capture is text, a URL, an image, or a file, with a list, archive state, and
  created/edited dates. Run NSDataDetector on text so URLs, phone numbers, and dates
  become tappable.
- iOS: a share extension so anything can be sent in from any app, plus a WidgetKit
  widget for one-tap capture. Mac: a menu bar item with a global hotkey opening a
  compact capture window.
- Inbox, Archive, and lists, with full-text search and undoable archive/delete. JSON
  export of everything so my notes are never trapped.
- Export actions for the destinations I actually use: Reminders and Calendar via
  EventKit, a Mail draft, Things and Bear via their URL schemes, and copy-as-Markdown.
  One small adapter file per destination so more are addable later.
- Offline-first: SwiftData writes locally and CloudKit retries when back online.
  Last-write-wins conflict handling is fine, say so in the README.
- No accounts, no telemetry, nothing leaves my devices except private iCloud sync and
  the exports I trigger.
- Out of scope: Apple Watch and Vision Pro apps, and Capture's 40+ destination catalog.
  Keeping that many exporters alive is the paid product's job, not mine.
- README: the entitlements to enable (App Groups, iCloud/CloudKit), and a plain warning
  that CloudKit sync needs a paid Apple Developer account.

## Required capabilities

- Xcode
- Apple Developer account for iCloud and App Group entitlements

## 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 Capture - Quick Notes.

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 =====
# Capture - Quick Notes product brief

## Problem

The core capture inbox is a weekend build: everything runs on public Apple frameworks, so SwiftData plus CloudKit sync, a share extension, and a menu bar capture window cover the loop on iPhone and Mac. What is not a weekend is Capture's real surface: five Apple platforms and a catalog of 40+ destination exporters whose URL schemes, APIs, and content rules shift independently. Build the two-platform inbox with a handful of exporters you actually use and it is genuinely yours; chase full parity and you have signed up for the maintenance.

## Product outcome

Catch text, links, images, and files on iPhone and Mac, sync them through your private iCloud, organize them into lists, then send each item on to the apps you actually use via destination-specific export actions.

## Target user

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

## Required capabilities

- Xcode
- Apple Developer account for iCloud and App Group entitlements

## Explicit non-goals for v1

- App Store-ready polish across iPhone, iPad, Mac, Apple Watch, and Apple Vision Pro
- years of CloudKit migration, conflict, and offline-sync edge cases
- ongoing maintenance for more than 40 destination-specific export integrations
- the localization, accessibility, and device test matrix
- fast compatibility updates when Apple or a destination app changes behavior

## 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 me a native quick-capture inbox for iPhone and Mac to replace Capture. Requirements:

- Swift 6 + SwiftUI, one Xcode project: an iOS app and a macOS menu bar app sharing a
  Swift package for the model, persistence, search, and export logic. SwiftData for
  storage, synced through my private CloudKit database.
- A capture is text, a URL, an image, or a file, with a list, archive state, and
  created/edited dates. Run NSDataDetector on text so URLs, phone numbers, and dates
  become tappable.
- iOS: a share extension so anything can be sent in from any app, plus a WidgetKit
  widget for one-tap capture. Mac: a menu bar item with a global hotkey opening a
  compact capture window.
- Inbox, Archive, and lists, with full-text search and undoable archive/delete. JSON
  export of everything so my notes are never trapped.
- Export actions for the destinations I actually use: Reminders and Calendar via
  EventKit, a Mail draft, Things and Bear via their URL schemes, and copy-as-Markdown.
  One small adapter file per destination so more are addable later.
- Offline-first: SwiftData writes locally and CloudKit retries when back online.
  Last-write-wins conflict handling is fine, say so in the README.
- No accounts, no telemetry, nothing leaves my devices except private iCloud sync and
  the exports I trigger.
- Out of scope: Apple Watch and Vision Pro apps, and Capture's 40+ destination catalog.
  Keeping that many exporters alive is the paid product's job, not mine.
- README: the entitlements to enable (App Groups, iCloud/CloudKit), and a plain warning
  that CloudKit sync needs a paid Apple Developer account.

## 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 Capture - Quick Notes capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# Capture - Quick Notes indie build

## Goal

Build the smallest trustworthy replacement for the core Capture - Quick Notes workflow for one developer or a tiny team.

## Scope

Catch text, links, images, and files on iPhone and Mac, sync them through your private iCloud, organize them into lists, then send each item on to the apps you actually use via destination-specific export actions.

## 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:
- App Store-ready polish across iPhone, iPad, Mac, Apple Watch, and Apple Vision Pro
- years of CloudKit migration, conflict, and offline-sync edge cases
- ongoing maintenance for more than 40 destination-specific export integrations
- the localization, accessibility, and device test matrix
- fast compatibility updates when Apple or a destination app changes behavior

If those capabilities are essential, use FSNotes 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 me a native quick-capture inbox for iPhone and Mac to replace Capture. Requirements:

- Swift 6 + SwiftUI, one Xcode project: an iOS app and a macOS menu bar app sharing a
  Swift package for the model, persistence, search, and export logic. SwiftData for
  storage, synced through my private CloudKit database.
- A capture is text, a URL, an image, or a file, with a list, archive state, and
  created/edited dates. Run NSDataDetector on text so URLs, phone numbers, and dates
  become tappable.
- iOS: a share extension so anything can be sent in from any app, plus a WidgetKit
  widget for one-tap capture. Mac: a menu bar item with a global hotkey opening a
  compact capture window.
- Inbox, Archive, and lists, with full-text search and undoable archive/delete. JSON
  export of everything so my notes are never trapped.
- Export actions for the destinations I actually use: Reminders and Calendar via
  EventKit, a Mail draft, Things and Bear via their URL schemes, and copy-as-Markdown.
  One small adapter file per destination so more are addable later.
- Offline-first: SwiftData writes locally and CloudKit retries when back online.
  Last-write-wins conflict handling is fine, say so in the README.
- No accounts, no telemetry, nothing leaves my devices except private iCloud sync and
  the exports I trigger.
- Out of scope: Apple Watch and Vision Pro apps, and Capture's 40+ destination catalog.
  Keeping that many exporters alive is the paid product's job, not mine.
- README: the entitlements to enable (App Groups, iCloud/CloudKit), and a plain warning
  that CloudKit sync needs a paid Apple Developer account.

## Required capabilities

- Xcode
- Apple Developer account for iCloud and App Group entitlements

## 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.

# Capture - Quick Notes product brief

## Problem

The core capture inbox is a weekend build: everything runs on public Apple frameworks, so SwiftData plus CloudKit sync, a share extension, and a menu bar capture window cover the loop on iPhone and Mac. What is not a weekend is Capture's real surface: five Apple platforms and a catalog of 40+ destination exporters whose URL schemes, APIs, and content rules shift independently. Build the two-platform inbox with a handful of exporters you actually use and it is genuinely yours; chase full parity and you have signed up for the maintenance.

## Product outcome

Catch text, links, images, and files on iPhone and Mac, sync them through your private iCloud, organize them into lists, then send each item on to the apps you actually use via destination-specific export actions.

## Target user

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

## Required capabilities

- Xcode
- Apple Developer account for iCloud and App Group entitlements

## Explicit non-goals for v1

- App Store-ready polish across iPhone, iPad, Mac, Apple Watch, and Apple Vision Pro
- years of CloudKit migration, conflict, and offline-sync edge cases
- ongoing maintenance for more than 40 destination-specific export integrations
- the localization, accessibility, and device test matrix
- fast compatibility updates when Apple or a destination app changes behavior

## 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 me a native quick-capture inbox for iPhone and Mac to replace Capture. Requirements:

- Swift 6 + SwiftUI, one Xcode project: an iOS app and a macOS menu bar app sharing a
  Swift package for the model, persistence, search, and export logic. SwiftData for
  storage, synced through my private CloudKit database.
- A capture is text, a URL, an image, or a file, with a list, archive state, and
  created/edited dates. Run NSDataDetector on text so URLs, phone numbers, and dates
  become tappable.
- iOS: a share extension so anything can be sent in from any app, plus a WidgetKit
  widget for one-tap capture. Mac: a menu bar item with a global hotkey opening a
  compact capture window.
- Inbox, Archive, and lists, with full-text search and undoable archive/delete. JSON
  export of everything so my notes are never trapped.
- Export actions for the destinations I actually use: Reminders and Calendar via
  EventKit, a Mail draft, Things and Bear via their URL schemes, and copy-as-Markdown.
  One small adapter file per destination so more are addable later.
- Offline-first: SwiftData writes locally and CloudKit retries when back online.
  Last-write-wins conflict handling is fine, say so in the README.
- No accounts, no telemetry, nothing leaves my devices except private iCloud sync and
  the exports I trigger.
- Out of scope: Apple Watch and Vision Pro apps, and Capture's 40+ destination catalog.
  Keeping that many exporters alive is the paid product's job, not mine.
- README: the entitlements to enable (App Groups, iCloud/CloudKit), and a plain warning
  that CloudKit sync needs a paid Apple Developer account.

## 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 Capture - Quick Notes 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