I Designed an 8-Step Video Editing System on My Phone -- Here's the Workflow

TL;DR: I designed a complete 8-step video editing automation -- AI scene analysis, narration, TTS, subtitles, compositing, 22 style presets -- entirely from my phone during a single commute-to-couch session. The system runs in production daily. This article breaks down the mobile workflow, the design decisions, and why AI coding from your phone is not a gimmick.

This article is the design story behind the AWP Video Editing Skill — how I architected an 8-step pipeline entirely from my phone. For the complete Skill documentation and all 22 style presets, see The AWP Video Editing Skill Guide. For the Cherry Studio desktop GUI setup, see Cherry Studio + Claude Code.

What Does an 8-Step Video Editing Pipeline Look Like?

The video editing automation I built handles the full journey from raw footage to finished video. No timeline dragging. No manual cuts. One command triggers all eight steps of the video editing pipeline.

Here are the eight steps at a glance:

1. Scene analysis -- AI detects shot boundaries and logs timestamps.
2. Jump cut removal -- Strips dead air and filler based on that analysis.
3. Narration generation -- Writes a voiceover script matched to the trimmed duration.
4. Text-to-speech (TTS) -- Renders the script in a voice bound to the chosen style preset.
5. Subtitle generation -- Produces word-synced subtitle tracks from the audio.
6. Subtitle burning -- Bakes subtitles onto the frames, no toggle needed.
7. Final compositing -- Merges video, audio, and subtitles with background-music ducking.
8. Checkpoint logging -- Saves state so a crash resumes instead of restarting.

I am keeping the step descriptions short on purpose. This article is about the design -- how I made these calls from a phone. For the full step-by-step Skill documentation, the FFmpeg command reference, and all 22 style presets, see The AWP Video Editing Skill Guide, the official write-up of the open-source Skill this pipeline became.

The one design decision worth pulling out here -- because I made it on my phone -- is the three-layer prompt architecture.

Creative layer controls style -- voice personality, pacing, tone. This is where the 22 presets live (the full catalog is documented in the Skill guide); switching between them changes the entire feel of the output without touching code.

Parameter layer controls technical decisions. Scene detection sensitivity, subtitle font size, audio ducking ratio, export resolution. These are the knobs an editor would normally twist in a GUI.

Configuration layer controls environment. File paths, API keys, output directories, temp folder locations. Boring but essential.

The layers are independent. Change the creative preset from "explainer" to "showcase" and nothing in the parameter or configuration layers needs to move. This separation was not my idea -- Claude Code proposed it during the initial architecture pass, and I immediately saw why it mattered. When layers bleed into each other, every small change risks breaking something unrelated.

I was wrong about one thing early on: I assumed narration should be generated once, before any editing. Bad call. After jump cuts, segment durations shift -- a 30-second segment might become 18 seconds after removing dead air. The narration word count needs to match the post-cut duration, not the original. I caught this while reviewing the architecture doc on my phone and added a narration-recalibration step in about 15 seconds of typing.

How Can You Code From Your Phone?

This is the question I get most often, so let me be direct: you are not writing code on your phone. You are giving natural language instructions and reviewing structured output. Your phone is a command bridge, not an IDE.

The workflow has two channels:

Input channel -- You tell Claude Code what to do. "Refactor the video scripts into a standard Skill with an 8-step pipeline." "Add narration recalibration after the jump cut step." "Design 22 creative style presets." These are plain English sentences typed with your thumbs.

Output channel -- You read what Claude Code produced. Architecture documents, configuration files, test logs, error reports. All rendered as readable pages rather than raw terminal output.

The modern option: Claude Code Remote Control

Since February 2026, Anthropic offers a native solution. Run claude remote-control in your terminal, scan the QR code with the Claude mobile app, and your phone becomes a live window into your local Claude Code session. Your code stays on your machine. The phone is just a viewport.

This is what I use now. But when I built the video editing system, Remote Control did not exist yet. I used a remote desktop app to mirror my Mac screen on my phone, plus a local Markdown preview server to render Claude Code's document output as clean web pages. Two apps, constant switching between them -- it worked, but Remote Control is cleaner.

The underlying principle has not changed: your phone handles "instruct" and "review" naturally, because both are text-based tasks. The tooling just got easier.

