Vibecode CapCut
track this build5 steps, step by step0%KINDA · weekend project
price $19.99/moyou'd save $239.88/yrbuild time multi-daycategory 🎬 audio & videoreplaced by 0 people
A captioner/trimmer/exporter is buildable, but CapCut's value is mobile editing polish, effects/templates, asset library, TikTok workflow, and real-time rendering.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of CapCut. 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 ===== # CapCut indie build ## Goal Build the smallest trustworthy replacement for the core CapCut workflow for one developer or a tiny team. ## Scope Upload video, auto-caption, cut/trim, add simple templates/effects, and export social aspect ratios. ## 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: - mobile app quality - effects/templates - asset library - timeline editor - platform integrations - rendering performance If those capabilities are essential, use Shotcut 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 video captioning and clipping tool to replace CapCut Pro. Requirements: - A CLI: Python + ffmpeg + faster-whisper. clip input.mp4 transcribes and burns captions; --cut 0:12-0:58 trims first; a folder as input batches every video in it. - Captions from word-level timestamps, grouped 3-5 words per line, rendered as ASS subtitles: bold font, white fill, black outline, centered in the lower third, burned in with ffmpeg. - style.json controls the look in one place: font, size, colors, margin. - Aspect exports: --format 9x16 (blur-pad or center-crop, chosen by flag), 1x1, and 16x9, with bitrate defaults sane for phone playback. - --srt writes the plain subtitle file next to the video so I can fix typos, then --from-srt re-burns without re-transcribing. - Output is <name>-<format>.mp4 beside the input; never overwrite a source file. - Fully local and offline after the model download: no accounts, no uploads, no telemetry. Use the GPU when present, CPU still works. - Out of scope: a timeline editor, effects and templates, and a music library; CapCut's editor polish is the product. This is for talking-head clips. - README: installing ffmpeg and choosing a whisper model size. ## Required capabilities - ffmpeg - speech-to-text - video rendering queue - client editor - storage - optional image/video AI APIs ## 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 CapCut. 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 ===== # CapCut indie build ## Goal Build the smallest trustworthy replacement for the core CapCut workflow for one developer or a tiny team. ## Scope Upload video, auto-caption, cut/trim, add simple templates/effects, and export social aspect ratios. ## 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: - mobile app quality - effects/templates - asset library - timeline editor - platform integrations - rendering performance If those capabilities are essential, use Shotcut 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 video captioning and clipping tool to replace CapCut Pro. Requirements: - A CLI: Python + ffmpeg + faster-whisper. clip input.mp4 transcribes and burns captions; --cut 0:12-0:58 trims first; a folder as input batches every video in it. - Captions from word-level timestamps, grouped 3-5 words per line, rendered as ASS subtitles: bold font, white fill, black outline, centered in the lower third, burned in with ffmpeg. - style.json controls the look in one place: font, size, colors, margin. - Aspect exports: --format 9x16 (blur-pad or center-crop, chosen by flag), 1x1, and 16x9, with bitrate defaults sane for phone playback. - --srt writes the plain subtitle file next to the video so I can fix typos, then --from-srt re-burns without re-transcribing. - Output is <name>-<format>.mp4 beside the input; never overwrite a source file. - Fully local and offline after the model download: no accounts, no uploads, no telemetry. Use the GPU when present, CPU still works. - Out of scope: a timeline editor, effects and templates, and a music library; CapCut's editor polish is the product. This is for talking-head clips. - README: installing ffmpeg and choosing a whisper model size. ## Required capabilities - ffmpeg - speech-to-text - video rendering queue - client editor - storage - optional image/video AI APIs ## 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 CapCut. 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 ===== # CapCut product brief ## Problem A captioner/trimmer/exporter is buildable, but CapCut's value is mobile editing polish, effects/templates, asset library, TikTok workflow, and real-time rendering. ## Product outcome Upload video, auto-caption, cut/trim, add simple templates/effects, and export social aspect ratios. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - ffmpeg - speech-to-text - video rendering queue - client editor - storage - optional image/video AI APIs ## Explicit non-goals for v1 - mobile app quality - effects/templates - asset library - timeline editor - platform integrations - rendering performance ## 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 video captioning and clipping tool to replace CapCut Pro. Requirements: - A CLI: Python + ffmpeg + faster-whisper. clip input.mp4 transcribes and burns captions; --cut 0:12-0:58 trims first; a folder as input batches every video in it. - Captions from word-level timestamps, grouped 3-5 words per line, rendered as ASS subtitles: bold font, white fill, black outline, centered in the lower third, burned in with ffmpeg. - style.json controls the look in one place: font, size, colors, margin. - Aspect exports: --format 9x16 (blur-pad or center-crop, chosen by flag), 1x1, and 16x9, with bitrate defaults sane for phone playback. - --srt writes the plain subtitle file next to the video so I can fix typos, then --from-srt re-burns without re-transcribing. - Output is <name>-<format>.mp4 beside the input; never overwrite a source file. - Fully local and offline after the model download: no accounts, no uploads, no telemetry. Use the GPU when present, CPU still works. - Out of scope: a timeline editor, effects and templates, and a music library; CapCut's editor polish is the product. This is for talking-head clips. - README: installing ffmpeg and choosing a whisper model size. ## 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 CapCut capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# CapCut indie build ## Goal Build the smallest trustworthy replacement for the core CapCut workflow for one developer or a tiny team. ## Scope Upload video, auto-caption, cut/trim, add simple templates/effects, and export social aspect ratios. ## 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: - mobile app quality - effects/templates - asset library - timeline editor - platform integrations - rendering performance If those capabilities are essential, use Shotcut 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 video captioning and clipping tool to replace CapCut Pro. Requirements: - A CLI: Python + ffmpeg + faster-whisper. clip input.mp4 transcribes and burns captions; --cut 0:12-0:58 trims first; a folder as input batches every video in it. - Captions from word-level timestamps, grouped 3-5 words per line, rendered as ASS subtitles: bold font, white fill, black outline, centered in the lower third, burned in with ffmpeg. - style.json controls the look in one place: font, size, colors, margin. - Aspect exports: --format 9x16 (blur-pad or center-crop, chosen by flag), 1x1, and 16x9, with bitrate defaults sane for phone playback. - --srt writes the plain subtitle file next to the video so I can fix typos, then --from-srt re-burns without re-transcribing. - Output is <name>-<format>.mp4 beside the input; never overwrite a source file. - Fully local and offline after the model download: no accounts, no uploads, no telemetry. Use the GPU when present, CPU still works. - Out of scope: a timeline editor, effects and templates, and a music library; CapCut's editor polish is the product. This is for talking-head clips. - README: installing ffmpeg and choosing a whisper model size. ## Required capabilities - ffmpeg - speech-to-text - video rendering queue - client editor - storage - optional image/video AI APIs ## 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.
PRODUCT.md
# CapCut product brief ## Problem A captioner/trimmer/exporter is buildable, but CapCut's value is mobile editing polish, effects/templates, asset library, TikTok workflow, and real-time rendering. ## Product outcome Upload video, auto-caption, cut/trim, add simple templates/effects, and export social aspect ratios. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - ffmpeg - speech-to-text - video rendering queue - client editor - storage - optional image/video AI APIs ## Explicit non-goals for v1 - mobile app quality - effects/templates - asset library - timeline editor - platform integrations - rendering performance ## 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 video captioning and clipping tool to replace CapCut Pro. Requirements: - A CLI: Python + ffmpeg + faster-whisper. clip input.mp4 transcribes and burns captions; --cut 0:12-0:58 trims first; a folder as input batches every video in it. - Captions from word-level timestamps, grouped 3-5 words per line, rendered as ASS subtitles: bold font, white fill, black outline, centered in the lower third, burned in with ffmpeg. - style.json controls the look in one place: font, size, colors, margin. - Aspect exports: --format 9x16 (blur-pad or center-crop, chosen by flag), 1x1, and 16x9, with bitrate defaults sane for phone playback. - --srt writes the plain subtitle file next to the video so I can fix typos, then --from-srt re-burns without re-transcribing. - Output is <name>-<format>.mp4 beside the input; never overwrite a source file. - Fully local and offline after the model download: no accounts, no uploads, no telemetry. Use the GPU when present, CPU still works. - Out of scope: a timeline editor, effects and templates, and a music library; CapCut's editor polish is the product. This is for talking-head clips. - README: installing ffmpeg and choosing a whisper model size. ## 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 CapCut 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 · this prompt is generated from the build plan · improve it via PR
They pay because short-form editing is fast on a phone and full of reusable trends/effects.
xmobile app quality
xeffects/templates
xasset library
xtimeline editor
xplatform integrations
xrendering performance
share on X ↗"I just replaced CapCut ($19.99/mo) with one prompt"
Don't feel like building it? These folks already made it free.
SShotcutA sturdy desktop editor that would rather give you controls than trends.open source↗
KdenliveA real multitrack editor with local captions, minus the template casino.open source↗
Adobe ExpressBrowser editing, captions, graphics and templates without a watermark; premium stock and clever tricks still wave from behind glass.free↗all 5 free alternatives to CapCut →· no votes, no pay-to-list · just what's real
Vibecode CapCut
Kinda. The core of CapCut is buildable in a weekend with the prompt on this page, but there are real gaps: mobile app quality, effects/templates. Read the honest list above before committing.
How much does CapCut cost?
CapCut costs about $19.99/month (Pro, checked 2026-07-30), which is $239.88 per year.
What do I lose by replacing CapCut?
Honestly: mobile app quality; effects/templates; asset library; timeline editor; platform integrations; rendering performance. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to CapCut?
Yes: Shotcut (A sturdy desktop editor that would rather give you controls than trends.) Kdenlive (A real multitrack editor with local captions, minus the template casino.) Adobe Express (Browser editing, captions, graphics and templates without a watermark; premium stock and clever tricks still wave from behind glass.) All 5 curated free alternatives are at vibecodeit.com/capcut/alternatives. The prompt is for when you want it exactly your way.