Vibecode Snapchat

You are building a lean indie version of Snapchat.

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

## Goal

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

## Scope

Snap a photo with a caption overlay and send it to an invited friend group; each snap deletes after one timed view, with daily streaks and 24-hour group stories.

## 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:
- the people: everyone you snap with is on Snapchat, not on your server
- AR lenses and filters backed by years of face-tracking models
- screenshot detection · a web app cannot see or stop screenshots
- Snap Map, Discover, Spotlight and the creator ecosystem
- reliable mobile push · web push on iOS is best-effort, not messenger-grade

If those capabilities are essential, use Signal 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 private ephemeral photo-messaging app, snaps for one friend group that opts in. Requirements:

- Node 22 + Fastify + better-sqlite3, and a vanilla-JS installable PWA served from
  /public with no build step: manifest, service worker, an offline shell that caches
  the UI but never caches snaps.
- Core loop: open the camera with getUserMedia, capture a photo, type or draw a
  caption overlay on a canvas, send it to one or more friends.
- A snap is viewable exactly once for up to 10 seconds; the server deletes the image
  file immediately after the view and keeps only a minimal sent/opened log row.
- Accounts are invite-code only: the admin seeds codes with a CLI script, signup is
  username plus passcode, sessions are httpOnly cookies.
- Per-pair daily streaks tracked server-side, shown next to each friend.
- Group stories: a snap posted to my story is visible to all members and hard-deleted
  after 24 hours by a sweep job.
- Media lives as files on disk outside the web root; metadata in SQLite with WAL mode.
- Web push for new snaps behind a permission prompt; the app must work fully without
  it, and the README says iOS web push is best-effort. VAPID keys and session secret
  in .env, with a documented script that generates them and a .env.example.
- HTTPS is required for camera and push: document local dev with a self-signed cert
  and production behind Caddy on a cheap VPS.
- Be honest in the UI: label view-once as deleted from our server, and state plainly
  that screenshots cannot be detected on the web.
- Tests for delete-after-view, the 24-hour story sweep, and streak day-boundary math
  with a fake clock.
- Out of scope: AR lenses and face filters, Snap Map, Discover or Spotlight feeds,
  video calls, screenshot detection, analytics, and third-party auth.
- README: setup, deploying, where data lives, how deletion actually works, and how
  to invite the first two friends.

## Required capabilities

- a small VPS or free-tier Node host with HTTPS (camera and push APIs require it)
- friends willing to install the PWA and actually use it

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

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

## Goal

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

## Scope

Snap a photo with a caption overlay and send it to an invited friend group; each snap deletes after one timed view, with daily streaks and 24-hour group stories.

## 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:
- the people: everyone you snap with is on Snapchat, not on your server
- AR lenses and filters backed by years of face-tracking models
- screenshot detection · a web app cannot see or stop screenshots
- Snap Map, Discover, Spotlight and the creator ecosystem
- reliable mobile push · web push on iOS is best-effort, not messenger-grade

If those capabilities are essential, use Signal 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 private ephemeral photo-messaging app, snaps for one friend group that opts in. Requirements:

- Node 22 + Fastify + better-sqlite3, and a vanilla-JS installable PWA served from
  /public with no build step: manifest, service worker, an offline shell that caches
  the UI but never caches snaps.
- Core loop: open the camera with getUserMedia, capture a photo, type or draw a
  caption overlay on a canvas, send it to one or more friends.
- A snap is viewable exactly once for up to 10 seconds; the server deletes the image
  file immediately after the view and keeps only a minimal sent/opened log row.
- Accounts are invite-code only: the admin seeds codes with a CLI script, signup is
  username plus passcode, sessions are httpOnly cookies.
- Per-pair daily streaks tracked server-side, shown next to each friend.
- Group stories: a snap posted to my story is visible to all members and hard-deleted
  after 24 hours by a sweep job.
- Media lives as files on disk outside the web root; metadata in SQLite with WAL mode.
- Web push for new snaps behind a permission prompt; the app must work fully without
  it, and the README says iOS web push is best-effort. VAPID keys and session secret
  in .env, with a documented script that generates them and a .env.example.
- HTTPS is required for camera and push: document local dev with a self-signed cert
  and production behind Caddy on a cheap VPS.
- Be honest in the UI: label view-once as deleted from our server, and state plainly
  that screenshots cannot be detected on the web.