What "instruct and review" looks like in practice

Here is a real sequence from that day:

• On the subway: I opened a remote session and typed: "Refactor the video editing scripts into a Skill with clear input/output contracts for each step." Claude Code ran for about four minutes. I put my phone in my pocket and watched the stations pass.
• Still on the subway: Pulled out my phone, reviewed the architecture document. Eight steps, clean I/O boundaries. Spotted the narration timing issue. Typed: "Add narration recalibration based on post-cut segment duration." Fifteen seconds. Done.
• At a coffee shop: Reviewed all eight workflow documents. Noticed that TTS voice selection was a separate parameter from style presets. Typed: "Bind TTS voice to the creative preset -- professional explainer gets the steady male voice, energetic showcase gets the upbeat female voice. Users should not pick voice and style separately." This took maybe 20 seconds.
• Waiting for someone: Typed: "Generate 22 creative style presets." Went back to my coffee. Five minutes later, scrolled through the presets. Two were nearly identical. Typed: "Merge presets 14 and 17 -- differentiate by adjusting speech rate and background music volume." Ten seconds.
• On the couch at home: Typed: "Run the full pipeline test with preset 'professional explainer' on the sample footage." First run crashed -- a scene detection parameter had a decimal point error. Claude Code read its own error log, fixed the value, and reran. The output video played correctly. Narration pacing was smooth, subtitles were positioned correctly, transitions were clean.

Total hands-on time across the whole day: roughly 90 minutes. But those 90 minutes were spread across six hours of otherwise dead time -- commuting, waiting, relaxing.

Why Does "Speak + Review" Replace "Write + Debug"?

Remote desktop is old technology. Phones are old technology. But designing an 8-step automation pipeline from a phone was genuinely impossible before AI coding agents.

Traditional programming demands three things that phones cannot provide:

1. A large screen to see enough code context at once
2. A physical keyboard for rapid, precise text input
3. Long focus blocks to hold complex logic in your head

AI coding flips all three requirements. You do not need to see code -- you review documents and test results. You do not need a keyboard -- natural language input works fine with thumbs. You do not need long focus blocks -- you can give a 15-second instruction, do something else for five minutes, and come back to review.

The shift is from "write code" to "instruct and review." Phones are excellent at both.

I realized this on the subway, and it was not a gradual insight. It hit me mid-station: the reason I could work from my phone was not that my phone had gotten more capable. It was that programming itself had changed shape. The bottleneck moved from "can I type fast enough" to "can I describe what I want clearly enough." Thumbs handle the second bottleneck just fine.

This has a practical implication worth spelling out: fragmented time becomes productive time. Not in the "reply to emails on the bus" sense -- in the "design a production automation system across six micro-sessions" sense. The pipeline I built that day is not a prototype. It has processed hundreds of videos since. The work was real and the phone was the only interface I used.

How to Set Up Your Own Mobile AI Coding Environment

The simplest path in 2026 takes about five minutes.

Option A: Claude Code Remote Control (recommended)

1. Install Claude Code on your Mac or PC (npm install -g @anthropic-ai/claude-code)
2. Run claude remote-control in your terminal -- or enable it permanently with /config → "Enable Remote Control for all sessions"
3. Open the Claude mobile app (iOS or Android) or visit claude.ai/code
4. Scan the QR code displayed in your terminal
5. Your phone now shows your live Claude Code session. Type instructions, review output, approve actions.

Everything runs locally on your machine. The phone is a window, not a host.

Option B: Remote desktop + Markdown preview (DIY)

If you want a setup that works with any terminal AI tool -- not just Claude Code:

1. Install any remote desktop app (Parsec, Chrome Remote Desktop, or similar). Connect your phone to your computer.
2. Deploy a local Markdown preview server on your computer. A simple Python script with mistune renders .md files as styled web pages. Configure it to serve your working directory on a local port (e.g., 0.0.0.0:8642).
3. On your phone: use the remote desktop app to type commands, and the browser to read Markdown output at your computer's local IP address.

Option B is what I used when I built the video editing system. It still works and has one advantage: you can preview any Markdown file from any tool, not just Claude Code session output. If your CLAUDE.md configuration generates complex project docs, this preview setup makes them readable on mobile.

