Interfaces + Open Design / Foundation

I Drew Her, Then Made Her Dance on My Table (AI TUTORIAL)

A creator breaks down how he made a hyper-real AI video entirely with free, local, open-source tools, combining motion transfer from his own filmed dancing, a 'reality fusion' clip swap, and first-and-last-frame generation across ComfyUI, WanGP, and LTX.

Prompt Mastery20 minTranscript found

Quick learning frame

Read this before watching.

Agent ops treats agents like services: observable state, queues, permissions, logs, recovery, and post-run review.

New playlist item from Prompt Mastery; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Skill you build: The ability to plan and stitch together multiple AI video techniques (motion transfer, character replacement, and first-last-frame chaining) into one seamless, believable clip using local and cloud ComfyUI workflows.

Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.

Concept diagram

Where this video fits.

01Project state
02Session
03Queue/Kanban
04Tools
05Logs
06Recovery
07Post-run review

Deep lesson

Turn this video into working knowledge.

3,049 cleaned transcript words reviewed across 805 timed caption segments.

Thesis

I Drew Her, Then Made Her Dance on My Table (AI TUTORIAL) teaches a practical hermes operations move: A creator breaks down how he made a hyper-real AI video entirely with free, local, open-source tools, combining motion transfer from his own filmed dancing, a 'reality fusion' clip swap, and first-and-last-frame generation across ComfyUI, WanGP, and LTX.

The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.

1:17

Real motion, real effort

“Want to learn? Let me show you how it's done for free. Guys, welcome for another video. Now, let's do the breakdown of this video. And everything you've seen in the introduction video was made with local AI...”

The centerpiece is motion transfer: the creator filmed himself dancing (practicing a full day) and drove an AI avatar with that footage so the movement reads as natural and human, arguing that visible creator effort is what makes AI content connect when generated scenes otherwise feel boring. Film a short clip of yourself performing a simple movement to use as the driving video, so your AI avatar inherits genuinely human motion rather than generic generated animation.

11:11

Motion transfer workflow

“just download it from here. Export workflows and then and that's right there. All right. And then if you do deploy in the locals, there's a few thing you need to pay attention. So now I'm in my...”

In the cloud ComfyUI motion-transfer workflow you upload just a reference image plus a driving video and hit run; it took about 16 minutes for a roughly 10-second clip (about 7 minutes per 5 seconds), and enabling sage attention (disabled here) would speed generation by an estimated 20-30%. Load the motion-transfer workflow, supply one reference image and one driving video, and time a short render, then note whether sage attention is enabled on your setup.

14:49

First-last-frame chaining

“all different tools with a and to solving different kind of problems. So with my knowledge I can help you guys too. So, but I just strongly urge you guys do not limit yourself. Just use one two...”

Using Wan 2.2 and LTX 2.3, he sets a screenshot as the start frame and the finished-drawing frame as the end frame, then reuses each end frame as the next start frame to build a timelapse; he stresses using whichever tool fits (WanGP for speed via built-in sage attention, ComfyUI for missing functions) rather than being loyal to one, and to set the seed to -1 for random results. Generate one 5-second first-and-last-frame clip, then feed its final frame back in as the start frame of the next clip to practice chaining a continuous sequence.

01

Project state

Start with this video's job: A creator breaks down how he made a hyper-real AI video entirely with free, local, open-source tools, combining motion transfer from his own filmed dancing, a 'reality fusion' clip swap, and first-and-last-frame generation across ComfyUI, WanGP, and LTX. Treat "Project state" as the outcome you are trying to make visible, not a topic label. Anchor it to 1:17, where the video says: “Want to learn? Let me show you how it's done for free. Guys, welcome for another video. Now, let's do the breakdown of this video. And everything you've seen in the introduction video was made with local AI...”

02

Session

Use "Session" to locate the part of the hermes operations mechanism the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 11:11, where the video says: “just download it from here. Export workflows and then and that's right there. All right. And then if you do deploy in the locals, there's a few thing you need to pay attention. So now I'm in my...”

03

Queue/Kanban

Turn "Queue/Kanban" into the reusable artifact for this lesson: A Hermes-style agent-ops runbook with health checks, state transitions, logs, recovery steps, and review criteria. This is where watching becomes something you can inspect and reuse.

04

Tools

Use "Tools" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.

05

Logs

Use "Logs" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.

06

Recovery

Use "Recovery" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.

07

Post-run review

Connect "Post-run review" to I Drew Her, Then Made Her Dance on My Table (AI TUTORIAL) by naming the claim, the evidence, and the artifact it should produce.

Example

Source-backed artifact packet

Convert the video into a scoped artifact request that includes the transcript claim, mechanism, acceptance criteria, and proof. The output should be a hermes-style agent-ops runbook with health checks, state transitions, logs, recovery steps, and review criteria..

Example

Hermes operations proof brief

Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the hermes operations pattern.

Example

Teach-back module

Transform the lesson into a definition, a Project state -> Session -> Queue/Kanban -> Tools -> Logs -> Recovery -> Post-run review diagram, one misconception, one practice exercise, and a check-for-understanding question.

Do not learn it wrong
  • Treating the title as the lesson without checking what the transcript actually says.
  • treating UI features as reliability
  • missing logs
  • no stop/recover path
  • Letting the lesson drift into feature cheerleading.
  • Letting the lesson drift into ops advice without logs/state.
  • Letting the lesson drift into assuming reliability from a demo alone.

