Vibecode GatherOS

You are building a lean indie version of GatherOS.

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 =====
# GatherOS indie build

## Goal

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

## Scope

Capture images, screenshots, pasted files, and URLs into a private local library, organize them with collections and tags, then find them by text, color, or optional semantic search.

## 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:
- X, Instagram, and Cosmos bookmark imports with their platform-specific backfill and dedup pipelines
- the browser extension and native messaging bridge for one-click capture from any site
- the finished AI pipeline's provider maintenance and results without supplying my own OpenAI key
- the mature Spaces canvas, presentation mode, and board export polish
- mobile clients, multi-device sync, and long-term update and support plumbing

If those capabilities are essential, use Pinry 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 personal visual reference library for macOS to replace GatherOS. Requirements:

- Use Electron + React + TypeScript + Vite with better-sqlite3, sharp, and node-vibrant; do not offer alternative stacks.
- Make the core loop work end to end: paste or drag in an image, save a screenshot with Command+Shift+S, or paste a URL, then keep the original, thumbnail, title, source URL, and content hash.
- Store metadata in SQLite and media under ~/Library/Application Support/ReferenceShelf/; include collections, tags, notes, soft-delete trash, ZIP export, and a restore-safe backup command.
- Show a keyboard-friendly masonry library with All, Unsorted, and Trash views, bulk tag or collection actions, an item detail panel, and a source link.
- Add SQLite FTS5 search for title, source, notes, and tags, plus palette extraction with color filters;
  keep these working with no network or AI.
- Add one bounded Spaces board with pan, zoom, image cards, text, sticky notes, shapes, autosave, and PNG export;
  store board positions as JSON.
- Use an optional OpenAI API key from .env for title, tag, and embedding jobs; if the key is absent,
  show a clear disabled state and keep the local search usable.
- No accounts, no telemetry, no cloud sync, and everything stays on my Mac except explicit OpenAI calls.
- Out of scope: X, Instagram, and Cosmos imports, mobile clients, multi-device sync, and the full browser-extension/native-messaging bridge;
  keep URL capture as paste or drag.
- Include a README with install commands, Screen Recording permission steps, the data directory, backup and export instructions,
  OpenAI data handling, tests, and known limitations.

## Required capabilities

- macOS 13+
- Node.js 22 and an Electron toolchain
- Screen Recording permission for global capture
- optional OpenAI API key in .env for AI features

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

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 =====
# GatherOS indie build

## Goal

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

## Scope

Capture images, screenshots, pasted files, and URLs into a private local library, organize them with collections and tags, then find them by text, color, or optional semantic search.

## 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:
- X, Instagram, and Cosmos bookmark imports with their platform-specific backfill and dedup pipelines
- the browser extension and native messaging bridge for one-click capture from any site
- the finished AI pipeline's provider maintenance and results without supplying my own OpenAI key
- the mature Spaces canvas, presentation mode, and board export polish
- mobile clients, multi-device sync, and long-term update and support plumbing

If those capabilities are essential, use Pinry 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 personal visual reference library for macOS to replace GatherOS. Requirements:

- Use Electron + React + TypeScript + Vite with better-sqlite3, sharp, and node-vibrant; do not offer alternative stacks.
- Make the core loop work end to end: paste or drag in an image, save a screenshot with Command+Shift+S, or paste a URL, then keep the original, thumbnail, title, source URL, and content hash.
- Store metadata in SQLite and media under ~/Library/Application Support/ReferenceShelf/; include collections, tags, notes, soft-delete trash, ZIP export, and a restore-safe backup command.
- Show a keyboard-friendly masonry library with All, Unsorted, and Trash views, bulk tag or collection actions, an item detail panel, and a source link.
- Add SQLite FTS5 search for title, source, notes, and tags, plus palette extraction with color filters;
  keep these working with no network or AI.
- Add one bounded Spaces board with pan, zoom, image cards, text, sticky notes, shapes, autosave, and PNG export;
  store board positions as JSON.
- Use an optional OpenAI API key from .env for title, tag, and embedding jobs; if the key is absent,
  show a clear disabled state and keep the local search usable.
