A little help.
Back to creating.

It is a free collection of 20 prompt drafts covering planning, editing, B-roll, audio, color, motion graphics, automation, and delivery. Choose a prompt for your task, read its requirements, and bring it into your AI assistant. It is a starting point for your own workflow, not an application that edits an entire video for you.

Use the free-kit signup on the main website. Enter an email address you can access and follow the confirmation instructions in your inbox. Keep the kit access email and bookmark the library page once you reach it so you can return to the prompts.

Check your spam, junk, and promotions folders, then search your inbox for Andrew Farmer or Edit with AI. Make sure you used the intended email address and allow a few minutes for delivery. If it still does not arrive, contact support with the address you used and approximately when you signed up. You do not need to send your email password.

Try the most recent kit email and open its link in your regular browser. If the link was wrapped across lines when copied, use the original clickable link instead. If it still fails, contact support with the error text and signup email. Do not post private confirmation links publicly.

The library offers a ZIP download plus Markdown and JSON versions of the prompt collection. Extract the ZIP first. Open the Markdown file in a text or Markdown reader to read and copy prompts. The JSON file is structured data for tools and is not an installer. You can also use the online library without downloading the files.

Download it again using a stable connection and check your browser's Downloads list for a completed file. Extract the ZIP before opening its contents. If the ZIP still fails, use the individual Markdown download or read prompts in the library. Tell support which file failed, your browser, and the exact error.

Start with the task you want help with, such as rough cut, B-roll, dialogue, or export. Search for that task, then narrow by category, software, prompt type, or requirements. Filters work together; if you get no results, clear them and try a broader term. Open a prompt to review its instructions before copying it.

Open the prompt details and use Select text, then copy with Command-C on Mac or Ctrl-C on Windows. You can also copy from the Markdown download. Some browser permissions or privacy settings restrict clipboard access; the prompt itself is still usable.

Paste the full prompt into the AI assistant that fits its listed requirements. Replace placeholders with your project details, supply the requested materials, and answer follow-up questions. Review the response before applying it to your edit. A prompt pasted into a chat does not automatically connect that chat to your editing software.

Ready-to-use prompts help an AI assistant analyze, plan, or advise using the information you provide. Create-with-AI prompts ask an AI coding workflow to build something, such as a graphic or script, and may need a project, development tools, or editor integration. Read the software and requirements on each prompt before starting.

You do not need to buy AI Motion Bridge to read or use the starter-kit prompts. Requirements vary: many planning prompts work in an AI chat, while graphics and automation prompts need additional tools or configuration. Any paid editor, AI account, or other third-party service is separate from the free kit.

Many prompts produce plans or editing advice you can apply manually in different editors. Prompts that generate code or automate an editor have narrower requirements. Check the software label and tell the AI your exact editor and version; do not run a script written for a different application.

The collection is labeled as prompt drafts that need real-world testing. Treat the outputs as suggestions to check against your footage, software, and goals. Start on a copy or small test project for any generated script or automation, and share a specific example with support if a prompt is confusing or fails.

Provide the video goal, audience, editor version, desired length, and relevant source material. Explain what was wrong with the first answer and ask for one specific revision at a time. Tell the AI to flag missing information instead of guessing. Verify technical settings and creative choices yourself before using the output.

Use an accurate transcript with source timecodes, and explain the story goal and target length. For frame-based edit lists, include the source frame rate and timecode format. Check suggested cuts against the actual media; a transcript cannot reveal every visual or audio problem. A written edit list still needs a compatible way to apply it in your editor.

The planning prompts can suggest visuals, match ideas to a supplied asset inventory, or recommend placements from your script and timecodes. They cannot see files you have not supplied, and a plan alone does not move clips onto a timeline. Review availability, rights, and timing, then apply the suggestions manually or through a separately configured workflow.

Use them as starting points. Audio advice needs context about the recording and voice; color advice needs references and your camera/color-management pipeline. Compare before and after, listen and view on suitable equipment, and adjust for the actual footage. A written description alone cannot guarantee a clean mix or an accurate grade.

Those prompts are written for an AI coding workflow using a Remotion project. They are separate from AI Motion Bridge's editable OGraf workflow in Resolve. Check that the required project and tools are set up before using them. If your goal is an editable AI Motion Bridge graphic, use that product's installation and Getting Started instructions instead.

Save a backup and test on a copy of your project. Confirm the script targets your editor version and uses APIs documented for that version. Give the AI the exact error and the step that failed. An AI chat needs an explicitly configured connection or execution method to control an editor; generating code alone does not provide one. Avoid repeatedly running a partially completed script without checking what it changed.

Reload the page and make sure JavaScript is enabled. Try your browser's normal window if an extension or strict blocking mode may be interfering. You can use the Markdown or ZIP download while troubleshooting. If the issue continues, send support your browser/version and the message shown on screen.

