Engineering & AI
Lemo-Opuscar: approve a video style before a full render
Lemo-Opuscar provides templates for making videos with code so you can approve colors, typography, and pacing on one scene before rendering the full clip.
Summary
- Use the same scene to see which style makes the idea clear before rendering the full video.
- The library has 99 styles, each with a demo film and directions for Claude Code.
- Approve a frame and then a moving sample. Check text, timing, and audio in the aspect ratio you plan to publish.

You need a video that explains a process, but a brief that says “clean and modern” can leave everyone picturing a different clip. Lemo-Opuscar lets you watch style demos and try a scene of your own before committing to a look for the whole video.
How does the repo help you choose a style?
The library groups 99 styles into 15 categories. Each has a film you can watch and a STYLE.md file that guides the agent on layout, movement, and sound. A moving reference shows how a style directs attention from one detail to the next. Demo gallery
Claude Code writes code to render frames with Canvas or WebGL and assemble them with audio. The video is rendered in code. Three styles still require an image tool for their illustrations: Manga Panels, Text Flash Cuts, and Comic History Cartoon. README at the reviewed commit
When is it worth using?
- When movement has a clear job. Try it for an explainer, diagram, or data video. For example, use motion to link the order confirmation to the customer notification that follows.
- When you want a repeatable look. If several videos need the same colors, type and rhythm, adapt a library style, review a frame and save your own version. Custom style workflow
- When real footage is central. If viewers need to see the real interface or the physical product, use actual recordings as source material and use graphics to explain key moments.
Test one scene and decide whether to continue
- Choose a 10–15 second scene. For example, show the moment the system sends a notification after confirming an order. Keep the content fixed while comparing styles.
- Watch two demos and pick one to try. Compare Swiss Motion Graphics with Whiteboard Explainer. For a vertical post, request that aspect ratio from the start. Preview a frame when adapting a style, or ask to review the storyboard before rendering a film.
- Watch on the intended device. Play it on a phone without sound first and check whether the order of events is clear. Turn sound on and see whether the narration matches the visuals and stays audible over the music. If you have to pause to read, adjust the text size or timing before extending the cut.
The README calls for Node.js 20+, FFmpeg 7+, and Python 3.11+ or uv. The author estimates about 30–60 minutes per film and substantial agent token use. Measure actual time and usage on your sample before scheduling a series. Environment requirements and estimates
Preparing the AI agent
Provide two references you have watched, the script for one scene, the aspect ratio, approved colors and fonts, and assets you can use. Ask the agent to stop for the storyboard or test frame, then deliver the export and source code so the team can make changes.
For client work, read the license by file type. It gives permission to use the project documentation to make commercial films and include it in that film’s deliverables under the stated terms. Third-party assets, such as fonts, music and some voice tracks, have their own terms. Repository license
HubCom reviewed the documentation and source at commit f9e2042 on November 20, 2026. HubCom has yet to render a film with it or use it in a client project.
Terms in this article (3)
- Lemo-Opuscar
- A library of film styles and instructions for rendering video in code with Claude Code.
- Storyboard
- A sequence of draft shots used to review the story and timing before rendering.
- FFmpeg
- A set of tools for processing images and audio when exporting video.
Frequently asked questions
Does Lemo-Opuscar need a video generation model?
Video frames are rendered in code. The README identifies three styles that use an image tool for their illustrations.
Can I reuse a custom style across clips?
Yes. The custom style workflow lets you approve a sample and keep its directions, demo, and source code for later use.
What should I check before rendering the whole film?
Use one scene to make sure viewers understand the point, can read the text, and can hear the narration in the planned aspect ratio.
Sources
- Lemo-Opuscar README at the reviewed commit, Lemomo
- Lemo-Opuscar demo gallery, Lemomo
- Custom style workflow, Lemomo
- Licenses by file type, Lemomo