Preston Chin uses Melda OS as the home for each piece of content, then connects his personal editing and review tools around it. This founder workflow shows how a content card can give the next step its context. The current Melda OS workspace handles ideas, sources, scripts, and approvals; Preston’s custom editing, scheduling, and analytics tools are separate.
Key takeaways
- Keep the source, script, and decision together so the next person or tool knows what to work on.
- Separate a repeatable editing style from the changes needed for one video.
- Keep human review before the finished video leaves the workflow.
The documented workflow
In his September 18 walkthrough, Preston describes a card that connects a script, raw footage, and stage status through a Content ID. His examples include an outdoor take (C3330), a livestream clip (C3308), and a tutorial (C3336). Each uses a different reusable editing skill in his connected setup.
A concrete handoff: for C3330, Preston invokes his edit-outdoor-talking-head-resolve skill with the Content ID, using DaVinci Resolve in his personal setup. His instruction adds photos above the opening title. The returned render then enters his review loop; the ID alone does not make an edit approved.
- Start with the card. The Content ID points the editing task to the right script and recording.
- Choose the format. An outdoor take, livestream clip, and tutorial have different editing needs.
- Review the render. Preston watches the video and requests changes before approving it.
- Hand off the approved file. His separate, account-specific skills handle filing, scheduling, and weekly analytics.
Those downstream steps describe Preston’s personal setup. They are not automatic features of the current Melda OS workspace. See the original examples and workflow.
Where Preston reviews
His phone-review walkthrough shows a separate review page for watching versions and preparing feedback. Its approval button saves a decision in the phone’s browser; he copies that decision back to the editing conversation. Playback and instructions are distinct steps.
The lesson for a content team is practical: define where feedback goes and what actually triggers the next action. A video that plays correctly is ready to review. It still needs someone to decide whether the words, captions, and visuals are right.
What Melda OS offers today
Melda OS is a content workspace for experts, coaches, consultants, and agency founders. Send Emmy, its AI content agent, an idea or source link; develop a script, revise it, and keep the source and writing on a card in Pipeline.
- Draft with context. Save audience and voice guidance in your workspace Profile. Ask for a brief and hook options when you need them.
- Review the writing. Approve the script or send it back with a note. Check the facts and add your own experience before recording.
- Take your work with you. Download scripts and export your cards for the rest of your production process.
The workspace does not edit video, post, schedule, or track performance automatically. Use your own production tools, or book a call about a separately scoped paid production service. Workspace access is on a launch waitlist.
Apply the pattern to your content
Start with one video before designing a whole content operation. A useful handoff should answer these questions:
- Which source and script belong to this piece?
- What is ready, and what still needs a decision?
- Which preferences should carry into the next video?
- Who approves the words and the finished edit?
For a coach, the source might be a question clients keep asking. For an agency founder, it might be a lesson from a project you have permission to discuss. Keep one clear point, write for the ear, and review the result before recording. Our short-form script template gives you a starting structure; the workflow for coaches and consultants adds examples.
Sources and scope
This editorial case study is based on Preston’s public accounts: How To Vibe Edit Videos With One Prompt (September 18, 2026) and How I Edit Videos From My Phone With Codex (September 6, 2026), read October 24, 2026. The original posts contain the walkthroughs and video examples.
This is a founder workflow example, not a measured customer-results study. It does not establish a time saving, publishing volume, audience growth, or revenue outcome. Product availability above reflects the current Melda OS offer.
