You commented PLAN. Here is the file, the way the system reads it, and a template with three real entries from my own November. The idea I plan once a month and decide once a day. The plan is one JSON file. Every post is one entry. The studio reads the file, draws it as a calendar, renders whatever has a script, and creates one scheduled job per post. My job each day is a tick. ...
You commented CLIP. This is the system, with the code that matters. It is not a product. It cuts Shorts out of my own films in my own format, and that narrow scope is exactly why it works. What goes in, what comes out In: one film already cut from phone clips (the Dashain film, nine minutes, sixty-five iPhone clips shot in HLG), plus the catalogue of those clips. Out: five vertical Shorts with a title stamp, natural sound, an optional music track, loudness-normalised, uploaded to YouTube as scheduled videos in one command. ...
You commented STUDIO. Here is the whole thing, with the parts named, what each one does, and what it cost. Nothing here is a product you can install; it is my own setup, built with Claude Code over a few weeks, and I describe it so you can build your own version of the parts you need. What it is in one paragraph A local web app on my Mac in Panauti. It reads a month plan, writes each reel’s script into a JSON file, voices it with a clone of my voice, renders a vertical video, uploads it to YouTube as a scheduled Short, posts it to Facebook and Instagram at the right minute, pulls the comments back every half hour, drafts replies in my voice, and sends my phone a notification whenever something needs me. Nothing goes out without my tick. ...