Vibecode ScreenshotOne

You are building a lean indie version of ScreenshotOne.

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

## Goal

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

## Scope

Send a URL or HTML to an authenticated HTTP endpoint and receive a cached PNG, JPEG, WebP, or PDF rendered by a local Chrome/Chromium worker.

## 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:
- managed browser capacity, rate limiting, and high availability
- maintained ad, cookie banner, chat widget, and popup blocking rules
- residential proxies, selectable IP locations, and stealth tuning
- scrolling screenshots, video generation, and GPU rendering
- production support for difficult sites and browser edge cases

If those capabilities are essential, use Gotenberg 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 self-hosted website screenshot API to replace ScreenshotOne for personal use. Requirements:

- Node 22 + Fastify + Playwright (Chromium) + better-sqlite3, one process, no queue system.
- GET /take?url=&format=png|jpeg|webp|pdf&width=&height=&full_page=&delay_ms= renders the
  page in a pooled Chromium context and returns the image bytes directly.
- POST /take accepts raw HTML or Markdown in the body and renders that instead
  (Markdown through marked into a plain template).
- Auth is one API key from .env, checked on every request; 401 without it.
- Cache by hash of the normalized options: metadata in SQLite, files under data/cache/,
  with a cache_ttl option and a fresh=true bypass.
- Block ads and cookie banners the honest way: load EasyList and the
  "I don't care about cookies" filter list at startup, apply them via request
  interception, plus a small CSS hide-list for common consent overlays. Do not
  promise it catches everything.
- Hard 15-second navigation timeout, one retry, then a JSON error with the reason;
  never a hanging request.
- Concurrency capped at a small context pool (default 2) with an in-memory queue,
  so the box does not fall over.
- Out of scope: proxies and IP locations, stealth evasion, scrolling video capture,
  GPU rendering, dashboards, usage billing. That fleet is the paid product.
- README: npx playwright install chromium, .env keys, Chromium memory expectations,
  and a one-line warning that hostile sites will beat this build.

## Required capabilities

- Docker
- a machine with enough memory to run Chrome/Chromium

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

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

## Goal

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

## Scope

Send a URL or HTML to an authenticated HTTP endpoint and receive a cached PNG, JPEG, WebP, or PDF rendered by a local Chrome/Chromium worker.

## 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:
- managed browser capacity, rate limiting, and high availability
- maintained ad, cookie banner, chat widget, and popup blocking rules
- residential proxies, selectable IP locations, and stealth tuning
- scrolling screenshots, video generation, and GPU rendering
- production support for difficult sites and browser edge cases

If those capabilities are essential, use Gotenberg 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 self-hosted website screenshot API to replace ScreenshotOne for personal use. Requirements:

- Node 22 + Fastify + Playwright (Chromium) + better-sqlite3, one process, no queue system.
- GET /take?url=&format=png|jpeg|webp|pdf&width=&height=&full_page=&delay_ms= renders the
  page in a pooled Chromium context and returns the image bytes directly.
- POST /take accepts raw HTML or Markdown in the body and renders that instead
  (Markdown through marked into a plain template).
- Auth is one API key from .env, checked on every request; 401 without it.
- Cache by hash of the normalized options: metadata in SQLite, files under data/cache/,
  with a cache_ttl option and a fresh=true bypass.
- Block ads and cookie banners the honest way: load EasyList and the
  "I don't care about cookies" filter list at startup, apply them via request
  interception, plus a small CSS hide-list for common consent overlays. Do not
  promise it catches everything.
- Hard 15-second navigation timeout, one retry, then a JSON error with the reason;
  never a hanging request.
- Concurrency capped at a small context pool (default 2) with an in-memory queue,
  so the box does not fall over.
- Out of scope: proxies and IP locations, stealth evasion, scrolling video capture,
  GPU rendering, dashboards, usage billing. That fleet is the paid product.
- README: npx playwright install chromium, .env keys, Chromium memory expectations,
  and a one-line warning that hostile sites will beat this build.

## Required capabilities

- Docker
- a machine with enough memory to run Chrome/Chromium

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

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

## Problem

A competent coding agent can build a useful self-hosted screenshot endpoint around Playwright in a weekend. Matching ScreenshotOne's reliable browser fleet, proxy locations, stealth behavior, maintained blocking rules, videos, and production edge-case handling is a much larger infrastructure product.

## Product outcome

Send a URL or HTML to an authenticated HTTP endpoint and receive a cached PNG, JPEG, WebP, or PDF rendered by a local Chrome/Chromium worker.

## Target user

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

## Required capabilities

- Docker
- a machine with enough memory to run Chrome/Chromium

## Explicit non-goals for v1

- managed browser capacity, rate limiting, and high availability
- maintained ad, cookie banner, chat widget, and popup blocking rules
- residential proxies, selectable IP locations, and stealth tuning
- scrolling screenshots, video generation, and GPU rendering
- production support for difficult sites and browser edge cases

## 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 self-hosted website screenshot API to replace ScreenshotOne for personal use. Requirements:

- Node 22 + Fastify + Playwright (Chromium) + better-sqlite3, one process, no queue system.
- GET /take?url=&format=png|jpeg|webp|pdf&width=&height=&full_page=&delay_ms= renders the
  page in a pooled Chromium context and returns the image bytes directly.