Transcript-derived moments

Use timestamps to study the actual video.

Quality check

Do not count this as learned until these are true.

01

State the transcript-backed claim in your own words: A creator breaks down how he made a hyper-real AI video entirely with free, local, open-source tools, combining motion transfer from his own filmed dancing, a 'reality fusion' clip swap, and first-and-last-frame generation across ComfyUI, WanGP, and LTX.

02

Explain the practical stakes without hype: New playlist item from Prompt Mastery; queued for transcript-backed review, topic mapping, and a practical learning artifact.

03

Map the idea onto the Project state -> Session -> Queue/Kanban -> Tools -> Logs -> Recovery -> Post-run review sequence and name the weakest link.

04

Produce the artifact and include the evidence that proves it: A Hermes-style agent-ops runbook with health checks, state transitions, logs, recovery steps, and review criteria.

Put it into practice

Give this grounded prompt to Codex or Claude after watching.

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: I Drew Her, Then Made Her Dance on My Table (AI TUTORIAL)
- URL: https://www.youtube.com/watch?v=_HXfXERZRTM
- Topic: Interfaces + Open Design
- My current learning frame: Pick a simple scene and produce one short clip that chains two techniques from the video, for example a first-and-last-frame timelapse whose ending frame becomes the start of a motion-transfer clip driven by footage you filmed yourself.
- Why this matters: New playlist item from Prompt Mastery; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 1:17 / Evidence 1: "Want to learn? Let me show you how it's done for free. Guys, welcome for another video. Now, let's do the breakdown of this video. And everything you've seen in the introduction video was made with local AI..."
- 4:06 / Evidence 2: "end point. So this is the key, right? So we need to find a starting point of the clip and we find a end point of a clip which is uh right about like here right so this..."
- 9:20 / Evidence 3: "come to this page and click on launch on the cloud. All right guys, so once you launch the workflow, this workflow I made it extremely easy. So this is a scale to long video motion transfer. The..."
- 11:11 / Evidence 4: "just download it from here. Export workflows and then and that's right there. All right. And then if you do deploy in the locals, there's a few thing you need to pay attention. So now I'm in my..."
- 12:57 / Evidence 5: "now let's come down to the last part of the technical breakdown which is going to be first and last frame. I use a combination of 1 2.2 2 and LTX 2.3 for this project. And while we're..."
- 14:49 / Evidence 6: "all different tools with a and to solving different kind of problems. So with my knowledge I can help you guys too. So, but I just strongly urge you guys do not limit yourself. Just use one two..."
- 16:48 / Evidence 7: "part is going to be my second starting frame. So I want a 5 seconds just for me to draw the face. The prompt is exactly the same. All right, if you guys want to have a look."

Video-aware target:
- Prompt lane: Hermes operations
- Mechanism to extract: Identify the operations control that makes long-running agent work visible, recoverable, or safer.
- Artifact to produce: A Hermes-style agent-ops runbook with health checks, state transitions, logs, recovery steps, and review criteria.
- Artifact must include: health check; state model; permission boundary; log source; recovery action

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Identify the operations control that makes long-running agent work visible, recoverable, or safer. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A Hermes-style agent-ops runbook with health checks, state transitions, logs, recovery steps, and review criteria.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Project state -> Session -> Queue/Kanban -> Tools -> Logs -> Recovery -> Post-run review
   - answers to these source questions: What operational failure is prevented? | What state is visible? | What can be recovered or redirected?
   - 3 concrete examples that apply the video idea to real agentic work, such as Hermes Kanban triage; local model endpoint check; agent swarm recovery review
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: treating UI features as reliability; missing logs; no stop/recover path
   - a checklist for the next real workflow, focused on: status, model/backend, tools, logs, recovery
   - one practical exercise with a clear done signal: Write a runbook for restarting one stuck Hermes-style agent session.
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "I Drew Her, Then Made Her Dance on My Table (AI TUTORIAL)", not a generic Interfaces + Open Design essay.
- Ground each ops recommendation in transcript evidence about state, queues, models, tools, security, logs, or recovery.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: feature cheerleading; ops advice without logs/state; assuming reliability from a demo alone.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.

Misconceptions

What to stop believing.

A beautiful page is automatically a good learning tool.

Learning requires sequence, active recall, feedback, and application.

Generated UI should be accepted as-is.

Generated UI needs critique, revision, and browser verification.

Practice studio

Learning only counts when you make something.

01

Transcript evidence map

Separate what the video actually says from what you already believe about the topic.

3 source-backed takeaways with timestamps, confidence, and a transfer note.
02

One useful artifact

Apply the video to a real workflow and produce a hermes-style agent-ops runbook with health checks, state transitions, logs, recovery steps, and review criteria..

A reusable artifact with a done signal and one verification step.
03

Hermes operations teach-back card

Explain the hermes operations mechanism to someone who has not watched the video yet.

A 90-second explanation, one diagram, one example, and one misconception to avoid.

Recall check

Answer first, then reveal — without rewatching.

What is the motion transfer technique, and why did the creator film himself dancing?

What two inputs does the cloud motion-transfer workflow need, and roughly how long does it take?

How does the first-and-last-frame method build a continuous timelapse, and why does the creator use multiple tools?

Source shelf

Use the video as a doorway, then verify with primary sources.

ReadingOpen Design Repogithub.com/open-design-dev/open-designReadingReact Docsreact.dev/