The kit contains prompts and their usage requirements. Installation, tool configuration, and complete workflow training are separate from the collection. Start with a planning prompt that matches the tools you already have, and use the product-specific guide when a prompt requires a coding project or editor connection.

Use the unsubscribe link in an email from Andrew Farmer. If it does not work, contact support with the subscribed address so the issue can be investigated. Unsubscribing from emails is separate from submitting a support request; the support form does not sign you up for the mailing list.

Create custom motion graphics with AI Motion Bridge using Codex or Claude Code. Your assistant authors and revises the design from your creative direction. AI Motion Bridge checks the graphic, saves it to your library, and handles placement in DaVinci Resolve as a native OGraf clip with supported Inspector controls. You can continue refining the design with either assistant.

The starter kit is a collection of prompt drafts for a range of editing tasks. AI Motion Bridge is a separate paid tool with an installer and a specific AI-assistant-to-Resolve motion-graphics workflow. Downloading the free kit does not install or purchase AI Motion Bridge.

The current launch workflow supports an Apple silicon Mac running macOS 14 or later, Codex or local Claude Code, and DaVinci Resolve Studio 21.1.1. Verify those requirements against the current product page and the guide included with your download before installing. Separate app licenses and AI-service costs are not included with AI Motion Bridge.

The current launch is for Apple silicon Macs. Windows and Intel Macs are outside the officially supported setup. Do not assume that a source file or an installer from another platform makes those systems supported. Contact support before purchasing if you are unsure about your computer.

AI Motion Bridge 1.6.0 supports Codex and local Claude Code with DaVinci Resolve Studio. The single Mac installer lets you choose Codex, Claude Code, or Both, using one shared engine and library. Other editors and AI platforms are not officially supported. Rendered video does not retain native OGraf Inspector controls in another editor.

The stated launch requirement is DaVinci Resolve Studio 21.1.1. The free edition is not the supported configuration for this release. Check your installed edition and version before purchasing or troubleshooting, and use the product page for any future compatibility announcements.

Extract the Mac installer supplied with your purchase, read “* START HERE - Mac Installation.txt”, and open the installer app. If macOS blocks the first launch, follow that guide and the Mac security-warning answer below. Choose Codex, Claude Code, or Both. It installs one engine, bundled tools, the selected assistant skills, and the Resolve library integration. Install and sign in to your chosen assistant separately. Restart Resolve, then choose Workspace → Workflow Integrations → AI Motion Bridge. Start a fresh local assistant session with access to your authoring folder. For Claude, use its Code tab rather than Cowork or a cloud session. A new library starts empty; updates preserve existing graphics.

Use Claude Code locally on the same Mac as AI Motion Bridge and DaVinci Resolve. In the Claude desktop app, choose the Code tab and a local session with access to your authoring folder. Ordinary Claude chat, Cowork, and cloud coding sessions are not supported by this local integration. Install and sign in to Claude Code separately, then choose Claude Code or Both in the AI Motion Bridge installer. Start a fresh session after installation.

No. One AI Motion Bridge Mac installer offers Codex, Claude Code, or Both. Selecting Both connects the two assistants to the same installed engine and library. Either assistant can help create and revise graphics; identify the existing graphic and files when switching conversations. Updates to the engine benefit the shared product. When installing an update, choose Both to update both assistant integrations together. Separate assistant apps and accounts are still required.

The Mac installer package bundles its runtime components, including Python, Node, and the graphics browser. Follow that package's guide before installing separate developer tools. A source-only archive has different prerequisites; if your instructions do not match what you downloaded, contact support with the package name.

The current installer is not signed with an Apple Developer ID or notarized by Apple, so macOS may block its first launch. For the official purchase download, extract the ZIP and read “* START HERE - Mac Installation.txt”. Try opening the installer; if Apple says it cannot verify the app or check it for malicious software, dismiss that alert, then open System Settings → Privacy & Security → Security → Open Anyway. Confirm Open and authenticate if asked. Continue through the installer and choose Codex, Claude Code, or Both. These steps apply only to that verification warning. If the message says “will damage your computer” or “damaged”, stop and contact support. If Open Anyway is unavailable, send support the exact warning. Do not disable system-wide security.

Start a fresh local session after installation and ask to use AI Motion Bridge. In Claude Code you can also type /ai-motion-bridge. Check that you selected your assistant in the installer and are using the same Mac account. Restart the assistant if needed. Claude cloud sessions and Cowork do not use this local integration. If it remains unavailable, send support the installer result and app versions.

Open the supported Resolve Studio version and the project you intend to use. Follow the connection checks in your Getting Started guide, including any required application permissions. Ask your assistant to check the connection before creating a graphic. If it fails, capture the exact connection error and your versions; do not change project settings at random.

