Choose from 51 Film Styles to Tell Your Story lemo-opuscar

Choose a style for the job

Lemo-Opuscar lets Claude Opus 5.5 create coded stories, explainers and product films. The current repository contains 51 built-in styles, each with a sample film and production guide. Compare the styles, then have the agent develop shots, sound and pacing around your own content.

The four creator films above appear in this order. Start with the one closest to your intended use:

Film	Useful for	What to watch
Chinese Ink Wash: The Swordsman and the River	Cultural subjects, atmospheric shorts and brand stories	How empty space, ink and movement work together beyond a black-and-white palette.
Whiteboard Explainer: Einstein in Your Pocket	Educational videos, courses and product principles	How drawings and words follow the explanation before revealing the whole board.
Living Screencast: Clawd Moves In	Software tutorials, feature announcements and onboarding	How a pixel character directs attention and interface changes explain features.
Paper Pop-up: Pip’s Paper Adventure	Brand stories, picture books and narrative shorts	How page turns connect scenes while paper, lighting and character movement stay consistent.

The product film resembles a screen recording, but its interface is redrawn in code. It does not automatically record or operate your software. Your version needs accurate interface and feature references.

The creator’s article described 39 styles at publication. There were 43 when this site first collected the skill; the repository now lists 51. OPUSCAR 98 is a separate showcase, rather than part of that built-in count.

This exercise introduces a fictional article-saving app by showing how to find one article in a large collection. The example requests were written for this tutorial. We have not used them to generate a video. The sample films are the creator’s work, not results from this exercise.

Install the plugin and prepare the tools

In a terminal, install the Claude Code plugin:

claude plugin marketplace add lemomo-ai/lemo-opuscar
claude plugin install lemo-opuscar@lemolab

You need Node.js 20+, FFmpeg and Python 3.11+ or uv. The creator primarily develops on Apple Silicon Macs; Windows uses WSL. Complex 3D and shader-heavy styles place greater demands on the GPU.

The plugin keeps its shared library at ~/lemo-opuscar by default. Each film project lives in the directory where you start the task. Core dependencies, voice tools and instrument samples are installed as needed. Dependency downloads and online Chinese speech services require network access.

Alternatively, start from a clone:

git clone https://github.com/lemomo-ai/lemo-opuscar.git
cd lemo-opuscar
claude

In clone mode, projects go into films/<project-name>/, unlike plugin mode. Choose either route. This tutorial was checked against the current README, skill instructions and production guides; we did not install upstream dependencies or produce this example.

Define the user problem and prepare your materials

A feature video does not need to show every button. This example has one purpose: finding a saved article through search and filtering. Prepare collection, search-result and article-detail screenshots, with accurate labels and descriptions of the operations.

Material	Purpose in this exercise
Product name, logo and colours	Replace the sample’s branding and interface palette.
References for three interface states	Show what changes after search and what opening an article reveals.
One benefit statement and accurate copy	Decide what each shot explains without inventing features.
Narration recording or sound requirements	Choose your recording, generated narration, or captions and sound effects only.

Send Claude Code:

Use lemo-opuscar to make a 30-second feature video for my article-saving app.
Audience: people who save many articles but struggle to find them later.
Explain one benefit: search and filter the collection to find the article they need.
Sequence: collection → enter a query → filter results → open the target article.
Available materials: [product description, three interface states, logo and colour references].
Chinese, no voiceover. Use captions, quiet music and interface sound effects. 16:9.
Recommend two or three suitable styles and explain how each would present this sequence.
Let me choose a style, then show a storyboard and preview frames in that style.
Wait for approval before making the full film.

If you have narration, identify the recording and provide its matching transcript. Product names, figures and capabilities must come from your information, rather than the agent filling gaps.

Compare styles and approve the storyboard

For this exercise, consider Living Screencast, Whiteboard Explainer or Isometric Infographic. The first demonstrates interface operations; whiteboard explains principles; isometric graphics illustrate processes. Choose according to what viewers need to understand.

If you choose Living Screencast, continue:

Choose Living Screencast.
Redraw my interface from the supplied references. Keep labels, copy and operation results accurate.
Do not reuse the sample's Claude interface or Clawd character.
Use an original blue pixel helper, a cursor and close-ups to guide attention.
Animate simulated typing and clicking; do not require viewers to interact.
Write an original treatment before reading demo code for techniques. Save it as TREATMENT.md.
Show the full storyboard and preview frames before search, after filtering and after opening details.
Do not render the full film until I approve.

TREATMENT.md records the film’s story, shots, sound and pacing. Upstream requires an original treatment before learning techniques from demos. Changing a sample’s title does not create a new story. This request explicitly adds storyboard and preview approvals; the skill does not stop for approval at every stage by default.

Follow the user’s actions through the storyboard. Do results change after the query? Does the next shot open the article just selected? Can viewers read its title? If a shot only introduces or flips cards without explaining a benefit, revise the storyboard first.

Preview one key sequence, then complete the film

After approving the style and storyboard, ask for the search sequence first. Check whether the redrawn interface and animation are accurate. Installing the skill does not supply your product’s interface; your screenshots and descriptions are its references.

Preview only the sequence from entering a query to displaying filtered results.
Keep my button labels, article titles and brand colours.
Show only matching results from my references. Do not invent articles or counts.
Allow time to read the query and see the results change. Sync effects with the simulated actions.
Complete the remaining film only after I approve this sequence.

Still frames reveal text, composition and state errors; playback reveals motion, pacing and sound problems. Default final output is 1920×1080 at 24fps. The creator describes checks including narration transcription, loudness and black-frame checks, plus contact sheets. Those aid review, but you still need to confirm the product is represented accurately.

Keep <project-name>.mp4, poster.jpg, TREATMENT.md, source, build.sh and CREDITS; include .srt when subtitles are needed. CREDITS should document the actual fonts, instruments, music and other third-party materials used.

Replace materials and revise one part

Adapting the film to your product involves more than a logo swap. Update the interface, copy and operation results together. Narration changes also require checking subtitles and shot durations.

Change	Check alongside it
Logo, colours and fonts	Background contrast, title length and font availability.
Interface and button copy	Click positions, action order and accurate search/filter states.
Narration or script	Subtitles, action timing and reading time in each shot.
Landscape to portrait	Recompose the interface, subject and captions rather than simply cropping the sides.

If the target article opens before viewers can identify it, ask:

At [actual timestamp], the results disappear before I can read the target article.
Hold the results longer before the simulated click opens details.
Keep the shot order, brand colours and approved opening. Keep the film at 30 seconds.
Shorten a transition to compensate, adjust the sound cues and check later captions.
Show the revised two shots before exporting the whole film and updating TREATMENT.md.

This identifies the problem, desired change and parts to preserve, making the next version easier to assess than a general request to improve pacing.

Use your own subject or product

Fill in the template with your information:

Use lemo-opuscar to make a short film.
Subject and audience: [what it explains and who it is for]
Viewer's question or problem: [one concrete point]
Sequence: [initial state → key change → final state]
Style: [name one, or recommend two or three with reasons]
Available materials: [paths to recordings, copy, screenshots, logo, fonts and music]
Sound: [narration language and voice, or captions and effects only]
Output: [duration, aspect ratio and subtitle language]
Must remain accurate: [features, figures, names and sources]
Approve the storyboard and key frames, then preview one key sequence before completing the film.
Deliver the video, editable project, build.sh and CREDITS.

For an explainer, provide the concept and evidence so a whiteboard film can build the explanation gradually. For a brand story, supply real experiences and consider paper-pop-up scenes. Decide what change viewers need to understand, then choose a style without reusing the sample’s characters or plot.

Explore the Gallery, style index, director’s guide and technical guide.

Check the licence for what you use

The current repository LICENSE and README declare MIT, with third-party assets retaining their own licences. The earlier article separately states MIT for code and CC BY 4.0 for documents, styles and films. These statements differ. Before using or redistributing a particular film or document, check the version and its applicable licence, retaining required attribution. The code licence alone does not grant unrestricted rights to every asset. Check permissions for your product screenshots, branding and reference videos too.