Vibecode Teleprompter.com
track this build5 steps, step by step0%YES · one-shottable
price $19.99/moyou'd save $239.88/yrbuild time one sittingcategory 🎬 audio & videoreplaced by 0 people
A teleprompter is text that moves down the screen at an adjustable speed, and every browser can already do that. The genuinely useful extras, mirror flip for beam-splitter rigs, large-type layout, keyboard speed control, camera preview behind the words, are all standard web APIs and fit in one session. Even voice-tracked scrolling, the feature people assume is magic, is a Web Speech API loop that matches recognized words against your script. What you cannot casually rebuild is the polished phone app you actually hold at arm's length while filming, plus remote control between two devices. If you record at a desk with a webcam, the DIY version is not a compromise, it is the same thing.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Teleprompter.com.
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 =====
# Teleprompter.com indie build
## Goal
Build the smallest trustworthy replacement for the core Teleprompter.com workflow for one developer or a tiny team.
## Scope
A local web app that stores scripts, scrolls them at a controllable speed over an optional live camera preview, mirrors on demand, and can record the take to a file.
## 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:
- A real iOS/Android app that behaves well when the screen is your only prompter
- Remote control from a second device without you building the socket plumbing
- Cloud sync of scripts across phone, laptop and someone else's machine
- Reliable voice tracking in noisy rooms; browser speech recognition drifts
- Export niceties: burned-in captions, project organization, team script sharing
If those capabilities are essential, use Teleprompter.com 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 a local teleprompter web app. Stack: Vite + React + TypeScript, no backend, no accounts, no telemetry, no external API calls.
Data: scripts are stored in localStorage as {id, title, body, updatedAt}. Ship with one sample script. No cloud, no sync, no login.
Layout: two views in a single page app.
1) Library: list scripts, create, rename, delete, edit body in a plain textarea with autosave on blur.
2) Prompt view: fullscreen scrolling display of the selected script.
Prompt view requirements:
- Very large default type, adjustable font size, line height and text width.
- Continuous smooth scroll driven by requestAnimationFrame, speed in pixels per second, not a CSS animation.
- Controls: space toggles play/pause, arrow up/down changes speed, arrow left/right jumps 3 seconds of scroll, R resets to top, M toggles horizontal mirror, F toggles fullscreen, Esc exits.
- A fixed reading line marker with adjustable vertical position.
- Mirror mode applies transform: scaleX(-1) to the text layer only, controls stay readable.
- Optional camera layer: getUserMedia video preview rendered behind the text at adjustable opacity. If permission is denied, fall back to a solid background and say so once, quietly.
- Optional recording: MediaRecorder on the camera+mic stream, save to a downloadable .webm. Do not attempt to composite the text into the recording.
- Optional voice tracking behind a toggle labelled experimental: use the browser SpeechRecognition API, fuzzy match recognized words against upcoming script tokens, and nudge scroll position toward the matched word. If SpeechRecognition is unavailable, hide the toggle.
Persist user settings (speed, font size, mirror, opacity, marker position) in localStorage.
Out of scope: multi device remote control, accounts, script sharing, burned-in captions, mobile native app.
Styling: plain CSS, dark background, high contrast, no UI framework. Controls auto-hide after 3 seconds of mouse idle during playback.
Deliver a README with npm install, npm run dev, the full keyboard shortcut list, and a note that camera and mic access require localhost or HTTPS. No .env needed since there are no secrets.
## Required capabilities
- A modern Chromium browser for camera access and speech recognition
- Webcam and mic permissions granted to localhost
- Optional: a second device on the same network if you want to prompt from a phone
## 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 Teleprompter.com.
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 =====
# Teleprompter.com indie build
## Goal
Build the smallest trustworthy replacement for the core Teleprompter.com workflow for one developer or a tiny team.
## Scope
A local web app that stores scripts, scrolls them at a controllable speed over an optional live camera preview, mirrors on demand, and can record the take to a file.
## 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:
- A real iOS/Android app that behaves well when the screen is your only prompter
- Remote control from a second device without you building the socket plumbing
- Cloud sync of scripts across phone, laptop and someone else's machine
- Reliable voice tracking in noisy rooms; browser speech recognition drifts
- Export niceties: burned-in captions, project organization, team script sharing
If those capabilities are essential, use Teleprompter.com 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 a local teleprompter web app. Stack: Vite + React + TypeScript, no backend, no accounts, no telemetry, no external API calls.
Data: scripts are stored in localStorage as {id, title, body, updatedAt}. Ship with one sample script. No cloud, no sync, no login.
Layout: two views in a single page app.
1) Library: list scripts, create, rename, delete, edit body in a plain textarea with autosave on blur.
2) Prompt view: fullscreen scrolling display of the selected script.
Prompt view requirements:
- Very large default type, adjustable font size, line height and text width.
- Continuous smooth scroll driven by requestAnimationFrame, speed in pixels per second, not a CSS animation.
- Controls: space toggles play/pause, arrow up/down changes speed, arrow left/right jumps 3 seconds of scroll, R resets to top, M toggles horizontal mirror, F toggles fullscreen, Esc exits.
- A fixed reading line marker with adjustable vertical position.
- Mirror mode applies transform: scaleX(-1) to the text layer only, controls stay readable.
- Optional camera layer: getUserMedia video preview rendered behind the text at adjustable opacity. If permission is denied, fall back to a solid background and say so once, quietly.
- Optional recording: MediaRecorder on the camera+mic stream, save to a downloadable .webm. Do not attempt to composite the text into the recording.
- Optional voice tracking behind a toggle labelled experimental: use the browser SpeechRecognition API, fuzzy match recognized words against upcoming script tokens, and nudge scroll position toward the matched word. If SpeechRecognition is unavailable, hide the toggle.
Persist user settings (speed, font size, mirror, opacity, marker position) in localStorage.
Out of scope: multi device remote control, accounts, script sharing, burned-in captions, mobile native app.
Styling: plain CSS, dark background, high contrast, no UI framework. Controls auto-hide after 3 seconds of mouse idle during playback.
Deliver a README with npm install, npm run dev, the full keyboard shortcut list, and a note that camera and mic access require localhost or HTTPS. No .env needed since there are no secrets.
## Required capabilities
- A modern Chromium browser for camera access and speech recognition
- Webcam and mic permissions granted to localhost
- Optional: a second device on the same network if you want to prompt from a phone
## 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 Teleprompter.com.
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 =====
# Teleprompter.com product brief
## Problem
A teleprompter is text that moves down the screen at an adjustable speed, and every browser can already do that. The genuinely useful extras, mirror flip for beam-splitter rigs, large-type layout, keyboard speed control, camera preview behind the words, are all standard web APIs and fit in one session. Even voice-tracked scrolling, the feature people assume is magic, is a Web Speech API loop that matches recognized words against your script. What you cannot casually rebuild is the polished phone app you actually hold at arm's length while filming, plus remote control between two devices. If you record at a desk with a webcam, the DIY version is not a compromise, it is the same thing.
## Product outcome
A local web app that stores scripts, scrolls them at a controllable speed over an optional live camera preview, mirrors on demand, and can record the take to a file.
## Target user
A serious builder who needs a maintainable product foundation rather than a one-off demo.
## Required capabilities
- A modern Chromium browser for camera access and speech recognition
- Webcam and mic permissions granted to localhost
- Optional: a second device on the same network if you want to prompt from a phone
## Explicit non-goals for v1
- A real iOS/Android app that behaves well when the screen is your only prompter
- Remote control from a second device without you building the socket plumbing
- Cloud sync of scripts across phone, laptop and someone else's machine
- Reliable voice tracking in noisy rooms; browser speech recognition drifts
- Export niceties: burned-in captions, project organization, team script sharing
## 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 a local teleprompter web app. Stack: Vite + React + TypeScript, no backend, no accounts, no telemetry, no external API calls.
Data: scripts are stored in localStorage as {id, title, body, updatedAt}. Ship with one sample script. No cloud, no sync, no login.
Layout: two views in a single page app.
1) Library: list scripts, create, rename, delete, edit body in a plain textarea with autosave on blur.
2) Prompt view: fullscreen scrolling display of the selected script.
Prompt view requirements:
- Very large default type, adjustable font size, line height and text width.
- Continuous smooth scroll driven by requestAnimationFrame, speed in pixels per second, not a CSS animation.
- Controls: space toggles play/pause, arrow up/down changes speed, arrow left/right jumps 3 seconds of scroll, R resets to top, M toggles horizontal mirror, F toggles fullscreen, Esc exits.
- A fixed reading line marker with adjustable vertical position.
- Mirror mode applies transform: scaleX(-1) to the text layer only, controls stay readable.
- Optional camera layer: getUserMedia video preview rendered behind the text at adjustable opacity. If permission is denied, fall back to a solid background and say so once, quietly.
- Optional recording: MediaRecorder on the camera+mic stream, save to a downloadable .webm. Do not attempt to composite the text into the recording.
- Optional voice tracking behind a toggle labelled experimental: use the browser SpeechRecognition API, fuzzy match recognized words against upcoming script tokens, and nudge scroll position toward the matched word. If SpeechRecognition is unavailable, hide the toggle.
Persist user settings (speed, font size, mirror, opacity, marker position) in localStorage.
Out of scope: multi device remote control, accounts, script sharing, burned-in captions, mobile native app.
Styling: plain CSS, dark background, high contrast, no UI framework. Controls auto-hide after 3 seconds of mouse idle during playback.
Deliver a README with npm install, npm run dev, the full keyboard shortcut list, and a note that camera and mic access require localhost or HTTPS. No .env needed since there are no secrets.
## 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 Teleprompter.com capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.README.md
# Teleprompter.com indie build ## Goal Build the smallest trustworthy replacement for the core Teleprompter.com workflow for one developer or a tiny team. ## Scope A local web app that stores scripts, scrolls them at a controllable speed over an optional live camera preview, mirrors on demand, and can record the take to a file. ## 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: - A real iOS/Android app that behaves well when the screen is your only prompter - Remote control from a second device without you building the socket plumbing - Cloud sync of scripts across phone, laptop and someone else's machine - Reliable voice tracking in noisy rooms; browser speech recognition drifts - Export niceties: burned-in captions, project organization, team script sharing If those capabilities are essential, use Teleprompter.com 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 a local teleprompter web app. Stack: Vite + React + TypeScript, no backend, no accounts, no telemetry, no external API calls.
Data: scripts are stored in localStorage as {id, title, body, updatedAt}. Ship with one sample script. No cloud, no sync, no login.
Layout: two views in a single page app.
1) Library: list scripts, create, rename, delete, edit body in a plain textarea with autosave on blur.
2) Prompt view: fullscreen scrolling display of the selected script.
Prompt view requirements:
- Very large default type, adjustable font size, line height and text width.
- Continuous smooth scroll driven by requestAnimationFrame, speed in pixels per second, not a CSS animation.
- Controls: space toggles play/pause, arrow up/down changes speed, arrow left/right jumps 3 seconds of scroll, R resets to top, M toggles horizontal mirror, F toggles fullscreen, Esc exits.
- A fixed reading line marker with adjustable vertical position.
- Mirror mode applies transform: scaleX(-1) to the text layer only, controls stay readable.
- Optional camera layer: getUserMedia video preview rendered behind the text at adjustable opacity. If permission is denied, fall back to a solid background and say so once, quietly.
- Optional recording: MediaRecorder on the camera+mic stream, save to a downloadable .webm. Do not attempt to composite the text into the recording.
- Optional voice tracking behind a toggle labelled experimental: use the browser SpeechRecognition API, fuzzy match recognized words against upcoming script tokens, and nudge scroll position toward the matched word. If SpeechRecognition is unavailable, hide the toggle.
Persist user settings (speed, font size, mirror, opacity, marker position) in localStorage.
Out of scope: multi device remote control, accounts, script sharing, burned-in captions, mobile native app.
Styling: plain CSS, dark background, high contrast, no UI framework. Controls auto-hide after 3 seconds of mouse idle during playback.
Deliver a README with npm install, npm run dev, the full keyboard shortcut list, and a note that camera and mic access require localhost or HTTPS. No .env needed since there are no secrets.
## Required capabilities
- A modern Chromium browser for camera access and speech recognition
- Webcam and mic permissions granted to localhost
- Optional: a second device on the same network if you want to prompt from a phone
## 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
# Teleprompter.com product brief ## Problem A teleprompter is text that moves down the screen at an adjustable speed, and every browser can already do that. The genuinely useful extras, mirror flip for beam-splitter rigs, large-type layout, keyboard speed control, camera preview behind the words, are all standard web APIs and fit in one session. Even voice-tracked scrolling, the feature people assume is magic, is a Web Speech API loop that matches recognized words against your script. What you cannot casually rebuild is the polished phone app you actually hold at arm's length while filming, plus remote control between two devices. If you record at a desk with a webcam, the DIY version is not a compromise, it is the same thing. ## Product outcome A local web app that stores scripts, scrolls them at a controllable speed over an optional live camera preview, mirrors on demand, and can record the take to a file. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - A modern Chromium browser for camera access and speech recognition - Webcam and mic permissions granted to localhost - Optional: a second device on the same network if you want to prompt from a phone ## Explicit non-goals for v1 - A real iOS/Android app that behaves well when the screen is your only prompter - Remote control from a second device without you building the socket plumbing - Cloud sync of scripts across phone, laptop and someone else's machine - Reliable voice tracking in noisy rooms; browser speech recognition drifts - Export niceties: burned-in captions, project organization, team script sharing ## 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 a local teleprompter web app. Stack: Vite + React + TypeScript, no backend, no accounts, no telemetry, no external API calls.
Data: scripts are stored in localStorage as {id, title, body, updatedAt}. Ship with one sample script. No cloud, no sync, no login.
Layout: two views in a single page app.
1) Library: list scripts, create, rename, delete, edit body in a plain textarea with autosave on blur.
2) Prompt view: fullscreen scrolling display of the selected script.
Prompt view requirements:
- Very large default type, adjustable font size, line height and text width.
- Continuous smooth scroll driven by requestAnimationFrame, speed in pixels per second, not a CSS animation.
- Controls: space toggles play/pause, arrow up/down changes speed, arrow left/right jumps 3 seconds of scroll, R resets to top, M toggles horizontal mirror, F toggles fullscreen, Esc exits.
- A fixed reading line marker with adjustable vertical position.
- Mirror mode applies transform: scaleX(-1) to the text layer only, controls stay readable.
- Optional camera layer: getUserMedia video preview rendered behind the text at adjustable opacity. If permission is denied, fall back to a solid background and say so once, quietly.
- Optional recording: MediaRecorder on the camera+mic stream, save to a downloadable .webm. Do not attempt to composite the text into the recording.
- Optional voice tracking behind a toggle labelled experimental: use the browser SpeechRecognition API, fuzzy match recognized words against upcoming script tokens, and nudge scroll position toward the matched word. If SpeechRecognition is unavailable, hide the toggle.
Persist user settings (speed, font size, mirror, opacity, marker position) in localStorage.
Out of scope: multi device remote control, accounts, script sharing, burned-in captions, mobile native app.
Styling: plain CSS, dark background, high contrast, no UI framework. Controls auto-hide after 3 seconds of mouse idle during playback.
Deliver a README with npm install, npm run dev, the full keyboard shortcut list, and a note that camera and mic access require localhost or HTTPS. No .env needed since there are no secrets.
## 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 Teleprompter.com 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
Because the people who buy teleprompter software are usually filming on a phone, not sitting at a laptop, and a native app that survives screen rotation, background audio, lock behavior and a physical prompter rig is worth more than the twelve lines of scroll logic inside it. Paying also means not thinking about it five minutes before a take, which is exactly when a hand-rolled tool decides the camera permission expired.
xA real iOS/Android app that behaves well when the screen is your only prompter
xRemote control from a second device without you building the socket plumbing
xCloud sync of scripts across phone, laptop and someone else's machine
xReliable voice tracking in noisy rooms; browser speech recognition drifts
xExport niceties: burned-in captions, project organization, team script sharing
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced Teleprompter.com ($19.99/mo) with one prompt"
Vibecode Teleprompter.com
Yes. A competent AI coding agent (Claude Code, Codex, Cursor) can build a usable personal Teleprompter.com replacement in one session with the prompt on this page. It runs on your own machine or server with no subscription.
How much does Teleprompter.com cost?
Teleprompter.com costs about $19.99/month (Pro, checked 2026-08-18), which is $239.88 per year. That's what you save by replacing it with one prompt.
What do I lose by replacing Teleprompter.com?
Honestly: A real iOS/Android app that behaves well when the screen is your only prompter; Remote control from a second device without you building the socket plumbing; Cloud sync of scripts across phone, laptop and someone else's machine; Reliable voice tracking in noisy rooms; browser speech recognition drifts; Export niceties: burned-in captions, project organization, team script sharing. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Teleprompter.com?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.