Start with one simple graphic, such as a lower third or a title. State the exact text, visual style, colors, duration, and how it should enter and leave. Tell your assistant to use AI Motion Bridge and identify your intended Resolve project and timeline. Review a preview and ask for a small revision before building a more complex design.

You provide creative direction in everyday language while the AI handles graphic authoring. You still need to follow installation instructions, review the result, and describe revisions clearly. If a step fails, share the actual error rather than guessing at code changes or repeatedly rerunning the same request.

AI Motion Bridge is designed to help create graphics around your own ideas. It is not a fixed pack of premade designs. You can describe a new graphic or ask the AI to adapt an existing one, then refine the result to suit your project. Clear references and specific timing requests help guide the design.

Tell your assistant your intended width, height, frame rate, and duration, or identify the timeline whose format it should follow. The workflow can author different aspect ratios and sizes within the supported tools' limits. Check the resulting graphic in the target timeline before final export, especially for text margins and cropping.

Yes. Supply a reference you are allowed to use, your exact text and color values, and a description of the features you want. Explain the intended layout and motion rather than relying on the image alone. Review the result for accuracy; a reference guides the design but does not guarantee an identical recreation.

The workflow supports source images and still-image placeholders. Provide the actual image files and explain how they should be placed or animated. Keep those assets in a stable location with the graphic's files. Video drop zones are not implemented in the current workflow, so a still-image placeholder should not be treated as a video player.

Make sure the intended font is installed and available on the computer rendering the graphic. System fonts are not automatically embedded in the package. If a font is missing, install a properly licensed copy or ask for an available substitute, then verify the line breaks and layout again. Follow the font provider's licensing terms when sharing files.

Tell Codex or Claude Code what should change: for example, a slower entrance, larger headline, tighter spacing, or a different color. Identify the existing graphic and ask for a revision to that design. Supply a screenshot or timing note if useful, and mention any Inspector edits you want preserved. If you switch assistants or start a new conversation, point it to the same graphic and source files. Review the result; a design may take several iterations.

Select the imported native OGraf clip and use the controls exposed for that graphic. Depending on how it was authored, these can include text, fonts, colors, layout, and transforms. Only exposed controls are directly editable there. For a larger structural or animation change, ask your assistant to revise the original graphic.

Select the intended OGraf clip and open its Inspector. AI Motion Bridge installs the custom controls and saves/reopens the project as part of placement. Raw JSON import or dragging native media from the Media Pool does not install the full custom Inspector. Use the AI Motion Bridge library or checked install workflow. If controls are still missing, ask your assistant to inspect the job before retrying; preserve existing edits.

AI Motion Bridge saves your checked graphic to your library first. With your intended Resolve timeline open, choose Place at the playhead, Append to the end, or Not now. Placement uses a suitable video track in the current timeline and preserves its format. Not now keeps the graphic in your library for later. A separate timeline is created only when you explicitly request one.

The revision workflow is designed to preserve supported Inspector edits and trim when it can identify the existing graphic. Tell your assistant which graphic to revise and that your Resolve edits must be preserved. Unsupported expressions, connections, or keyframes may stop that process. Keep a backup and inspect the revised clip before replacing an approved version.

Ask your assistant to revise the existing AI Motion Bridge graphic and describe the change precisely. Identify the graphic's original files and the Resolve clip if available. Use the Inspector for exposed settings; use an AI revision for animation or design changes that are not exposed. Compare the updated result with your intended edit before keeping it.

Keep the graphic source, generated packages, job folders, and any linked assets. Resolve can reference files by their location, so importing a graphic does not mean all of its supporting files are safely embedded in the project. Store them in a stable project folder and include them in your backups.

Check whether a graphic package, image, job folder, or engine version was moved or deleted. Tell Codex or Claude Code what moved and ask it to inspect the missing references. Restore original locations from your backup if possible, then reopen and verify the project. Preserve the remaining files while troubleshooting. Contact support with the missing paths and what changed if the issue continues.

Plan to bring the supporting graphic packages, source/job folders, images, and required fonts as well as the Resolve project. The destination needs a supported AI Motion Bridge and Resolve setup. File locations may need attention because references can use absolute paths. Verify every graphic on the destination before deleting files on the original Mac; consult your purchase terms for licensing questions.

Check your AI Motion Bridge library first: a checked graphic is saved before placement, so Not now or a placement failure can leave it ready for later. Confirm the intended Resolve timeline is open. Ask your assistant to inspect the existing job and report which stages completed before retrying. Keep the files and avoid repeating an uncertain import, which may already have changed the timeline.

Yes. Copy the exact error into your local Codex or Claude Code conversation and explain what you were doing. Ask it to use AI Motion Bridge, inspect the existing job and Resolve state, explain the likely cause, and suggest a safe next step while preserving your library and edits. It can help diagnose setup, missing-file, connection, or graphic issues. Some errors require a product update or support; do not assume every error can be fixed by retrying.