- Tests for delete-after-view, the 24-hour story sweep, and streak day-boundary math
  with a fake clock.
- Out of scope: AR lenses and face filters, Snap Map, Discover or Spotlight feeds,
  video calls, screenshot detection, analytics, and third-party auth.
- README: setup, deploying, where data lives, how deletion actually works, and how
  to invite the first two friends.

## Required capabilities

- a small VPS or free-tier Node host with HTTPS (camera and push APIs require it)
- friends willing to install the PWA and actually use it

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

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

## Problem

The mechanics one-shot fine: ephemeral photo messages, 24-hour stories and streak counters are CRUD plus a delete timer. None of that is the product. Snapchat is where your friends already are · the value of a disappearing photo is who is on the other end, and a self-hosted clone with two users is a group chat with extra steps. Add the AR lens stack built on years of face-tracking models, screenshot detection that needs OS-level app privileges, and media infrastructure moving billions of snaps a day, and the honest verdict is that the network is the app. The prompt below is the consolation build: a private snap relay for one friend group that opts in.

## Product outcome

Snap a photo with a caption overlay and send it to an invited friend group; each snap deletes after one timed view, with daily streaks and 24-hour group stories.

## Target user

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

## Required capabilities

- a small VPS or free-tier Node host with HTTPS (camera and push APIs require it)
- friends willing to install the PWA and actually use it

## Explicit non-goals for v1

- the people: everyone you snap with is on Snapchat, not on your server
- AR lenses and filters backed by years of face-tracking models
- screenshot detection · a web app cannot see or stop screenshots
- Snap Map, Discover, Spotlight and the creator ecosystem
- reliable mobile push · web push on iOS is best-effort, not messenger-grade

## 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 private ephemeral photo-messaging app, snaps for one friend group that opts in. Requirements:

- Node 22 + Fastify + better-sqlite3, and a vanilla-JS installable PWA served from
  /public with no build step: manifest, service worker, an offline shell that caches
  the UI but never caches snaps.
- Core loop: open the camera with getUserMedia, capture a photo, type or draw a
  caption overlay on a canvas, send it to one or more friends.
- A snap is viewable exactly once for up to 10 seconds; the server deletes the image
  file immediately after the view and keeps only a minimal sent/opened log row.
- Accounts are invite-code only: the admin seeds codes with a CLI script, signup is
  username plus passcode, sessions are httpOnly cookies.
- Per-pair daily streaks tracked server-side, shown next to each friend.
- Group stories: a snap posted to my story is visible to all members and hard-deleted
  after 24 hours by a sweep job.
- Media lives as files on disk outside the web root; metadata in SQLite with WAL mode.
- Web push for new snaps behind a permission prompt; the app must work fully without
  it, and the README says iOS web push is best-effort. VAPID keys and session secret
  in .env, with a documented script that generates them and a .env.example.
- HTTPS is required for camera and push: document local dev with a self-signed cert
  and production behind Caddy on a cheap VPS.
- Be honest in the UI: label view-once as deleted from our server, and state plainly
  that screenshots cannot be detected on the web.
- Tests for delete-after-view, the 24-hour story sweep, and streak day-boundary math
  with a fake clock.
- Out of scope: AR lenses and face filters, Snap Map, Discover or Spotlight feeds,
  video calls, screenshot detection, analytics, and third-party auth.
- README: setup, deploying, where data lives, how deletion actually works, and how
  to invite the first two friends.

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

# Snapchat indie build

## Goal

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

## Scope

Snap a photo with a caption overlay and send it to an invited friend group; each snap deletes after one timed view, with daily streaks and 24-hour group stories.

## 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:
- the people: everyone you snap with is on Snapchat, not on your server
- AR lenses and filters backed by years of face-tracking models
- screenshot detection · a web app cannot see or stop screenshots
- Snap Map, Discover, Spotlight and the creator ecosystem
- reliable mobile push · web push on iOS is best-effort, not messenger-grade

If those capabilities are essential, use Signal 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 private ephemeral photo-messaging app, snaps for one friend group that opts in. Requirements:

- Node 22 + Fastify + better-sqlite3, and a vanilla-JS installable PWA served from
  /public with no build step: manifest, service worker, an offline shell that caches
  the UI but never caches snaps.
- Core loop: open the camera with getUserMedia, capture a photo, type or draw a
  caption overlay on a canvas, send it to one or more friends.
