Vibecode Subclip

You are building a lean indie version of Subclip.

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

## Goal

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

## Scope

Build only the closest consolation: import a video, transcribe it locally, cut by editing the transcript or removing silence, style subtitles, and export an MP4 and SRT.

## 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:
- ONNX model packaging and hardware-accelerated in-browser inference
- coordinated client-side and server-side Remotion rendering
- native macOS and iOS apps and their release pipelines
- production dubbing, voice cloning, storage, and render queues
- MCP server, developer APIs, NLE exports, and publishing integrations

If those capabilities are essential, use Lightweight Video Editor 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 the closest honest personal substitute for Subclip, not a platform clone. Requirements:

- Use Python 3.12 + FastAPI for a localhost web app, with a plain JavaScript frontend,
  FFmpeg for media work, and faster-whisper for word-level transcription.
- I can import MP4, MOV, WebM, MP3, or WAV files, see a synced transcript beside the
  video preview, and click any word to seek to its timestamp.
- Deleting transcript ranges creates an undoable cut list. Detect silences longer than
  500 ms and let me accept or reject each suggested cut before rendering.
- Let me edit subtitle text and timing, import or export SRT, and apply one ASS style
  file with font, colors, outline, position, and words-per-line controls.
- Export MP4 in 16:9, 9:16, or 1:1 with center-crop or blur-pad. Never overwrite the
  source, and show FFmpeg progress plus a useful failure message.
- Store projects as JSON under ~/SubclipDIY/projects and renders under
  ~/SubclipDIY/exports, with a recent-projects page and a delete-project action.
- Bind to localhost only. No accounts, uploads, telemetry, or network calls after the
  faster-whisper model has been downloaded.
- Deliberately exclude ONNX models in the browser, Remotion client or server rendering,
  native apps, cloud dubbing, render queues, publishing, an MCP server, and public APIs.
- Add unit tests for cut-list merging and subtitle grouping, plus one smoke test that
  imports a short fixture and produces a playable MP4.
- Include a README with setup for Python and FFmpeg, model-size guidance, data paths,
  supported formats, and an honest warning about CPU transcription and render speed.

## Required capabilities

- Python 3.12
- FFmpeg
- faster-whisper
- desktop with enough storage for source media and renders
- GPU optional

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

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

## Goal

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

## Scope

Build only the closest consolation: import a video, transcribe it locally, cut by editing the transcript or removing silence, style subtitles, and export an MP4 and SRT.

## 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:
- ONNX model packaging and hardware-accelerated in-browser inference
- coordinated client-side and server-side Remotion rendering
- native macOS and iOS apps and their release pipelines
- production dubbing, voice cloning, storage, and render queues
- MCP server, developer APIs, NLE exports, and publishing integrations

If those capabilities are essential, use Lightweight Video Editor 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 the closest honest personal substitute for Subclip, not a platform clone. Requirements:

- Use Python 3.12 + FastAPI for a localhost web app, with a plain JavaScript frontend,
  FFmpeg for media work, and faster-whisper for word-level transcription.
- I can import MP4, MOV, WebM, MP3, or WAV files, see a synced transcript beside the
  video preview, and click any word to seek to its timestamp.
- Deleting transcript ranges creates an undoable cut list. Detect silences longer than
  500 ms and let me accept or reject each suggested cut before rendering.
- Let me edit subtitle text and timing, import or export SRT, and apply one ASS style
  file with font, colors, outline, position, and words-per-line controls.
- Export MP4 in 16:9, 9:16, or 1:1 with center-crop or blur-pad. Never overwrite the
  source, and show FFmpeg progress plus a useful failure message.
- Store projects as JSON under ~/SubclipDIY/projects and renders under
  ~/SubclipDIY/exports, with a recent-projects page and a delete-project action.
- Bind to localhost only. No accounts, uploads, telemetry, or network calls after the
  faster-whisper model has been downloaded.
