Prompt guidelines for Bingeable

You describe the video in plain English. Bingeable either records your live product in a cloud browser, photographs signed-in screens for a cinematic ad, or designs a motion video from a public marketing page — then writes narration and renders a finished video you can edit, translate, and publish.

If the request could be more than one type, chat asks “What kind of video?” Pick Tutorial, Walkthrough, Product demo, or Showcase. A focused prompt usually skips that step.

Use the same names you will see in chat. Setup requirements differ: product demos cannot start without a saved login and an app URL.

Set the project up for the video you want. The URL you entered at create time is where Bingeable starts. Tutorial and product demo need the live app, not the public homepage.

If you saved a site-root URL such as https://acme.com/, a first tutorial prompt may hint: continue and we will click Login, or update the URL to the login or dashboard. For a product demo, update the URL first — a marketing homepage will not photograph the app.

• Tutorial — completed scan, saved login, app URL (login page or dashboard).
• Walkthrough — completed scan; add login if the tour goes inside the product.
• Product demo — saved login (credentials or secure-browser session) and app URL are mandatory. Scan after login is saved. Chat will offer a public-site showcase instead if login is missing.
• Showcase — public marketing URL is enough. Scan and login are skipped.
• Reconnect or “Log in to continue scanning” from project settings when the session expires or the site uses SSO.
• Use Plan mode in the composer to review the outline before recording — helpful for complex tutorials.

One workflow, one outcome. If you need two unrelated tasks, run two prompts in separate chats.

Name a single path you can complete by hand, using the real button and field labels. Skip “if implemented” extras until that path works.

• Name the task: “create a task”, “connect Stripe”, “add an event type”.
• Say who it is for when it matters: “Walk a new user through…” or “Show an admin how to…”.
• Starting point — sidebar, Settings, dashboard, or a named page.
• Exact menu, tab, or button labels when your product uses non-obvious names.
• End state — what success looks like on screen.
• Negative constraints — “don't click Schedule Later”, “explain the contact list but don't select one”.
• Exact values in quotes when they matter — e.g. campaign name “Welcome series”.

Copy a pattern and swap in your product's workflow:

• Show how to [complete a specific task].
• Walk a new user through [connecting / setting up / configuring] [feature].
• Create a tutorial on how to [action] in [area of the product].
• Record a demo showing how to [outcome] from [starting screen].
• Explain how to [multi-step outcome] end to end.

These are real prompts that produced finished tutorial videos. Each one names a single workflow inside a live product.

Bingeable's planner uses your wording to choose the right path through complex UI. These details consistently produce cleaner recordings:

• Mention picker steps before forms — e.g. “choose this option from the list, then fill the login form”.
• Keep all fields in one form on a single step — “enter name, email, and role, then save”.
• Use “pick any option” when the exact choice does not matter.
• Call out explain-only moments — “show the schedule screen but don't click Confirm”.
• Keep the prompt to one happy path — if a long request fails, send a shorter prompt with the real button labels.

A walkthrough is a live recorded tour, not a task tutorial. Plan pages and sections to visit. Do not ask to submit forms or create records unless you actually want a tutorial.

• Name the pages or sections: homepage, pricing, docs, the in-product assistant.
• Say to scroll long pages and pause so the viewer can take each section in.
• Add login only if the tour should enter the signed-in app.

A product demo is a cinematic ad built from real in-app screenshots — not a click-path tutorial and not a public-site marketing crawl. Bingeable signs in, photographs populated screens, and narrates benefits.

Before you prompt: the project URL must be the live app (login or dashboard), and you must have saved credentials or finished secure-browser login. Without both, chat cannot make a product demo (it may offer a public-site showcase instead).

• Name 4–6 screens to show — dashboard, list, editor, canvas — not a 16-step workflow.
• Ask for what the viewer should see, not “click” or “fill in”.
• Prefer populated in-app surfaces over empty states, settings, and login.
• Do not ask to complete long forms; product demo does not record a click path.

A showcase is a designed motion video of a public marketing page. Login and scan are not required. The marketing homepage is the right project URL.

Paste a specific page URL in the prompt to focus that page instead of the homepage.

• Say “showcase”, “landing page video”, or paste the public URL.
• Name the page to feature: pricing, a product landing page, or the whole site.
• Do not ask for in-app clicks, forms, or a signed-in dashboard — use product demo or tutorial instead.

Stay on your own product. Consumer-brand explainers and unrelated URLs are off scope. Marketing and launch videos of your product are in scope — as a showcase (public page) or a product demo (signed-in app).

• “Create a video about [consumer product] benefits” — off scope.
• A 16-step prompt covering every feature and “if implemented” extras — split into one happy path.
• Product demo with a marketing homepage URL and no saved login — it cannot photograph the app.
• Tutorial that starts on the public homepage when you meant the dashboard — use the app URL.
• Two video types in one chat — start a new chat to switch from a tutorial to a marketing showcase.
• External URLs unrelated to your project.

After a video renders, stay in the same chat and describe what should change in plain English. Bingeable drafts patches — narration, captions, callouts, zoom, timing, translations — and shows a preview before you click Render changes.

Select a specific step in the timeline to scope an edit: “Edit ‘Connect Stripe’ — clearer narration on this step.”

Most edits fall into these buckets:

• Narration & tone — script wording, friendlier voice, fix a phrase.
• Captions — shorter subtitles, clearer on-screen text.
• Callouts & focus — highlight a button, zoom on the important click.
• Pacing — shorter intro, remove dead time, faster overall.
• Translation — whole video in another language (15 languages supported).
• Hide a step — remove a step from the final cut without re-recording the whole flow.

Copy, paste, and tweak after your video renders:

Stay in the same chat when you are refining the current video — translate it, tighten pacing, fix narration, add callouts.

Start a new chat when you want a different workflow or a different video type. A chat that already made an in-app tutorial cannot become a marketing-page showcase — chat will ask you to start a new chat.

Some instructions change the underlying browser recording, not just the edit layer. Bingeable will re-record when you ask to:

• Add, remove, or reorder steps in the live workflow.
• Click a different path through the product.
• Hide a step that changes what was captured (depending on the edit).