- A snap is viewable exactly once for up to 10 seconds; the server deletes the image
  file immediately after the view and keeps only a minimal sent/opened log row.
- Accounts are invite-code only: the admin seeds codes with a CLI script, signup is
  username plus passcode, sessions are httpOnly cookies.
- Per-pair daily streaks tracked server-side, shown next to each friend.
- Group stories: a snap posted to my story is visible to all members and hard-deleted
  after 24 hours by a sweep job.
- Media lives as files on disk outside the web root; metadata in SQLite with WAL mode.
- Web push for new snaps behind a permission prompt; the app must work fully without
  it, and the README says iOS web push is best-effort. VAPID keys and session secret
  in .env, with a documented script that generates them and a .env.example.
- HTTPS is required for camera and push: document local dev with a self-signed cert
  and production behind Caddy on a cheap VPS.
- Be honest in the UI: label view-once as deleted from our server, and state plainly
  that screenshots cannot be detected on the web.
- Tests for delete-after-view, the 24-hour story sweep, and streak day-boundary math
  with a fake clock.
- Out of scope: AR lenses and face filters, Snap Map, Discover or Spotlight feeds,
  video calls, screenshot detection, analytics, and third-party auth.
- README: setup, deploying, where data lives, how deletion actually works, and how
  to invite the first two friends.

## Required capabilities

- a small VPS or free-tier Node host with HTTPS (camera and push APIs require it)
- friends willing to install the PWA and actually use it

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

# Snapchat product brief

## Problem

The mechanics one-shot fine: ephemeral photo messages, 24-hour stories and streak counters are CRUD plus a delete timer. None of that is the product. Snapchat is where your friends already are · the value of a disappearing photo is who is on the other end, and a self-hosted clone with two users is a group chat with extra steps. Add the AR lens stack built on years of face-tracking models, screenshot detection that needs OS-level app privileges, and media infrastructure moving billions of snaps a day, and the honest verdict is that the network is the app. The prompt below is the consolation build: a private snap relay for one friend group that opts in.

## Product outcome

Snap a photo with a caption overlay and send it to an invited friend group; each snap deletes after one timed view, with daily streaks and 24-hour group stories.

## Target user

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

## Required capabilities

- a small VPS or free-tier Node host with HTTPS (camera and push APIs require it)
- friends willing to install the PWA and actually use it

## Explicit non-goals for v1

- the people: everyone you snap with is on Snapchat, not on your server
- AR lenses and filters backed by years of face-tracking models
- screenshot detection · a web app cannot see or stop screenshots
- Snap Map, Discover, Spotlight and the creator ecosystem
- reliable mobile push · web push on iOS is best-effort, not messenger-grade

## 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 private ephemeral photo-messaging app, snaps for one friend group that opts in. Requirements:

- Node 22 + Fastify + better-sqlite3, and a vanilla-JS installable PWA served from
  /public with no build step: manifest, service worker, an offline shell that caches
  the UI but never caches snaps.
- Core loop: open the camera with getUserMedia, capture a photo, type or draw a
  caption overlay on a canvas, send it to one or more friends.
- A snap is viewable exactly once for up to 10 seconds; the server deletes the image
  file immediately after the view and keeps only a minimal sent/opened log row.
- Accounts are invite-code only: the admin seeds codes with a CLI script, signup is
  username plus passcode, sessions are httpOnly cookies.
- Per-pair daily streaks tracked server-side, shown next to each friend.
- Group stories: a snap posted to my story is visible to all members and hard-deleted
  after 24 hours by a sweep job.
- Media lives as files on disk outside the web root; metadata in SQLite with WAL mode.
- Web push for new snaps behind a permission prompt; the app must work fully without
  it, and the README says iOS web push is best-effort. VAPID keys and session secret
  in .env, with a documented script that generates them and a .env.example.
- HTTPS is required for camera and push: document local dev with a self-signed cert
  and production behind Caddy on a cheap VPS.
- Be honest in the UI: label view-once as deleted from our server, and state plainly
  that screenshots cannot be detected on the web.
- Tests for delete-after-view, the 24-hour story sweep, and streak day-boundary math
  with a fake clock.
- Out of scope: AR lenses and face filters, Snap Map, Discover or Spotlight feeds,
  video calls, screenshot detection, analytics, and third-party auth.
- README: setup, deploying, where data lives, how deletion actually works, and how
  to invite the first two friends.

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