What Else Can You Build From Your Phone?

The video editing pipeline was the first thing I built this way. It was not the last.

Long-form articles. I trigger a writing workflow, wait 10-15 minutes, and review the draft in my browser. Structural edits take a few sentences of instruction. I have written and published articles where 80% of the editorial work happened on my phone.

Agent monitoring. I run a fleet of AI agents that produce daily outputs -- research summaries, content drafts, analytics reports. All Markdown. Reviewing them from my phone during downtime replaced a dedicated morning desk session.

Emergency debugging. Once, during dinner, an agent pipeline threw an error. I opened Remote Control, described the error to Claude Code, and it diagnosed and fixed the issue in under five minutes. The alternative was driving home, opening my laptop, and losing 45 minutes.

The pattern is always the same: instruct → wait → review. Whether you are building a video editing automation or debugging a production issue, the phone is not where the work happens. It is where you direct the work and verify the results.

Three Things Worth Remembering

1. Mobile AI coding is real, not a gimmick. The 8-step video editing automation I designed from my phone runs in production daily. Claude Code's Skills framework makes these automations reusable with a single command -- if you want to build one yourself, the Claude Code Skill Development Guide walks through the structure.

2. The paradigm shift matters more than the tooling. Whether you use Remote Control, a remote desktop app, or something else entirely -- the point is that programming moved from "write code" to "instruct and review." Your specific prompt patterns matter more than your screen size.

3. Fragmented time adds up. Ninety minutes spread across a commute, a coffee shop, and a couch produced a production automation system. The constraint was never time -- it was whether you had the right workflow to use the time you had.

FAQ

Can you actually code from your phone with Claude Code?

Yes, but you are not running Claude Code on your phone. Claude Code runs on your Mac or PC. Your phone acts as a remote command interface -- you give instructions and review output. Anthropic's Remote Control feature (released February 2026) makes this native: run claude remote-control in your terminal, scan a QR code, and your phone becomes a window into your local session. Before Remote Control existed, developers used remote desktop apps to achieve the same workflow.

What tools do you need to build an AI video editing pipeline?

At minimum: Claude Code (the orchestration layer), FFmpeg (the open-source video processing toolkit -- handles trimming, concatenation, subtitle burning), and a TTS service (like ElevenLabs or Fish Audio) for AI narration. Optional additions include PySceneDetect (a Python library that detects shot boundaries in video files) for automatic scene segmentation. The three-layer prompt architecture (creative, parameter, configuration) keeps the system maintainable as it grows. For an overview of how Skills work in Claude Code, see our Skills guide.

How long does it take to build a video editing automation with Claude Code?

A basic pipeline (trim, concatenate, add subtitles) can be functional in 2-3 hours. The 8-step system described here -- with AI scene analysis, narration generation, TTS, subtitle burning, style presets, and checkpoint recovery -- took roughly one working day of elapsed time, but only about 90 minutes of actual hands-on input. The rest was Claude Code executing while I did other things.

Is mobile coding productive or just a gimmick?

It depends on what you mean by coding. Typing syntax into a phone editor? Terrible. But with AI agents like Claude Code, coding has shifted to "instruct and review" -- give a natural language command, wait for the agent to execute, then review the output. Phones handle both steps well. The key is having the right MCP connections (Model Context Protocol -- the way Claude Code talks to external tools and services) and project configuration set up on your machine before you go mobile.

Related Reading

• The AWP Video Editing Skill Guide — The complete Skill documentation, FFmpeg pipeline, and all 22 style presets
• Cherry Studio + Claude Code — The same pipeline set up through the Cherry Studio desktop GUI
• Claude Code Skill Development Guide — How to package a workflow into a reusable Skill
• Claude Code Complete Guide 2026 — Comprehensive Claude Code reference covering Skills, MCP, and mobile workflows
• 5 Claude Code Skills I Actually Use — How to build reusable automation Skills
• Claude Code Prompt Patterns — Effective prompt patterns for AI coding agents
• Claude Code MCP for Normal People — Connect Claude Code to external tools and services

Further Reading

• Claude Code Documentation — Official Claude Code setup, Remote Control, and Skills reference
• FFmpeg Official Documentation — FFmpeg command reference for video processing pipelines

— Leo