# AI use cases for Onetake (feitangyuan/onetake)

Repo: [feitangyuan/onetake](https://github.com/feitangyuan/onetake) | Use cases: 4 | Page: https://dedupedai.com/use-cases/feitangyuan-onetake/

onetake is a Claude Agent Skill that makes continuous-take motion films (product launch films, teasers and feature demos) in which each beat visibly grows out of the one before.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Make a 15-second product launch film with one camera: https://dedupedai.com/use-cases/feitangyuan-onetake/launch-film-from-app-description/
- Rebuild a feature demo from screenshots, no recording: https://dedupedai.com/use-cases/feitangyuan-onetake/feature-demo-from-screenshots/
- Diagnose a motion video that reads like a slideshow: https://dedupedai.com/use-cases/feitangyuan-onetake/fix-slideshow-motion-video/
- Plan a motion film beat by beat before rendering: https://dedupedai.com/use-cases/feitangyuan-onetake/plan-motion-film-beat-by-beat/

## How to make a 15-second product launch film with one camera with Onetake

Repo: [feitangyuan/onetake](https://github.com/feitangyuan/onetake) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README

Have a coding agent turn a short app description into a launch film where every beat carries into the next.

**Who it is for:** A founder or indie developer with an app and no motion designer, who needs a launch video this week.

**The problem:** Template and AI-made motion videos usually fade between unrelated title cards, so the film reads as a slideshow.

**The outcome:** A 15-second launch film, rendered as a draft, with one continuous camera and boundaries where something on screen becomes the next beat.

### Steps

1. Install the skill for Claude Code: `git clone https://github.com/feitangyuan/onetake.git ~/.claude/skills/onetake`
2. Install the Python packages and browser: `pip install playwright numpy scipy Pillow matplotlib` then `playwright install chromium`, and make sure ffmpeg and node are on your PATH. (inferred, check the README)
3. Ask the agent: "Make a 15 s launch video for my app" and describe the app in two or three sentences.
4. Read the three concepts it offers and the beat sheet. Check that each boundary names the thing that survives it.
5. Wait for the render and the verify step, then watch the draft before asking for changes.

### Prompt to paste into your agent

```text
Using the onetake skill in the feitangyuan/onetake repo, make a 15 second launch film for <app name and one-line description>. Output a 1080p30 draft video file and its beat sheet. Verify that the continuity check passes and that every boundary in the beat sheet names what carries across it before you report done.
```

### Caveat

The films are licensed for noncommercial use only, so a film for a paid product launch needs the separate commercial license from Onetake Pro.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/feitangyuan-onetake/launch-film-from-app-description/

## How to rebuild a feature demo from screenshots, no recording with Onetake

Repo: [feitangyuan/onetake](https://github.com/feitangyuan/onetake) | Difficulty: Advanced | Time: 120 minutes | Basis: From the README

Turn a set of app screenshots into a feature demo where the interface is rebuilt in HTML and the camera flies into it.

**Who it is for:** A product manager or developer who needs a feature walkthrough but cannot or does not want to record a live screen.

**The problem:** Screen recordings look blurry when the camera zooms in, and a demo that cuts between static screenshots reads as a slideshow.

**The outcome:** A feature demo in which the product interface is rebuilt from the screenshots and sits on the camera plane, so zooming stays sharp.

### Steps

1. Install the skill for Claude Code: `git clone https://github.com/feitangyuan/onetake.git ~/.claude/skills/onetake`
2. Install the Python packages and browser as in the launch film setup, plus ffmpeg and node. (inferred, check the README)
3. Put the screenshots of the feature in a folder you can point the agent to.
4. Ask the agent: "A feature demo rebuilt from these screenshots, no screen recording" and state the feature to show.
5. Check that the rebuilt interface matches your screenshots and that the feature steps follow in order.

### Prompt to paste into your agent

```text
Using the onetake skill in the feitangyuan/onetake repo, build a feature demo of <feature name> from the screenshots in <screenshot folder>, with no screen recording. Output a video file of the demo. Verify that the rebuilt interface matches the screenshots and that the camera moves between the steps without cuts.
```

### Caveat

The README does not say how many screenshots are needed or how complex the interface can be, so test with one feature before you plan a full demo.

Risk, reverse engineering: Only rebuild interfaces you own or have permission to show, because the skill recreates the product UI from your screenshots.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/feitangyuan-onetake/feature-demo-from-screenshots/

## How to diagnose a motion video that reads like a slideshow with Onetake

Repo: [feitangyuan/onetake](https://github.com/feitangyuan/onetake) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README

Run the continuity check on an existing motion video to find the cuts where nothing carries over, then fix them.

**Who it is for:** A marketer or designer whose AI-made or template motion video looks choppy and fades between unrelated scenes.

**The problem:** The video looks fine shot by shot but feels like separate slides, and the cause is hard to see by eye.

**The outcome:** A list of boundaries that fail the carry check, with a plan to make each one pass by letting something on screen survive into the next beat.

### Steps

1. Install the skill for Claude Code: `git clone https://github.com/feitangyuan/onetake.git ~/.claude/skills/onetake`
2. Install the Python packages and ffmpeg as listed in the requirements. (inferred, check the README)
3. Ask the agent: "my motion video feels like a slideshow, fix it" and give it the video or its source file.
4. Read the continuity result and the list of boundaries where nothing carried across.
5. Approve the revised beat sheet and check the new carry score before you ship the video.

### Prompt to paste into your agent

```text
Using the onetake skill in the feitangyuan/onetake repo, run the continuity check on <video file or source> and list every boundary where no element carries into the next beat. Output the failing boundaries with a carry score for each. Verify that the score is higher after you apply the proposed fixes.
```

### Caveat

The README describes the check on films made with Onetake, so results on video made by other tools depend on whether the skill can read its source, which the README does not state.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/feitangyuan-onetake/fix-slideshow-motion-video/

## How to plan a motion film beat by beat before rendering with Onetake

Repo: [feitangyuan/onetake](https://github.com/feitangyuan/onetake) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README

Use the rhythm and carry method to write a beat sheet where shot lengths vary and every boundary has a carried element.

**Who it is for:** A motion designer or content lead who wants to plan a teaser or feature film on paper before anyone renders it.

**The problem:** Plans often list scenes in order with no thought for what links them, and every shot ends up the same length.

**The outcome:** A beat sheet with varied shot lengths and a named survivor at every boundary, ready to hand to the render step.

### Steps

1. Install the skill for Claude Code: `git clone https://github.com/feitangyuan/onetake.git ~/.claude/skills/onetake`
2. Open the references folder in the repo to read the rhythm and carry notes.
3. Ask the agent: "Three concepts, pick one" and describe the product and the feeling you want.
4. Review the beat sheet. Confirm that shot lengths differ by at least four times and that each boundary names what survives it.

### Prompt to paste into your agent

```text
Using the onetake skill in the feitangyuan/onetake repo, write a beat sheet for a <length> teaser for <product>. Output one sentence per concept, then the chosen beat sheet with shot lengths and a named survivor at every boundary. Verify that shot lengths vary by at least four times and that no boundary is left without a carried element.
```

### Caveat

The beat sheet is a planning output only, and the README's rules still need the render and verify steps before any film exists.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/feitangyuan-onetake/plan-motion-film-beat-by-beat/