GTKottman

Mortiflix OSS — Design skill for Claude Code

Design community

A motion design studio on your own machine: Claude makes the video step by step, you approve every stage.

How to install Mortiflix OSS

This entry records only its repository, not the path inside it, so there is no exact command to give. Open GTKottman/mortiflix-oss and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Mortiflix OSS does

A motion design studio on your own machine: Claude makes the video step by step, you approve every stage. Bring your own Claude Code or API key.

Alternatives in Design

  • Studio — Launch the local design Studio — a live token editor over the latest extraction 3.6k ★
  • Companion — 2,200+ Web & mobile UI for Claude Code & Codex 2.2k ★
  • 3D Studio Pricing — Create a full-screen hero section with a looping video background and a pricing card overlay 152 ★

README

Mortiflix

Mortiflix

A motion design studio on your own machine.
Claude makes the video step by step. You approve every stage.

How to use Mortiflix: tap to watch the video
▶ Watch: How to use Mortiflix (3:07). This video was made with Mortiflix.


Most "AI video" tools are one prompt and a slot machine. Mortiflix works like a real motion design studio: a brief, a script, style frames, a transition board, an animatic, a final, and **you review each stage** before the next one starts. You pin a note on the exact spot of a frame or the exact moment of a video. The next version answers every note, one by one, and shows you what changed.

It's built for **one person**: you write the briefs, you review every stage, and the studio runs on your machine. The work is done by Claude through **your own Claude Code login or your own Anthropic API key**. Mortiflix is the harness around it: the pipelines, the gates, the review room, and the memory that carries a project across sessions and days.

 brief ──▶ script ──▶ style frames ──▶ animatic ──▶ build ──▶ final ──▶ delivered
   ▲          ▲            ▲              ▲                     ▲
   └── you ───┴──── you ───┴───── you ────┴──────── you ────────┘
       approve, pin notes, answer questions (the session stops at every gate)

Why it's built this way

  • Sessions end at gates. A Claude session works until it has something for you to review, submits it, writes a handoff and stops. When you respond, a fresh session picks up from the journal. Waiting on you costs nothing, for hours or for days.
  • The rules live in code, not in the prompt. Only you can approve a step you review. A submission is r