Include the full error text, what you asked for, the graphic name, and whether it reached your library or Resolve timeline. Add app versions and the job or file location if available. Try: “Use AI Motion Bridge to inspect this error and the existing job. Explain what failed and what already completed. Help me recover while preserving my library, files, and Inspector edits. Check before retrying an import.” Share only the relevant details and leave out passwords or private customer information. If it remains unresolved, send support the error and the steps already tried.

Save regularly and allow an active operation time to finish. If Codex, Claude Code, or Resolve becomes unresponsive, avoid starting duplicate imports. After recovering the app, ask your assistant to inspect what completed and reopen your saved project. A fresh Codex or Claude Code conversation, a simpler request, or restarting the affected app can help. Keep the original error and project details if the issue repeats.

Ask your assistant to inspect the existing job and Resolve state before doing anything else. A stopped request may already have saved a library item or placed a clip. Do not repeat the full request or force an uncertain stage to run again. Keep job files, package paths, and backups intact; resume only when the engine confirms that the recorded state supports it. Contact support if the recovery state is unclear.

Compare the graphic’s size and frame rate with the target timeline, then check clip scaling, fonts, linked images, and any Inspector changes. Review the same moment in both previews. Give Codex or Claude Code screenshots and timeline settings and ask it to inspect the mismatch. If it persists, include those details and what you tried in your support request.

Download the current installer using your original purchase-email link, save your work, and follow the included update instructions. Select Codex, Claude Code, or Both; choose Both to update both integrations together. Unselected assistant integrations stay on their existing version. The installer preserves your library, retains earlier engines, and backs up replaced skills. Restart Resolve and start a fresh assistant session. Keep older engines and graphic packages referenced by existing projects.

Check AI Motion Bridge's stated compatibility and the update notes first. A newer editor or operating-system release is not automatically verified for this workflow. Keep backups and avoid changing multiple tools in the middle of an important project. If you already updated and something broke, include the previous and current versions in your support request.

Check the purchase confirmation and delivery instructions from the checkout provider, including spam or junk folders. Make sure you are checking the email address used at checkout. If you still cannot access the product, contact support with that email, purchase date, and order reference if available. Do not send full card details or make a duplicate purchase to fix access.

AI Motion Bridge is a one-time purchase with no recurring AI Motion Bridge subscription. You can use the tool to create new graphics without buying each one separately. Your editor license and any AI-service subscriptions, usage charges, or limits are separate and determined by those providers.

Your purchase includes improvements, compatibility updates, and fixes released for AI Motion Bridge for the lifetime of the product. Separate future products or independently sold expansions are not automatically included. Check the product page and the instructions supplied with an update for its requirements and installation steps.

Review the AI Motion Bridge product page and the final checkout summary before paying. Those show the current offer and included items. Keep your order confirmation as the record of your purchase. If the product page and checkout appear to disagree, contact support before completing the purchase.

Check your checkout confirmation and payment-provider status before trying again; a pending authorization is not always a completed purchase. Contact support with your checkout email, date, and order reference. For a suspected duplicate, include both references if you have them. Never include a full card number, security code, or banking password.

AI Motion Bridge is licensed to one user for personal and commercial client work. You may deliver finished work to clients, but may not redistribute the software, installer, Codex or Claude Code skills, or purchase download link. Digital sales are final and refunds are not offered except where required by applicable law. Read the purchase terms linked in this page’s footer, or contact support for access problems or billing errors.

Choose the product, explain what you expected and what happened, and include the exact error plus the steps that reproduce it. For AI Motion Bridge, include your Mac model, macOS version, Resolve edition/version, which assistant you use (Codex or Claude Code), and the assistant and installer versions if known. Mention any troubleshooting your assistant already tried. For kit access, include the signup email. A short, specific example is more useful than an entire project dump.

This form accepts text only. Paste a short error message or describe what the screenshot shows. If files are needed, support can discuss an appropriate way to share them in a reply. Do not submit passwords, private client footage, full payment details, or sensitive documents through the form.

Support requests are private messages, not public forum posts. Your name, email, selected product, and message are processed through Formspree so Andrew can review and respond. Submitting this form does not subscribe you to Kit or the marketing email list. Only include information needed to resolve your request.

Wait for a successful submission confirmation. If a verification step is shown, complete it before assuming the message was sent. If the form reports an error, keep a copy of your message and follow the on-screen instructions. A support reply will go to the email address you entered, so check it carefully and check your spam folder too.

Clear your search and filters, or try a simpler word related to the issue. If an answer still does not fit, use Contact Support and select the relevant product or Something else. Explain what you have already tried so support can focus on the next useful step. This help center does not have public discussions or member accounts.