Lemo-Opuscar

A toolbox of film styles made in code: 66 ready to use, and your own. Pick a style or make one from scratch, bring your story, and let your coding agent direct. 66 种影片风格，每种都配一支完全用代码做出来的短片 · 🇨🇳 中文用户请看 简体中文说明

⚠️ Built for Claude. The styles are tuned for Claude Opus 5.5; other models may not reproduce them well, so use them with care.

🆕 2026-10-29 · 7 new styles: a Memphis diorama by @EianLu, a metro map, a chalkboard and more. See them ↓ 🆕 2026-10-22 · Edit & Documentary: 8 styles cut from real footage, documents and data. See them ↓ 🆕 2026-10-22 · Make a style your own: change a style or start blank, and keep it. See how ↓ 🆕 2026-10-16 · Evidence Films: 8 styles that film real material, every number sourced. See them ↓

Official repo: github.com/lemomo-ai/lemo-opuscar · by Lemomo (@lemomo_ai)

🎬 Feature presentation: OPUSCAR 98

Every frame, every note and every cut was written in code by Claude Opus 5.5. ▶ Watch · All 98 styles · Download 1080p

👋 About me

I'm Lemomo (@lemomo-ai). More about me on my profile.

Not an awesome list. Every film here was made by me, with Claude Opus 5.5. The styles are tuned for Opus 5.5; other models may not reproduce them.

Every film was directed, drawn, scored and mixed by an AI agent writing code:

• 🎨 Picture: canvas and WebGL pages, rendered frame by frame
• 🎵 Music: original scores from free sample libraries
• 🎙️ Voice: text-to-speech narration

No video generation, no stock footage.

How to use

Two ways in; the skill is the easiest.

Option 1: install the skill (recommended)

In your terminal:

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

Then use it from any folder.

• On first use it downloads the guides, tools and style prompts to ~/lemo-opuscar, shared by all your films.
• Each film's project, from source to finished video, goes in the folder you started from.
• For other agents, copy plugin/skills/lemo-opuscar/ into their skills folder.

Option 2: clone the repo

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

Films go into films/<name>/ inside the repo.

Then just say what you want

Make a 45-second film in the watercolor style about the coffee farm my family runs. Warm female narrator.

Make a 40-second LiDAR Survey film about the old quarry in the hills behind our town, from public laser-scan data.

Name the style in English or Chinese; the style index lists them all.

Not sure yet? With the skill installed, type /lemo-opuscar:lemo-opuscar and nothing else. It asks which language to use, then what you'd like to do: a film in a library style, make a style your own, or a film in a style you've saved.

It asks you once, up front:

• anything it can't decide about your topic;
• whether you have your own voice, music or other material;
• whether you want to see a storyboard first. Say yes and it stops once to show you the key shots in the real style; otherwise it goes straight to the finished film.

The agent reads three guides and works like a small studio:

Make a style your own

Everyone wants something different: their own brand colours, logo, characters, the tone of their channel. Now you can change a library style into one that's only yours, or make one from a blank page that the library doesn't have. It's the same process I use to add a new style to the library.

Two ways in. Pick one after starting the skill, or say it in one line:

I want to change the Ukiyo-e style into my own version.

Start from a blank page: a chalk-on-blackboard style, warm and slow.

• Change a library style: it lists every style with the gallery link, and you type the one to change.
• Start from a blank page: describe the look in your own words, or share a picture or a film you like. Claude picks the closest library style as the technique base, tells you why, and you agree or pick another.

Then five steps:

1. Plan it one question at a time. Each question has a few options, the recommended one first, with the reason. Roughly:

   • what it's for: what kind of films, which platform (vertical feeds want 1080×1920 or 1080×1440), any brand colours, logo, fonts or recurring characters;
   • what to change: for a library style it first sorts the style into three groups, safe to change (palette, type, pace, sound, signature moves), changes its character (materials and rendering, the colour logic, camera grammar) and can't change (the style's essence: change that and it's a different style);
   • which way to take each part, and last, a name.

   Vague is fine: say "more premium" or "livelier" and it turns that into concrete changes to pick from. Too slow? Choose "free conversation", the last option on every question, and just talk it through; say "you decide" at any point and it fills in the rest with its recommendations. At most five changes a round when changing a library style; everything is drawn in code, no image generation.

2. Review the summary. Each part before, after, and what it costs. Nothing is written until you agree.

3. See one style frame first, drawn with the real code. When you changed a library style, the same frame is rendered in the original too, side by side: original left, yours right. Say what's off; if it still isn't right after two rounds, it says so and suggests a closer base.

4. A 15–30 second demo film. Every change is on screen, with music and sound effects. It checks the film and fixes it once before handing it over.

5. Keep it when you're happy. It asks: keep it as my style, another round, or not now. Until you say yes, everything stays in that project's folder.

Once kept, the style lives in ~/lemo-my-styles/<name>/, shaped like a library style: the style prompt, what changed, the demo film and its source, so later films can reuse the techniques. Then name it like any other style: "Make a 30-second film in my Night Ukiyo-e style about…". When you pick a style, your own are listed first.

Library updates and reinstalling never touch them. When the base style is u