Vibecode VHS Slipcover Maker

You are building a lean indie version of VHS Slipcover Maker.

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 =====
# VHS Slipcover Maker indie build

## Goal

Build the smallest trustworthy replacement for the core VHS Slipcover Maker workflow for one developer or a tiny team.

## Scope

Type a title, adjust fonts and colors, and print your own labels and covers for VHS tapes, DVDs, Cassettes, Vinyl and more.

## 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:
- 30+ measured dieline templates: cassette J-cards, CD inserts, vinyl jackets, Blu-ray and DVD wraps, MiniDisc
- movie and music search that auto-fills cover art and metadata
- designs that persist and share as a URL
- die-cut label-sheet PDFs aligned to vendor sticker stock
- 22 UI languages

If those capabilities are essential, use VHS Slipcover Maker 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 printable VHS slipcover maker to replace VHS Slipcover Maker (vhs.texs.org). Requirements:

- Vite + React + Tailwind, client-only, no server. State lives in the URL
  query string, omit any param still at its default; the URL is the save
  file and the share link. No database.
- Render the whole slipcover as one flat SVG die-cut wrap, 10.73 x 9.17 in:
  back panel, 1.05 in spine, front panel, each panel 7.4 in tall (the VHS
  case face height), plus fold-over flaps. Physical inches are the source
  of truth, derive every pixel value from them.
- Front panel: drag-and-drop cover art with zoom and pan, cropped to the
  panel, with the title over it. Spine: title rotated 90 degrees plus year
  and runtime. Back panel: a synopsis block, up to four screenshot
  thumbnails, and a fake barcode.
- Ink and background color pickers, five bundled retro Google Fonts, and
  three era presets: 80s rental store, 90s studio release, plain typewriter.
- Fold lines show on screen but never export; the printed sheet gets only a
  thin cut line around the outer die-cut perimeter.
- Export a Tabloid (11 x 17 in) PDF with pdf-lib at 600 DPI, plus a PNG via
  canvas. Printed at 100% scale the folded sleeve must fit a standard VHS
  tape.
- No accounts, no telemetry, everything runs in the browser.
- Out of scope: every other format (sticker labels, cassette J-cards, DVD,
  vinyl), movie-poster search, and saved-design accounts. Do not attempt
  Safari-specific SVG fixes, Safari paints foreignObject at the wrong
  scale and supporting it is a project of its own.
- README: fold order for assembling the sleeve, and a warning that most
  home printers stop at Letter, the wrap needs 11 x 17 cardstock or a
  print shop.

## Required capabilities

- a printer that takes 11 x 17 cardstock, or a print shop
- TMDB API key only if you add movie-poster search

## 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 VHS Slipcover Maker.

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 =====
# VHS Slipcover Maker indie build

## Goal

Build the smallest trustworthy replacement for the core VHS Slipcover Maker workflow for one developer or a tiny team.

## Scope

Type a title, adjust fonts and colors, and print your own labels and covers for VHS tapes, DVDs, Cassettes, Vinyl and more.

## 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:
- 30+ measured dieline templates: cassette J-cards, CD inserts, vinyl jackets, Blu-ray and DVD wraps, MiniDisc
- movie and music search that auto-fills cover art and metadata
- designs that persist and share as a URL
- die-cut label-sheet PDFs aligned to vendor sticker stock
- 22 UI languages

If those capabilities are essential, use VHS Slipcover Maker 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 printable VHS slipcover maker to replace VHS Slipcover Maker (vhs.texs.org). Requirements:

- Vite + React + Tailwind, client-only, no server. State lives in the URL
  query string, omit any param still at its default; the URL is the save
  file and the share link. No database.
- Render the whole slipcover as one flat SVG die-cut wrap, 10.73 x 9.17 in:
  back panel, 1.05 in spine, front panel, each panel 7.4 in tall (the VHS
  case face height), plus fold-over flaps. Physical inches are the source
  of truth, derive every pixel value from them.
- Front panel: drag-and-drop cover art with zoom and pan, cropped to the
  panel, with the title over it. Spine: title rotated 90 degrees plus year
  and runtime. Back panel: a synopsis block, up to four screenshot
  thumbnails, and a fake barcode.
- Ink and background color pickers, five bundled retro Google Fonts, and
  three era presets: 80s rental store, 90s studio release, plain typewriter.
- Fold lines show on screen but never export; the printed sheet gets only a
  thin cut line around the outer die-cut perimeter.