- Deliberately exclude ONNX models in the browser, Remotion client or server rendering,
  native apps, cloud dubbing, render queues, publishing, an MCP server, and public APIs.
- Add unit tests for cut-list merging and subtitle grouping, plus one smoke test that
  imports a short fixture and produces a playable MP4.
- Include a README with setup for Python and FFmpeg, model-size guidance, data paths,
  supported formats, and an honest warning about CPU transcription and render speed.

## Required capabilities

- Python 3.12
- FFmpeg
- faster-whisper
- desktop with enough storage for source media and renders
- GPU optional

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

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

## Problem

Subclip is not a realistic vibe-coded replacement. A narrow transcript cutter is buildable, but the product is a multi-surface post-production system: ONNX models running locally in the browser, client-side and server-side Remotion rendering, cloud AI and media jobs, native macOS and iOS experiences, plus an MCP server and developer APIs. Reproducing and operating those surfaces is a platform project, not a one-shot build.

## Product outcome

Build only the closest consolation: import a video, transcribe it locally, cut by editing the transcript or removing silence, style subtitles, and export an MP4 and SRT.

## Target user

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

## Required capabilities

- Python 3.12
- FFmpeg
- faster-whisper
- desktop with enough storage for source media and renders
- GPU optional

## Explicit non-goals for v1

- ONNX model packaging and hardware-accelerated in-browser inference
- coordinated client-side and server-side Remotion rendering
- native macOS and iOS apps and their release pipelines
- production dubbing, voice cloning, storage, and render queues
- MCP server, developer APIs, NLE exports, and publishing integrations

## 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 the closest honest personal substitute for Subclip, not a platform clone. Requirements:

- Use Python 3.12 + FastAPI for a localhost web app, with a plain JavaScript frontend,
  FFmpeg for media work, and faster-whisper for word-level transcription.
- I can import MP4, MOV, WebM, MP3, or WAV files, see a synced transcript beside the
  video preview, and click any word to seek to its timestamp.
- Deleting transcript ranges creates an undoable cut list. Detect silences longer than
  500 ms and let me accept or reject each suggested cut before rendering.
- Let me edit subtitle text and timing, import or export SRT, and apply one ASS style
  file with font, colors, outline, position, and words-per-line controls.
- Export MP4 in 16:9, 9:16, or 1:1 with center-crop or blur-pad. Never overwrite the
  source, and show FFmpeg progress plus a useful failure message.
- Store projects as JSON under ~/SubclipDIY/projects and renders under
  ~/SubclipDIY/exports, with a recent-projects page and a delete-project action.
- Bind to localhost only. No accounts, uploads, telemetry, or network calls after the
  faster-whisper model has been downloaded.
- Deliberately exclude ONNX models in the browser, Remotion client or server rendering,
  native apps, cloud dubbing, render queues, publishing, an MCP server, and public APIs.
- Add unit tests for cut-list merging and subtitle grouping, plus one smoke test that
  imports a short fixture and produces a playable MP4.
- Include a README with setup for Python and FFmpeg, model-size guidance, data paths,
  supported formats, and an honest warning about CPU transcription and render speed.

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

# Subclip indie build

## Goal

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

## Scope

Build only the closest consolation: import a video, transcribe it locally, cut by editing the transcript or removing silence, style subtitles, and export an MP4 and SRT.

## 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:
- ONNX model packaging and hardware-accelerated in-browser inference
- coordinated client-side and server-side Remotion rendering
- native macOS and iOS apps and their release pipelines
- production dubbing, voice cloning, storage, and render queues
- MCP server, developer APIs, NLE exports, and publishing integrations

If those capabilities are essential, use Lightweight Video Editor 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 the closest honest personal substitute for Subclip, not a platform clone. Requirements:

- Use Python 3.12 + FastAPI for a localhost web app, with a plain JavaScript frontend,
  FFmpeg for media work, and faster-whisper for word-level transcription.
