Fifty workflows. Ten different ways to use AI.
A narration script belongs in a speech tool; a motion description belongs in a video tool. Choose the actual job, replace the placeholders and evaluate the result.
These public learning templates are separate from account-library Prompt Pack records. They are editorially reviewed, not provider-tested output claims.
Build your context and acceptance checks first →Claude: start with a useful task.
Where: Paste into a Claude conversation with the referenced material.
Prepare: Supply authorised notes, a goal and a concrete example of the result you want.
These are instructions to evaluate, not proof that the resulting facts are correct.
Templates reviewed for clarity and product fit; provider execution and output quality are not independently verified.
1. Turn rough notes into an operator brief
Using only [NOTES], prepare a decision brief for [AUDIENCE]. Separate confirmed facts, open decisions and next actions. For every action name an owner only if supplied; otherwise write owner needed. Preserve dates exactly. End with three questions whose answers would change the plan.
Check the result: No invented owners, deadlines or decisions; each action traces to the notes.
2. Match the useful parts of my writing
Read [GOOD EXAMPLE] and [WEAK EXAMPLE]. Identify three concrete differences in clarity, detail and tone. Rewrite [DRAFT] for [AUDIENCE] using the useful qualities of the good example. Preserve all supported facts and flag any claim that needs evidence. Show the revised draft and a short change list.
Check the result: The rewrite improves specific weaknesses without copying unrelated example facts.
3. Find contradictions in a project brief
Review [PROJECT BRIEF] for requirements that conflict or cannot be tested. Quote the relevant clauses in pairs. Explain the practical consequence and propose one question to resolve each conflict. Do not build anything or silently choose which requirement wins.
Check the result: Every conflict cites two actual requirements or clearly identifies missing evidence.
4. Create a teaching exercise from expertise
From [LESSON NOTES], create a ten-minute exercise for [BEGINNER AUDIENCE]. Include one worked example, one practice task and an answer rubric. Separate source-backed rules from your teaching analogies. Do not invent traditional references or scientific validation.
Check the result: A learner can complete the task and the rubric tests the stated lesson.
5. Prepare a clean handover
Convert [WORK LOG] into a handover with completed work, verified results, unresolved issues and the exact next action. Keep planned, implemented, tested and deployed separate. Include revision identifiers only when present. List missing evidence instead of filling it in.
Check the result: Someone else can resume without confusing plans with verified outcomes.
Gemini: start with a useful task.
Where: Paste into a Gemini conversation; add only files you are authorised to share.
Prepare: Replace bracketed fields and include the actual source material.
Availability of uploads and connected products varies. These prompts do not assume access to your Drive or email.
Templates reviewed for clarity and product fit; provider execution and output quality are not independently verified.
1. Make a bilingual workshop outline
Create a [DURATION]-minute outline from [TOPIC NOTES] for [AUDIENCE]. Write the main teaching in plain English and add short Hindi explanations for difficult ideas. Include time allocations and one practice activity. Flag any unsupported claim in the notes rather than presenting it as fact.
Check the result: Timings add up and the Hindi explanation preserves the same meaning.
2. Read a table without inventing causes
Using [PASTED TABLE], identify the largest changes and missing values. Show the arithmetic for each reported change. Separate observations from possible explanations. Do not infer customer motives or causation from this table. End with the additional data needed to investigate.
Check the result: Recalculate the reported changes independently and check units.
3. Draft a reply using approved facts
Draft a concise response to [CUSTOMER QUESTION] using only [APPROVED FACTS]. Match this tone example: [EXAMPLE]. If price, timing or eligibility is missing, state the question we need to answer rather than guessing. Provide the reply and a private checklist of facts to verify before sending.
Check the result: No fabricated promises, prices or eligibility rules; do not send automatically.
4. Turn a lesson into a revision quiz
Create six questions from [LESSON]. Mix recall, application and one error-spotting example. Put the answers after the questions, explain why each is correct and identify the passage supporting it. Avoid testing knowledge that is absent from the lesson.
Check the result: Every answer is supported by the supplied lesson and has one clear interpretation.
5. Simplify a confusing instruction sheet
Rewrite [INSTRUCTIONS] for a first-time user completing [TASK]. Preserve prerequisites, warnings and decision points. Use one action per numbered step. Mark missing screenshots or undefined terms. Finish with a test someone can perform to confirm completion.
Check the result: A new user can follow the sequence without losing necessary conditions.
NotebookLM: start with a useful task.
Where: Select the relevant sources in a notebook, then use its source-grounded chat.
Prepare: Add the authorised documents first and check that the selected source set covers the question.
A citation is a starting point for checking a claim; open it and verify the passage. Missing sources limit the answer.
Templates reviewed for clarity and product fit; provider execution and output quality are not independently verified.
1. Build an evidence table
From the selected sources, list the claims about [TOPIC] in a table: claim, supporting source citation, qualification and unanswered question. Separate direct source statements from inference. If the sources do not establish a claim, say so.
Check the result: Open every citation and check that it supports the adjacent claim.
2. Compare two source versions
Compare the selected old and new versions of [DOCUMENT]. Identify changed requirements, removed statements and unchanged conditions. Cite both versions where a change is claimed. Do not infer why the author made the change.
Check the result: Each claimed change appears in the actual before and after documents.
3. Prepare a source-grounded FAQ
Create eight beginner questions about [SUBJECT] using the selected sources. Answer each briefly with a supporting citation. Put questions the sources cannot answer into a separate section called Further evidence needed.
Check the result: Unanswered questions remain separate from supported answers.
4. Find disagreement without forcing consensus
Where do the selected sources disagree about [QUESTION]? Quote short relevant passages with citations, explain whether definitions or dates differ, and list what further evidence could resolve the disagreement. Preserve uncertainty.
Check the result: The answer does not blend incompatible claims into an invented consensus.
5. Make a study path with evidence
Build a beginner-to-intermediate study sequence for [GOAL] using the selected sources. For each step give the source section, one practice question and a criterion for moving on. Mark topics that require a source not currently included.
Check the result: The sequence points to usable source sections and does not pretend the notebook is exhaustive.
Perplexity: start with a useful task.
Where: Use a new search conversation and state the scope explicitly.
Prepare: Set the question, location and date range. Open important source links yourself.
Requested source/date preferences are instructions, not guaranteed search filters. Check publication and event dates.
Templates reviewed for clarity and product fit; provider execution and output quality are not independently verified.
1. Check a product capability
Does [PRODUCT] currently support [SPECIFIC CAPABILITY] in [PRODUCT MODE]? Prioritise official documentation. Separate generally available, preview and unsupported cases. Link the pages supporting each conclusion and give the date checked. If documentation conflicts, show the conflict.
Check the result: The source describes the exact product mode and current availability.
2. Compare practical limits
Compare [TOOL A] and [TOOL B] for [ONE JOB] in [REGION]. Use official sources for file limits, export formats and account requirements. Mark unavailable facts unknown. Do not choose a winner until you relate those limits to [MY CONSTRAINTS].
Check the result: Compare equivalent plans and distinguish facts from recommendations.
3. Find primary evidence for a claim
Investigate this claim: [CLAIM]. Find primary evidence where possible, explain what each source actually establishes and identify limits or contradictory findings. Separate a lack of evidence from evidence that the claim is false.
Check the result: Read the original evidence; a repeated secondary claim is not independent confirmation.
4. Build a dated change brief
What changed in [PRODUCT OR STANDARD] between [START DATE] and [END DATE]? Prioritise official release notes. List announcement date, effective date, practical impact and source. Exclude older changes republished inside a recent article.
Check the result: Dates refer to actual changes, not only the article publication date.
5. Find documentation for an error
Find official troubleshooting guidance for [REDACTED ERROR] in [PRODUCT AND VERSION]. Explain which conditions match my case: [CONTEXT]. Suggest a short read-only diagnostic sequence. Mark version mismatches and avoid unverified commands from forum posts.
Check the result: Verify version compatibility before running any suggested command.
Lovable: start with a useful task.
Where: Use the project conversation; start planning before requesting code changes.
Prepare: Use a project you own and record the current working checkpoint.
Generated code still needs review, permission checks and executable tests. A preview is not production acceptance.
Templates reviewed for clarity and product fit; provider execution and output quality are not independently verified.
1. Plan one user journey
Plan [USER JOURNEY] for [AUDIENCE]. Ask about missing inputs, permission boundaries and success criteria before changing code. Show screens, states and the smallest first component. Preserve [WORKING FEATURES]. Do not add unrelated integrations.
Check the result: The plan includes empty, loading, success and error states and names the permission boundary.
2. Build one accessible form
Implement only the [FORM] in the agreed plan. Use visible labels, keyboard access, field-level errors and a clear success state. Use this real example content: [CONTENT]. Preserve the existing design system and data contracts. Show how you tested invalid and valid input.
Check the result: Try keyboard-only use, missing fields, valid submission and duplicate clicks.
3. Repair a reproduced UI defect
Investigate [STEPS TO REPRODUCE] with expected [EXPECTED] and actual [ACTUAL]. Locate the responsible component before editing. Propose the smallest fix and protect [BEHAVIOUR]. After the change, rerun the reproduction and relevant regression checks.
Check the result: The same failure case passes after the patch and protected behaviour remains intact.
4. Review access to a private record
Review how [PRIVATE RECORD TYPE] is read and edited in this project. Trace the actual server-side ownership checks. Identify unsupported assumptions and propose tests for owner, another account and anonymous access. Do not expose real private data in test fixtures.
Check the result: UI hiding alone is not accepted as authorisation enforcement.
5. Prepare a release handover
Prepare a handover for the current checkpoint. List implemented changes, tests actually run, remaining failures, required environment-variable names without values and rollback instructions. Distinguish preview from deployed state. Do not publish or deploy as part of this request.
Check the result: Every test and deployment claim has an identifiable result or revision.
Midjourney: start with a useful task.
Where: Use the image prompt field. Replace bracketed subjects; choose dimensions in the product controls.
Prepare: Decide subject, composition, lighting and intended crop. Use references only with permission.
These describe images, not exact layouts or editable diagrams. Add factual labels and precise typography in an editor.
Templates reviewed for clarity and product fit; provider execution and output quality are not independently verified.
1. Editorial workshop cover
Editorial photograph of [SUBJECT] teaching a small group in a bright modern classroom, attentive expressions, natural window light, navy and warm cream palette, subject grouped on the right, open uncluttered space on the left for a title, realistic materials
Check the result: Inspect faces, hands, crop and available title space before adding text.
2. Product still-life concept
Studio still life of [PRODUCT] on a matte stone pedestal, soft side lighting, restrained warm gold reflections, clean royal blue backdrop, realistic surface texture, premium catalogue composition, clearly separated silhouette
Check the result: Check product geometry against the real item; concept imagery must not misrepresent a sale item.
3. Learning concept illustration
Minimal editorial illustration of a person organising scattered notes into three clear groups on a desk, crisp geometric forms, ink blue and muted saffron accents, generous negative space, calm educational mood, landscape composition
Check the result: Use an HTML caption to explain the concept; do not treat generated shapes as factual data.
4. Portrait-friendly thumbnail base
Close editorial portrait of [AUTHORISED SUBJECT DESCRIPTION] with a thoughtful expression, soft directional light, dark blue background with subtle warm rim light, eyes clearly visible, strong separation, generous margin around the head for cropping
Check the result: Confirm likeness permissions and inspect facial details at the intended thumbnail size.
5. Consistent lesson-background concept
Quiet architectural interior for an educational lesson background, modern Indian study room, pale limestone, dark blue shelving, restrained brass details, symmetrical composition, soft daylight, uncluttered central area, realistic editorial photography
Check the result: Check contrast behind actual lesson text and avoid busy details at mobile size.
Runway: start with a useful task.
Where: Use the video prompt for a compatible image-to-video mode with your authorised input image.
Prepare: Choose a clear starting frame and one dominant motion. Set duration in the product controls.
Model modes differ. These motion prompts are starting points, not guarantees of exact timing, identity or physics.
Templates reviewed for clarity and product fit; provider execution and output quality are not independently verified.
1. Gentle product reveal
The camera slowly moves closer to the product. A soft highlight travels across its surface. The product remains stationary on the pedestal. The movement is smooth and restrained.
Check the result: Inspect for warped product geometry and unwanted logo changes.
2. Calm classroom establishing shot
The camera makes a slow lateral move across the classroom. The seated participants make small natural movements while the teacher points to the board. Daylight remains consistent.
Check the result: Check people, board contents and motion continuity frame by frame.
3. Subtle portrait animation
The subject breathes naturally and makes a small head turn toward the camera. The camera remains fixed. The background is still, with soft consistent lighting.
Check the result: Verify likeness and facial stability; obtain permission for the reference portrait.
4. Atmospheric desk detail
A page on the desk lifts gently in a light breeze and settles. The camera slowly pushes toward the notebook. The objects keep their shape and position. The motion feels quiet and observational.
Check the result: Inspect object stability and avoid using invented notebook text as real evidence.
5. Transition-ready landscape
The camera rises slowly above the foreground plants to reveal the open landscape. Leaves move gently in the breeze. The horizon stays level and the lighting remains natural.
Check the result: Check horizon stability, edge artefacts and suitability for your actual edit.
ElevenLabs: start with a useful task.
Where: Use Text to Speech and paste only the narration text, not editorial instructions.
Prepare: Choose an authorised voice and the intended language. Replace bracketed words, spell difficult numbers and preview a short sample.
These are original narration scripts. Delivery, pronunciation and duration need listening checks; voice consent and usage rights remain your responsibility.
Templates reviewed for clarity and product fit; provider execution and output quality are not independently verified.
1. Workshop opening
Welcome to [WORKSHOP NAME]. Today, we will practise one useful skill: [SKILL]. You do not need to know every technical term. Keep one real question ready, follow the example, and check whether your final result answers that question clearly.
Check the result: Listen for the workshop name, pacing and natural pauses.
2. Short product walkthrough
Start by opening [SCREEN NAME]. Choose [ACTION], then enter [INPUT]. Before continuing, check [IMPORTANT DETAIL]. When [SUCCESS SIGNAL] appears, this step is complete. If you see an error, keep a note of the message before trying again.
Check the result: Match every spoken screen/action name against the actual product.
3. Lesson transition
You have seen the example. Now try it with your own material. Keep the goal the same, change one instruction, and compare the results. Look for a specific improvement rather than a longer answer. Pause here while you complete the exercise.
Check the result: Leave enough editing space for the pause and avoid rushing the instructions.
4. Hindi practice instruction
अब अपनी एक वास्तविक समस्या चुनिए। पहले साफ़ लिखिए कि आपको क्या परिणाम चाहिए। फिर एक अच्छा उदाहरण जोड़िए। उत्तर मिलने के बाद देखिए कि वह आपके सवाल का जवाब देता है या केवल सामान्य बातें दोहराता है।
Check the result: Use a compatible Hindi voice and listen for pronunciation and rhythm.
5. Evidence-aware conclusion
This example shows what happened under the conditions we tested. It does not prove the same result in every situation. Keep the useful part, note the remaining uncertainty, and choose one small next step that you can check for yourself.
Check the result: Ensure the surrounding lesson actually includes the test being referenced.
HeyGen: start with a useful task.
Where: Use Video Agent with your reviewed script and authorised reference assets.
Prepare: Replace placeholders and supply the real facts, brand details and intended audience before generating.
Review the proposed video plan, captions, pronunciation and asset rights before publishing. Output is not an authenticated recording of an event.
Templates reviewed for clarity and product fit; provider execution and output quality are not independently verified.
1. Explain one workshop exercise
Plan a short educational video for [AUDIENCE] explaining [EXERCISE]. Use this reviewed script: [SCRIPT]. Show the starting input, the action and the expected result as three scenes. Use calm blue and cream graphics with readable captions. Use only supplied facts and authorised assets.
Check the result: The visual steps match the actual exercise and captions remain readable on a phone.
2. Create a software walkthrough
Use the attached authorised screenshots to explain [WORKFLOW]. Follow this script: [SCRIPT]. Highlight the real control in each screenshot instead of inventing a product interface. Keep the cursor/action order aligned with narration. Ask for any missing screen before final generation.
Check the result: Compare each highlighted control and action with the current product.
3. Turn an FAQ into a clear explainer
Create a concise answer to [FAQ] for [AUDIENCE] using [APPROVED ANSWER]. Begin with the question, explain the answer with one example and end with [NEXT ACTION]. Use restrained motion graphics and a neutral professional delivery. Do not add unsupported claims or testimonials.
Check the result: All factual statements come from the approved answer.
4. Introduce a course honestly
Create a course introduction using [COURSE OUTLINE]. Explain who it is for, prerequisites, one practical exercise and the expected learning outcome. Use [SCRIPT] as the narration. Mark absent details for review. Avoid income promises, fake student quotations and unsupported credentials.
Check the result: The video accurately reflects the course and makes no invented promises.
5. Revise one scene only
In scene [NUMBER], replace [CURRENT VISUAL] with [NEW AUTHORISED VISUAL] and use this exact reviewed narration: [TEXT]. Preserve the other scenes, voice choice and overall style. Show the revised scene for review before any broader changes.
Check the result: Compare unaffected scenes with the previous version and check the requested revision.
Suno: start with a useful task.
Where: Use Custom mode: paste the style description into Styles and enable Instrumental for these examples.
Prepare: Choose the intended use and review the current plan's usage terms before commercial publication.
These are music direction, not lyrics or guaranteed durations. Listen, trim and check licensing for the actual output.
Templates reviewed for clarity and product fit; provider execution and output quality are not independently verified.
1. Quiet lesson background
Gentle instrumental, sparse acoustic piano, soft warm pads, slow steady pulse, restrained dynamics, spacious arrangement that leaves room for spoken teaching
Check the result: Music does not mask narration; verify there are no unexpected vocals.
2. Workshop opening cue
Uplifting instrumental, bright plucked strings, light hand percussion, warm modern Indian ambience, clear opening motif, confident but unhurried energy
Check the result: The cue suits the audience and can be cleanly faded beneath speech.
3. Product demonstration bed
Minimal electronic instrumental, clean soft synth pulses, light percussion, precise steady rhythm, understated optimistic mood, uncluttered midrange
Check the result: Avoid distracting changes underneath the demonstrated steps.
4. Reflective closing music
Reflective instrumental, warm felt piano, delicate ambient textures, slow tempo, gentle descending motif, calm resolution and soft ending
Check the result: Check the ending and edit it to fit the actual closing narration.
5. Practice-time loop concept
Neutral instrumental study music, subtle marimba pattern, soft bass pulse, even dynamics, patient relaxed mood, repetitive gentle structure suitable for an exercise timer
Check the result: Check loop seams in an editor; a style prompt does not guarantee a seamless loop.