One model.
Three jobs.
Here's how.

I've put my raw footage for a vertical video (9:16) in this folder: a camera file with my audio, and a screen recording shot at the same time.

Before you cut anything:
1. Transcribe the camera audio with word-level timings.
2. Find every double take, false start and dead pause.
3. Show me a cut plan: what you keep, what you drop and why, with timestamps.

Rules for this edit:
- Keep the last complete take of any line I repeated.
- Never cut in the middle of a word.
- When I'm talking about something on screen, show the screen recording on top and me underneath, in sync with what I'm saying.
- Captions above my head, not over my face.
- A bold hook title in the first frame, fully visible from frame one.

Tell me which tools you need on this computer to render it, and wait for my approval before you install anything. Don't render until I approve the plan.

Here are my notes on the version you just rendered. Make a new version. Don't overwrite the old one.

- 0:04: the sound effect is too loud. Make every sound effect softer, well under my voice.
- 0:12 to 0:20: show my real screen recording here, not a graphic.
- The captions sit too low. Move them above my head for the whole video.
- 0:31: there's still a repeated phrase. Keep only the second take.

After you render, list what you changed against each note, so I can check them one by one.

We're done with this video. Now go back through every note I gave you in this project and turn them into permanent rules in my video-editing skill file. Create the skill if it doesn't exist yet.

For each rule, write:
- the rule itself, in one line
- why it exists (the problem I flagged)
- how to check it on the finished render

Don't include anything specific to this one video, like timestamps or topic. Only the rules that should apply to every future edit. Show me the updated skill before you save it.

There's a reference video in this folder. I like its editing style and want my own intros to feel like it, without copying its content.

1. Use the video-understanding tool to break the reference down: shot lengths, framing, how text appears, how callouts are styled, pacing of the opening seconds.
2. Write that up as a short style spec and show it to me.
3. Build a reusable intro template in my brand colours and fonts that follows the spec. I should be able to swap in a new title and new footage each time.
4. Render one sample so I can review it.
5. Once I approve, save the style spec and the template as a skill for horizontal videos.

The file in this folder is the transcript of a group call. Somewhere in it is one idea people found genuinely useful.

1. Read the whole transcript. Pull out the single most useful, repeatable method from it. Tell me which one you picked and why, in three sentences. Wait for my OK.
2. Then build a one-page lead magnet as a single HTML file: a clear headline, the problem, the method step by step, and a short playbook section someone can follow on their own.
3. Use only what was actually said on the call. Don't invent numbers, results or quotes. If something is missing, leave a gap and list it for me.
4. Remove every participant's name and anything private.
5. Make it mobile-first, fast, and printable. Use my brand colours and fonts.

Build it locally only. Don't publish or deploy anything.

I'm taking over a website project. Everything I have is in this folder: a handoff doc, old notes, some copy and a few images. It's messy.

1. Read everything first. Write me a one-page summary: what the site is for, who it's for, which pages exist, what's finished and what's missing.
2. List every open question and every contradiction between the documents. Don't guess the answers.
3. Once I've answered, build the pages that are ready, and mark anything still waiting on the client clearly on the page.
4. Give me a checklist I can walk the client through.

Keep it local. I'll choose the hosting myself.

The page is approved. Before you deploy anything, give me my hosting options for a static page like this, including Cloudflare and my current host. For each: what I need to set up, what it costs me, and what could go wrong.

Don't deploy until I pick one and say go.

I want to run an advisory-board session on a decision in my business.

The decision: [describe it in two or three sentences]
What I know: [numbers, constraints, what I've tried]

Set up a board of five advisors with different lenses: a growth operator, a finance-first CFO, a customer advocate, a sceptic whose job is to find the flaw, and someone who has built this exact kind of business before.

Round 1: each advisor gives their view in one short paragraph.
Round 2: they challenge each other where they disagree.
Round 3: give me the decision you'd make, the biggest risk, and the cheapest test I could run this week to check it.

Mark anything you're assuming rather than taking from what I told you.

Before I build anything, I want you to try to break this idea.

The idea: [describe it]
Who it's for: [describe them]
What I'd build first: [describe it]

1. Give me the five most likely reasons this fails, ranked by how likely they are.
2. For each, the earliest signal that it's happening.
3. Which one could I test in under a week, without building the full thing?
4. What would have to be true for this to be worth building at all?

Be direct. Don't soften it. I'd rather hear it now than after I've built it.

Read the system in this folder before you change anything. Explain back to me, in plain language, what each part does and how the parts connect.

Then plan how to extend it to [new platform or new use]. Reuse what already exists. List every file you'd change and why, and tell me what could break. Don't change anything until I approve the plan.