- No accounts, no telemetry, no cloud sync, and everything stays on my Mac except explicit OpenAI calls.
- Out of scope: X, Instagram, and Cosmos imports, mobile clients, multi-device sync, and the full browser-extension/native-messaging bridge;
  keep URL capture as paste or drag.
- Include a README with install commands, Screen Recording permission steps, the data directory, backup and export instructions,
  OpenAI data handling, tests, and known limitations.

## Required capabilities

- macOS 13+
- Node.js 22 and an Electron toolchain
- Screen Recording permission for global capture
- optional OpenAI API key in .env for AI features

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

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 =====
# GatherOS product brief

## Problem

GatherOS's solo library is buildable, but a credible replacement is a weekend or multi-day project rather than a one-shot form. The visible grid, collections, tags, palettes, local SQLite files, and a basic board are approachable. The harder gaps are native macOS capture, the browser extension, X/Instagram/Cosmos imports, semantic AI, and interaction polish. A narrow local app is useful; call it a personal substitute, not feature parity.

## Product outcome

Capture images, screenshots, pasted files, and URLs into a private local library, organize them with collections and tags, then find them by text, color, or optional semantic search.

## Target user

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

## Required capabilities

- macOS 13+
- Node.js 22 and an Electron toolchain
- Screen Recording permission for global capture
- optional OpenAI API key in .env for AI features

## Explicit non-goals for v1

- X, Instagram, and Cosmos bookmark imports with their platform-specific backfill and dedup pipelines
- the browser extension and native messaging bridge for one-click capture from any site
- the finished AI pipeline's provider maintenance and results without supplying my own OpenAI key
- the mature Spaces canvas, presentation mode, and board export polish
- mobile clients, multi-device sync, and long-term update and support plumbing

## 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 personal visual reference library for macOS to replace GatherOS. Requirements:

- Use Electron + React + TypeScript + Vite with better-sqlite3, sharp, and node-vibrant; do not offer alternative stacks.
- Make the core loop work end to end: paste or drag in an image, save a screenshot with Command+Shift+S, or paste a URL, then keep the original, thumbnail, title, source URL, and content hash.
- Store metadata in SQLite and media under ~/Library/Application Support/ReferenceShelf/; include collections, tags, notes, soft-delete trash, ZIP export, and a restore-safe backup command.
- Show a keyboard-friendly masonry library with All, Unsorted, and Trash views, bulk tag or collection actions, an item detail panel, and a source link.
- Add SQLite FTS5 search for title, source, notes, and tags, plus palette extraction with color filters;
  keep these working with no network or AI.
- Add one bounded Spaces board with pan, zoom, image cards, text, sticky notes, shapes, autosave, and PNG export;
  store board positions as JSON.
- Use an optional OpenAI API key from .env for title, tag, and embedding jobs; if the key is absent,
  show a clear disabled state and keep the local search usable.
- No accounts, no telemetry, no cloud sync, and everything stays on my Mac except explicit OpenAI calls.
- Out of scope: X, Instagram, and Cosmos imports, mobile clients, multi-device sync, and the full browser-extension/native-messaging bridge;
  keep URL capture as paste or drag.
- Include a README with install commands, Screen Recording permission steps, the data directory, backup and export instructions,
  OpenAI data handling, tests, and known limitations.

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

# GatherOS indie build

## Goal

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

## Scope

Capture images, screenshots, pasted files, and URLs into a private local library, organize them with collections and tags, then find them by text, color, or optional semantic search.

## 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:
- X, Instagram, and Cosmos bookmark imports with their platform-specific backfill and dedup pipelines
- the browser extension and native messaging bridge for one-click capture from any site
- the finished AI pipeline's provider maintenance and results without supplying my own OpenAI key
- the mature Spaces canvas, presentation mode, and board export polish
- mobile clients, multi-device sync, and long-term update and support plumbing

If those capabilities are essential, use Pinry 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 personal visual reference library for macOS to replace GatherOS. Requirements:

- Use Electron + React + TypeScript + Vite with better-sqlite3, sharp, and node-vibrant; do not offer alternative stacks.
- Make the core loop work end to end: paste or drag in an image, save a screenshot with Command+Shift+S, or paste a URL, then keep the original, thumbnail, title, source URL, and content hash.
- Store metadata in SQLite and media under ~/Library/Application Support/ReferenceShelf/; include collections, tags, notes, soft-delete trash, ZIP export, and a restore-safe backup command.
- Show a keyboard-friendly masonry library with All, Unsorted, and Trash views, bulk tag or collection actions, an item detail panel, and a source link.
- Add SQLite FTS5 search for title, source, notes, and tags, plus palette extraction with color filters;
  keep these working with no network or AI.
- Add one bounded Spaces board with pan, zoom, image cards, text, sticky notes, shapes, autosave, and PNG export;
  store board positions as JSON.
- Use an optional OpenAI API key from .env for title, tag, and embedding jobs; if the key is absent,
  show a clear disabled state and keep the local search usable.
- No accounts, no telemetry, no cloud sync, and everything stays on my Mac except explicit OpenAI calls.
- Out of scope: X, Instagram, and Cosmos imports, mobile clients, multi-device sync, and the full browser-extension/native-messaging bridge;
  keep URL capture as paste or drag.
- Include a README with install commands, Screen Recording permission steps, the data directory, backup and export instructions,
  OpenAI data handling, tests, and known limitations.

## Required capabilities

- macOS 13+
- Node.js 22 and an Electron toolchain
- Screen Recording permission for global capture
- optional OpenAI API key in .env for AI features

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

# GatherOS product brief

## Problem

GatherOS's solo library is buildable, but a credible replacement is a weekend or multi-day project rather than a one-shot form. The visible grid, collections, tags, palettes, local SQLite files, and a basic board are approachable. The harder gaps are native macOS capture, the browser extension, X/Instagram/Cosmos imports, semantic AI, and interaction polish. A narrow local app is useful; call it a personal substitute, not feature parity.

## Product outcome

Capture images, screenshots, pasted files, and URLs into a private local library, organize them with collections and tags, then find them by text, color, or optional semantic search.

## Target user

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

## Required capabilities

- macOS 13+
- Node.js 22 and an Electron toolchain
- Screen Recording permission for global capture
- optional OpenAI API key in .env for AI features

## Explicit non-goals for v1

- X, Instagram, and Cosmos bookmark imports with their platform-specific backfill and dedup pipelines
- the browser extension and native messaging bridge for one-click capture from any site
- the finished AI pipeline's provider maintenance and results without supplying my own OpenAI key
- the mature Spaces canvas, presentation mode, and board export polish
- mobile clients, multi-device sync, and long-term update and support plumbing

## 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 personal visual reference library for macOS to replace GatherOS. Requirements:

- Use Electron + React + TypeScript + Vite with better-sqlite3, sharp, and node-vibrant; do not offer alternative stacks.
- Make the core loop work end to end: paste or drag in an image, save a screenshot with Command+Shift+S, or paste a URL, then keep the original, thumbnail, title, source URL, and content hash.
- Store metadata in SQLite and media under ~/Library/Application Support/ReferenceShelf/; include collections, tags, notes, soft-delete trash, ZIP export, and a restore-safe backup command.
- Show a keyboard-friendly masonry library with All, Unsorted, and Trash views, bulk tag or collection actions, an item detail panel, and a source link.
- Add SQLite FTS5 search for title, source, notes, and tags, plus palette extraction with color filters;
  keep these working with no network or AI.
- Add one bounded Spaces board with pan, zoom, image cards, text, sticky notes, shapes, autosave, and PNG export;
  store board positions as JSON.
- Use an optional OpenAI API key from .env for title, tag, and embedding jobs; if the key is absent,
  show a clear disabled state and keep the local search usable.
- No accounts, no telemetry, no cloud sync, and everything stays on my Mac except explicit OpenAI calls.
- Out of scope: X, Instagram, and Cosmos imports, mobile clients, multi-device sync, and the full browser-extension/native-messaging bridge;
  keep URL capture as paste or drag.
- Include a README with install commands, Screen Recording permission steps, the data directory, backup and export instructions,
  OpenAI data handling, tests, and known limitations.

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