# Gemini Notebook Video Prompts

Upload these three sources to one notebook:

1. `complete-user-guide.md`
2. `notebooklm-video-source-pack.md`
3. `torah-translate-notebooklm-video-source-pack.pdf`

Add the five authenticated screenshots as separate sources if the notebook accepts them directly; otherwise use the PDF, which embeds and captions them. Select only the sources relevant to each artifact.

Gemini Notebook's current source documentation explicitly supports Markdown, PDF, and common image formats, so the recommended package can be uploaded directly. Each source may contain up to 500,000 words or 200 MB. The free tier currently allows up to 50 sources, but account and daily generation limits are subject to change.

## Explainer Video Overview prompt

Create an accurate 4-6 minute product tutorial for a learner, teacher, or researcher encountering Torah and Chassidus Translate for the first time. Follow the demonstrated workflow in order: create a project, configure a provider without revealing a key, import a page or PDF, verify OCR and page identity, translate one test page, compare source and translation, use one learning tool, explain tutor consent and cost, then export and back up. Use the supplied authenticated screenshots as the visual spine. Preserve Hebrew right-to-left orientation. Keep the tone calm, literate, and instructional. State clearly that AI output requires review and that cloud provider charges and terms may apply. Do not invent testimonials, ratings, user counts, endorsements, provider prices, or unsupported capabilities.

Recommended style: **Explainer**, **Classic** or **Whiteboard**, landscape 16:9.

## Short advertising Video Overview prompt

Create a polished approximately 60-second introduction for Torah and Chassidus Translate. Begin with the challenge of learning from a difficult scanned Hebrew or Yiddish page. Show the named project and quickly move to the real parallel bilingual translation as the central proof. Then show project-grounded tutoring consent and masked provider readiness. Emphasize keeping the source visible, choosing a provider, asking better questions, and exporting a study copy. Use concise on-screen captions and calm editorial pacing. End with: “Keep the source in view, and make the next question possible.” Include a readable footer: “AI output requires review. Provider charges and terms may apply.” Do not imply perfect translation, guaranteed privacy, zero cost, or authoritative religious interpretation.

Recommended format: **Short** where available; otherwise use **Explainer** and request one minute. Recommended style: **Heritage** or **Paper-craft**, provided Hebrew remains sharp and unmirrored.

## Cinematic brand Video Overview prompt

Create a restrained cinematic brand film about the movement from a photographed sacred text to active learning. The original page is the hero. Use macro crops of Hebrew type, warm paper textures, deep green interface details, and slow transitions into the real side-by-side translation. The emotional arc is difficulty, access, comparison, curiosity, and return to the source. Present the app as a careful workspace, not an oracle. Include the real product name and conclude with the source and translation together. Avoid religious spectacle, fabricated libraries, glowing supernatural effects, generic AI imagery, and any invented endorsement. Include the review-and-provider-cost disclaimer.

Recommended format: **Cinematic** when available and appropriate for the account.

## Presenter slide deck prompt

Create an 8-10 slide presenter deck for a live demonstration. Use the authenticated screenshots and the following structure: problem, product principle, project organization, authenticated import, translation proof, learning loop, privacy and cost, exports and backup, responsible-use guardrails, next step. Use short headings and large screenshot crops. Put detailed speaking notes in the presenter narrative, not on the slide. Never reveal a credential or claim perfect accuracy.

## Audio Overview prompt

Create a practical conversation between an experienced teacher and a technically curious learner. Explain why keeping the source visible matters, how a one-page test run prevents wasted cost, how project-grounded tutoring differs from generic chat, and why provider invoices remain authoritative. Mention local options without implying that every feature runs offline. Close with a checklist for the listener's first project.

## Quality-control prompt for a second pass

Review the generated artifact against the selected sources. List every factual statement that is unsupported, every screenshot label that does not match the actual interface, every place Hebrew direction is wrong, and every missing disclosure about AI review, cloud transfer, provider billing, or transcripts. Then propose exact replacements. Do not merely summarize the artifact.

## Official workflow references

- https://support.google.com/gemininotebook/answer/16454555?hl=en
- https://support.google.com/gemininotebook/answer/16215270?hl=en
- https://support.google.com/gemininotebook/answer/16213268?hl=en
- https://support.google.com/gemininotebook/answer/16757456?hl=en