- POST /take accepts raw HTML or Markdown in the body and renders that instead
  (Markdown through marked into a plain template).
- Auth is one API key from .env, checked on every request; 401 without it.
- Cache by hash of the normalized options: metadata in SQLite, files under data/cache/,
  with a cache_ttl option and a fresh=true bypass.
- Block ads and cookie banners the honest way: load EasyList and the
  "I don't care about cookies" filter list at startup, apply them via request
  interception, plus a small CSS hide-list for common consent overlays. Do not
  promise it catches everything.
- Hard 15-second navigation timeout, one retry, then a JSON error with the reason;
  never a hanging request.
- Concurrency capped at a small context pool (default 2) with an in-memory queue,
  so the box does not fall over.
- Out of scope: proxies and IP locations, stealth evasion, scrolling video capture,
  GPU rendering, dashboards, usage billing. That fleet is the paid product.
- README: npx playwright install chromium, .env keys, Chromium memory expectations,
  and a one-line warning that hostile sites will beat this build.

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

# ScreenshotOne indie build

## Goal

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

## Scope

Send a URL or HTML to an authenticated HTTP endpoint and receive a cached PNG, JPEG, WebP, or PDF rendered by a local Chrome/Chromium worker.

## 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:
- managed browser capacity, rate limiting, and high availability
- maintained ad, cookie banner, chat widget, and popup blocking rules
- residential proxies, selectable IP locations, and stealth tuning
- scrolling screenshots, video generation, and GPU rendering
- production support for difficult sites and browser edge cases

If those capabilities are essential, use Gotenberg 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 self-hosted website screenshot API to replace ScreenshotOne for personal use. Requirements:

- Node 22 + Fastify + Playwright (Chromium) + better-sqlite3, one process, no queue system.
- GET /take?url=&format=png|jpeg|webp|pdf&width=&height=&full_page=&delay_ms= renders the
  page in a pooled Chromium context and returns the image bytes directly.
- POST /take accepts raw HTML or Markdown in the body and renders that instead
  (Markdown through marked into a plain template).
- Auth is one API key from .env, checked on every request; 401 without it.
- Cache by hash of the normalized options: metadata in SQLite, files under data/cache/,
  with a cache_ttl option and a fresh=true bypass.
- Block ads and cookie banners the honest way: load EasyList and the
  "I don't care about cookies" filter list at startup, apply them via request
  interception, plus a small CSS hide-list for common consent overlays. Do not
  promise it catches everything.
- Hard 15-second navigation timeout, one retry, then a JSON error with the reason;
  never a hanging request.
- Concurrency capped at a small context pool (default 2) with an in-memory queue,
  so the box does not fall over.
- Out of scope: proxies and IP locations, stealth evasion, scrolling video capture,
  GPU rendering, dashboards, usage billing. That fleet is the paid product.
- README: npx playwright install chromium, .env keys, Chromium memory expectations,
  and a one-line warning that hostile sites will beat this build.

## Required capabilities

- Docker
- a machine with enough memory to run Chrome/Chromium

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

# ScreenshotOne product brief

## Problem

A competent coding agent can build a useful self-hosted screenshot endpoint around Playwright in a weekend. Matching ScreenshotOne's reliable browser fleet, proxy locations, stealth behavior, maintained blocking rules, videos, and production edge-case handling is a much larger infrastructure product.

## Product outcome

Send a URL or HTML to an authenticated HTTP endpoint and receive a cached PNG, JPEG, WebP, or PDF rendered by a local Chrome/Chromium worker.

## Target user

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

## Required capabilities

- Docker
- a machine with enough memory to run Chrome/Chromium

## Explicit non-goals for v1

- managed browser capacity, rate limiting, and high availability
- maintained ad, cookie banner, chat widget, and popup blocking rules
- residential proxies, selectable IP locations, and stealth tuning
- scrolling screenshots, video generation, and GPU rendering
- production support for difficult sites and browser edge cases

## 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 self-hosted website screenshot API to replace ScreenshotOne for personal use. Requirements:

- Node 22 + Fastify + Playwright (Chromium) + better-sqlite3, one process, no queue system.
- GET /take?url=&format=png|jpeg|webp|pdf&width=&height=&full_page=&delay_ms= renders the
  page in a pooled Chromium context and returns the image bytes directly.
- POST /take accepts raw HTML or Markdown in the body and renders that instead
  (Markdown through marked into a plain template).
- Auth is one API key from .env, checked on every request; 401 without it.
- Cache by hash of the normalized options: metadata in SQLite, files under data/cache/,
  with a cache_ttl option and a fresh=true bypass.
- Block ads and cookie banners the honest way: load EasyList and the
  "I don't care about cookies" filter list at startup, apply them via request
  interception, plus a small CSS hide-list for common consent overlays. Do not
  promise it catches everything.
- Hard 15-second navigation timeout, one retry, then a JSON error with the reason;
  never a hanging request.
- Concurrency capped at a small context pool (default 2) with an in-memory queue,
  so the box does not fall over.
- Out of scope: proxies and IP locations, stealth evasion, scrolling video capture,
  GPU rendering, dashboards, usage billing. That fleet is the paid product.
- README: npx playwright install chromium, .env keys, Chromium memory expectations,
  and a one-line warning that hostile sites will beat this build.

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