- I can import MP4, MOV, WebM, MP3, or WAV files, see a synced transcript beside the
  video preview, and click any word to seek to its timestamp.
- Deleting transcript ranges creates an undoable cut list. Detect silences longer than
  500 ms and let me accept or reject each suggested cut before rendering.
- Let me edit subtitle text and timing, import or export SRT, and apply one ASS style
  file with font, colors, outline, position, and words-per-line controls.
- Export MP4 in 16:9, 9:16, or 1:1 with center-crop or blur-pad. Never overwrite the
  source, and show FFmpeg progress plus a useful failure message.
- Store projects as JSON under ~/SubclipDIY/projects and renders under
  ~/SubclipDIY/exports, with a recent-projects page and a delete-project action.
- Bind to localhost only. No accounts, uploads, telemetry, or network calls after the
  faster-whisper model has been downloaded.
- Deliberately exclude ONNX models in the browser, Remotion client or server rendering,
  native apps, cloud dubbing, render queues, publishing, an MCP server, and public APIs.
- Add unit tests for cut-list merging and subtitle grouping, plus one smoke test that
  imports a short fixture and produces a playable MP4.
- Include a README with setup for Python and FFmpeg, model-size guidance, data paths,
  supported formats, and an honest warning about CPU transcription and render speed.

## Required capabilities

- Python 3.12
- FFmpeg
- faster-whisper
- desktop with enough storage for source media and renders
- GPU optional

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

# Subclip product brief

## Problem

Subclip is not a realistic vibe-coded replacement. A narrow transcript cutter is buildable, but the product is a multi-surface post-production system: ONNX models running locally in the browser, client-side and server-side Remotion rendering, cloud AI and media jobs, native macOS and iOS experiences, plus an MCP server and developer APIs. Reproducing and operating those surfaces is a platform project, not a one-shot build.

## Product outcome

Build only the closest consolation: import a video, transcribe it locally, cut by editing the transcript or removing silence, style subtitles, and export an MP4 and SRT.

## Target user

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

## Required capabilities

- Python 3.12
- FFmpeg
- faster-whisper
- desktop with enough storage for source media and renders
- GPU optional

## Explicit non-goals for v1

- ONNX model packaging and hardware-accelerated in-browser inference
- coordinated client-side and server-side Remotion rendering
- native macOS and iOS apps and their release pipelines
- production dubbing, voice cloning, storage, and render queues
- MCP server, developer APIs, NLE exports, and publishing integrations

## 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 the closest honest personal substitute for Subclip, not a platform clone. Requirements:

- Use Python 3.12 + FastAPI for a localhost web app, with a plain JavaScript frontend,
  FFmpeg for media work, and faster-whisper for word-level transcription.
- I can import MP4, MOV, WebM, MP3, or WAV files, see a synced transcript beside the
  video preview, and click any word to seek to its timestamp.
- Deleting transcript ranges creates an undoable cut list. Detect silences longer than
  500 ms and let me accept or reject each suggested cut before rendering.
- Let me edit subtitle text and timing, import or export SRT, and apply one ASS style
  file with font, colors, outline, position, and words-per-line controls.
- Export MP4 in 16:9, 9:16, or 1:1 with center-crop or blur-pad. Never overwrite the
  source, and show FFmpeg progress plus a useful failure message.
- Store projects as JSON under ~/SubclipDIY/projects and renders under
  ~/SubclipDIY/exports, with a recent-projects page and a delete-project action.
- Bind to localhost only. No accounts, uploads, telemetry, or network calls after the
  faster-whisper model has been downloaded.
- Deliberately exclude ONNX models in the browser, Remotion client or server rendering,
  native apps, cloud dubbing, render queues, publishing, an MCP server, and public APIs.
- Add unit tests for cut-list merging and subtitle grouping, plus one smoke test that
  imports a short fixture and produces a playable MP4.
- Include a README with setup for Python and FFmpeg, model-size guidance, data paths,
  supported formats, and an honest warning about CPU transcription and render speed.

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