Videos for freelancers and agencies

To make social videos for clients without building every animation by hand in a timeline editor or a motion design app, describe each video in a prompt and let Claude Code build it as a HyperFrames composition in the client's exact colors and fonts. Because the video is code, one design can be rendered again for every product, hook or language the client needs, and delivered as an MP4 or as a transparent layer for their own editor.

Below are what the license allows and a workflow that scales across clients.

What the license covers

• Client work is included. Unlimited videos for yourself and your clients, including paid ads, forever. You may edit and remix everything.
• Your copy stays private. Keep it in your own private storage; a private GitHub repository is fine.
• The files are never shared. Do not resell, publish or put them where others can get them: a public repository, a shared folder, a download link, another pack, a course, a template store or an AI training set.
• One buyer, one license. Every teammate who works with the pack needs their own copy.

In practice: your clients get the rendered files, and the kit stays with you.

A brand skin per client

The STYLE part of every prompt takes a skin or exact hex colors, fonts and sizes. For each client, write the look down once in a short skin file: background, card, text, muted text, an accent and a second accent as hex values, a display font and a body font, a motion personality and a handful of sounds that suit it.

One of the Prompt Vault's pro prompts builds such a skin from a logo: it reads the logo's colors, checks every text color against its background for WCAG AA contrast and saves the result as a skin file with a test render. Fonts come from the client's own files or from the pack's 16 open-source font families. Keep one skin file per client next to their projects, then point every prompt at it:

Use the skin in clients/[client]/brand-skin.md instead of the skin named in the prompt. Keep text inside x 60 to 940 and y 250 to 1440.

You can also adjust a built-in skin in one line, for example "Skin SAAS, accent #0E9F6E", and keep the rest of it.

Batch variants per client

Clients rarely need one video. They need one per product, location, offer, hook or language. The mcc-batch skill turns a finished video into a template with declared variables and renders a version per row of a spreadsheet:

1. Export the client's sheet as CSV.
2. Claude Code maps each column to a variable and writes a rows file with a short slug per row.
3. It renders the longest and the shortest values first, so you can see that the text fits.
4. One command renders the rest; a manifest lists what rendered and what failed.

Use my mcc-batch skill on this project. Rows: clients/[client]/locations.csv, one video per row. Map the columns to the variables, add a slug per row, render the longest name first and show me a frame, then render every row to renders/[client]/{slug}.mp4.

The same skill makes five hook variants of one video, an A/B pair of openings, versions in other languages and episode cards for a series. Rows with names in them are personal data: keep the rows and the renders on your own machine and delete them after delivery. See batch-rendering video variants.

Layers for the client's own editor

Clients who edit their own footage often only want graphics on top. Deliver layers:

• Transparent video as WebM (VP9 with alpha) or MOV (ProRes 4444) for desktop editors that read an alpha channel.
• A green-screen MP4 for CapCut and phone editors, keyed out with a chroma key. See green screen.
• Caption layers. The mcc-captions skill renders captions in one of 12 styles on their own, transparent, with a green-screen copy, or as SRT and VTT files.
• Recolored overlays. The 60 overlays come with their source, so they can be rendered again in the client's brand color.

Render this project as a transparent overlay for my client's editor: a .mov in ProRes 4444 and a .webm, plus a green-screen MP4 on #00FF00. Report the three paths and sizes.

Revisions without a rebuild

Because the video is code, a client note such as "shorter headline" or "use the green from the new logo" is an edit and a new render, not a new project. The same input gives the same frames, so a fix changes only what you asked for.

Working away from your desk

You do not need a computer. Claude Code runs in the cloud from the Claude app, with a free GitHub account and a private repository that holds the kit and your client projects. The video renders in the cloud session and you download the MP4 to your phone. The one-time phone setup takes about 15 minutes. English voice-overs from the offline voice-over tool run fine there; other languages are slow without a GPU, so make those on a computer.

A simple client routine

• Brief. Where it will be posted, the format and the client's real facts and numbers.
• Skin. The client's skin file, made once.
• First video. Built, checked and rendered as a draft for review.
• Template. Every text, number, color and image the client may change becomes a variable.
• Delivery. MP4s, transparent layers or caption files, named per row.

Getting started

Try the workflow on one client idea with the free starter kit. The full pack adds the templates, skills and sounds above under a license that covers client work, one copy per person.