- Export a Tabloid (11 x 17 in) PDF with pdf-lib at 600 DPI, plus a PNG via
  canvas. Printed at 100% scale the folded sleeve must fit a standard VHS
  tape.
- No accounts, no telemetry, everything runs in the browser.
- Out of scope: every other format (sticker labels, cassette J-cards, DVD,
  vinyl), movie-poster search, and saved-design accounts. Do not attempt
  Safari-specific SVG fixes, Safari paints foreignObject at the wrong
  scale and supporting it is a project of its own.
- README: fold order for assembling the sleeve, and a warning that most
  home printers stop at Letter, the wrap needs 11 x 17 cardstock or a
  print shop.

## Required capabilities

- a printer that takes 11 x 17 cardstock, or a print shop
- TMDB API key only if you add movie-poster search

## 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 VHS Slipcover Maker.

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 =====
# VHS Slipcover Maker product brief

## Problem

The core loop, type a title and print a correctly sized VHS slipcover, is a one-session build. But the rich design possibilities, range of 30+ physical media types, 22+ languages supported, and instant generation of covers from a variety of media sources makes this a lengthy project to spin up on your own. That part is not coming out of one prompt.

## Product outcome

Type a title, adjust fonts and colors, and print your own labels and covers for VHS tapes, DVDs, Cassettes, Vinyl and more.

## Target user

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

## Required capabilities

- a printer that takes 11 x 17 cardstock, or a print shop
- TMDB API key only if you add movie-poster search

## Explicit non-goals for v1

- 30+ measured dieline templates: cassette J-cards, CD inserts, vinyl jackets, Blu-ray and DVD wraps, MiniDisc
- movie and music search that auto-fills cover art and metadata
- designs that persist and share as a URL
- die-cut label-sheet PDFs aligned to vendor sticker stock
- 22 UI languages

## 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 printable VHS slipcover maker to replace VHS Slipcover Maker (vhs.texs.org). Requirements:

- Vite + React + Tailwind, client-only, no server. State lives in the URL
  query string, omit any param still at its default; the URL is the save
  file and the share link. No database.
- Render the whole slipcover as one flat SVG die-cut wrap, 10.73 x 9.17 in:
  back panel, 1.05 in spine, front panel, each panel 7.4 in tall (the VHS
  case face height), plus fold-over flaps. Physical inches are the source
  of truth, derive every pixel value from them.
- Front panel: drag-and-drop cover art with zoom and pan, cropped to the
  panel, with the title over it. Spine: title rotated 90 degrees plus year
  and runtime. Back panel: a synopsis block, up to four screenshot
  thumbnails, and a fake barcode.
- Ink and background color pickers, five bundled retro Google Fonts, and
  three era presets: 80s rental store, 90s studio release, plain typewriter.
- Fold lines show on screen but never export; the printed sheet gets only a
  thin cut line around the outer die-cut perimeter.
- Export a Tabloid (11 x 17 in) PDF with pdf-lib at 600 DPI, plus a PNG via
  canvas. Printed at 100% scale the folded sleeve must fit a standard VHS
  tape.
- No accounts, no telemetry, everything runs in the browser.
- Out of scope: every other format (sticker labels, cassette J-cards, DVD,
  vinyl), movie-poster search, and saved-design accounts. Do not attempt
  Safari-specific SVG fixes, Safari paints foreignObject at the wrong
  scale and supporting it is a project of its own.
- README: fold order for assembling the sleeve, and a warning that most
  home printers stop at Letter, the wrap needs 11 x 17 cardstock or a
  print shop.

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

# VHS Slipcover Maker indie build

## Goal

Build the smallest trustworthy replacement for the core VHS Slipcover Maker workflow for one developer or a tiny team.

## Scope

Type a title, adjust fonts and colors, and print your own labels and covers for VHS tapes, DVDs, Cassettes, Vinyl and more.

## 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:
- 30+ measured dieline templates: cassette J-cards, CD inserts, vinyl jackets, Blu-ray and DVD wraps, MiniDisc
- movie and music search that auto-fills cover art and metadata
- designs that persist and share as a URL
- die-cut label-sheet PDFs aligned to vendor sticker stock
- 22 UI languages

If those capabilities are essential, use VHS Slipcover Maker 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 printable VHS slipcover maker to replace VHS Slipcover Maker (vhs.texs.org). Requirements:

- Vite + React + Tailwind, client-only, no server. State lives in the URL
  query string, omit any param still at its default; the URL is the save
  file and the share link. No database.
- Render the whole slipcover as one flat SVG die-cut wrap, 10.73 x 9.17 in:
  back panel, 1.05 in spine, front panel, each panel 7.4 in tall (the VHS
  case face height), plus fold-over flaps. Physical inches are the source
  of truth, derive every pixel value from them.
- Front panel: drag-and-drop cover art with zoom and pan, cropped to the
  panel, with the title over it. Spine: title rotated 90 degrees plus year
  and runtime. Back panel: a synopsis block, up to four screenshot
  thumbnails, and a fake barcode.
- Ink and background color pickers, five bundled retro Google Fonts, and
  three era presets: 80s rental store, 90s studio release, plain typewriter.
- Fold lines show on screen but never export; the printed sheet gets only a
  thin cut line around the outer die-cut perimeter.
- Export a Tabloid (11 x 17 in) PDF with pdf-lib at 600 DPI, plus a PNG via
  canvas. Printed at 100% scale the folded sleeve must fit a standard VHS
  tape.
- No accounts, no telemetry, everything runs in the browser.
- Out of scope: every other format (sticker labels, cassette J-cards, DVD,
  vinyl), movie-poster search, and saved-design accounts. Do not attempt
  Safari-specific SVG fixes, Safari paints foreignObject at the wrong
  scale and supporting it is a project of its own.
- README: fold order for assembling the sleeve, and a warning that most
  home printers stop at Letter, the wrap needs 11 x 17 cardstock or a
  print shop.

## Required capabilities

- a printer that takes 11 x 17 cardstock, or a print shop
- TMDB API key only if you add movie-poster search

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

# VHS Slipcover Maker product brief

## Problem

The core loop, type a title and print a correctly sized VHS slipcover, is a one-session build. But the rich design possibilities, range of 30+ physical media types, 22+ languages supported, and instant generation of covers from a variety of media sources makes this a lengthy project to spin up on your own. That part is not coming out of one prompt.

## Product outcome

Type a title, adjust fonts and colors, and print your own labels and covers for VHS tapes, DVDs, Cassettes, Vinyl and more.

## Target user

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

## Required capabilities

- a printer that takes 11 x 17 cardstock, or a print shop
- TMDB API key only if you add movie-poster search

## Explicit non-goals for v1

- 30+ measured dieline templates: cassette J-cards, CD inserts, vinyl jackets, Blu-ray and DVD wraps, MiniDisc
- movie and music search that auto-fills cover art and metadata
- designs that persist and share as a URL
- die-cut label-sheet PDFs aligned to vendor sticker stock
- 22 UI languages

## 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 printable VHS slipcover maker to replace VHS Slipcover Maker (vhs.texs.org). Requirements:

- Vite + React + Tailwind, client-only, no server. State lives in the URL
  query string, omit any param still at its default; the URL is the save
  file and the share link. No database.
- Render the whole slipcover as one flat SVG die-cut wrap, 10.73 x 9.17 in:
  back panel, 1.05 in spine, front panel, each panel 7.4 in tall (the VHS
  case face height), plus fold-over flaps. Physical inches are the source
  of truth, derive every pixel value from them.
- Front panel: drag-and-drop cover art with zoom and pan, cropped to the
  panel, with the title over it. Spine: title rotated 90 degrees plus year
  and runtime. Back panel: a synopsis block, up to four screenshot
  thumbnails, and a fake barcode.
- Ink and background color pickers, five bundled retro Google Fonts, and
  three era presets: 80s rental store, 90s studio release, plain typewriter.
- Fold lines show on screen but never export; the printed sheet gets only a
  thin cut line around the outer die-cut perimeter.
- Export a Tabloid (11 x 17 in) PDF with pdf-lib at 600 DPI, plus a PNG via
  canvas. Printed at 100% scale the folded sleeve must fit a standard VHS
  tape.
- No accounts, no telemetry, everything runs in the browser.
- Out of scope: every other format (sticker labels, cassette J-cards, DVD,
  vinyl), movie-poster search, and saved-design accounts. Do not attempt
  Safari-specific SVG fixes, Safari paints foreignObject at the wrong
  scale and supporting it is a project of its own.
- README: fold order for assembling the sleeve, and a warning that most
  home printers stop at Letter, the wrap needs 11 x 17 cardstock or a
  print shop.

## 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 VHS Slipcover Maker 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