Cursor for YouTube: A Weekly Build-in-Public Short

Cursor for YouTube

A weekly Short about what you built is the cheapest honest content a solo maker can produce: the work already happened, and viewers like watching progress. What stops most people is the Sunday-evening effort of remembering what changed and phrasing it. Cursor sits in the editor with the commit history, so it can do the remembering. This page follows a founder of a recipe app who posts a 45-second recap each Friday, covering what Cursor reads, how the script follows the recording, what stays out of the frame and how the draft waits for approval in Tareno.

Example: a recipe-app founder posts a Friday recap

Imagine a founder who builds a recipe app alone. On Friday she asks Cursor to read the week's commits and pick the two changes a user would notice: a faster search and a new shopping-list screen. She records a 40-second clip of both on her phone simulator, exports it vertically and adds it to the Tareno library. Cursor writes a 45-second script that follows the recording and a title under 100 characters, finds the file with list_media and saves the draft through create_drafts. It also notices that last week's Short, read through list_account_posts, opened with a number and suggests the same here. She approves the Friday 18:00 slot in the dashboard.

Step by step

1. 01

   Ask for the two changes users notice

   Have Cursor read the week's commits and pick no more than two changes visible on screen. A weekly Short that covers five things shows none of them clearly.

2. 02

   Record what you will describe

   Record a vertical clip of up to 60 seconds, export it and add it to your Tareno library. Cursor cannot record, and a script written before the recording tends to describe a demo that does not happen.

3. 03

   Check what the frame shows

   Look for test accounts, emails, unreleased pricing and anything from a customer. If it should not be public, it should not be in the clip.

4. 04

   Write the script to the footage

   Ask for a spoken script of about 45 seconds that follows the recording, plus three titles of at most 100 characters. The script has to match the footage second by second.

5. 05

   Learn from last week's Short

   Ask Cursor to read your channel's recent videos through list_account_posts and say which opening worked best. Reuse that pattern, not the sentences.

6. 06

   Save the draft and approve

   Cursor saves the title and the clip through create_drafts. Request a slot with a date, a time and an IANA time zone, and approve the pending request in the Tareno dashboard.

Prompts to copy

Read the commits from the last seven days and pick at most two changes a user would notice on screen. For each give a one-sentence description in plain words and tell me what I should show in a 20-second part of the recording.

I recorded [recap-week-12.mp4], a 40-second clip that shows the faster search and the new shopping-list screen in that order. Write a 45-second spoken script that matches the footage, with a hook in the first sentence, and three titles of at most 100 characters.

Use Tareno to list my last five Shorts and tell me which opening line got the most views, with the numbers you can see. Describe the pattern in one sentence, and apply it to the new script without reusing the wording.

Use Tareno to find [recap-week-12.mp4] and save it as a YouTube draft for [channel name] with title option [1]. After I confirm, ask Tareno to schedule it for [Friday 18:00] in the [Europe/Lisbon] time zone and return the pending action ID.

Mistakes to avoid

• Covering the whole week. Two visible changes make a clear Short; five make a list nobody remembers.
• Recording after writing. If the script describes a flow you then do not film, the voiceover and the screen disagree.
• Showing a screen with a test account's email in the corner. Check the edges of the frame as well as the middle.
• Copying last week's opening word for word. Reuse the pattern, such as a number first, and write a fresh line.