Free drops from my reelsYou're on 1 of 44 free drops.Every free thing I promise in a reel gets its own page like this one. The rest are one tap away.See all 44 →
REEL 48 THE BLUEPRINT

Build your own AI tool. Even if you cannot code yet.

I am a video editor. 52 days ago I could not build software. Today my own AI video editor has 24 tools, 32 skills and 26,982 lines of code, and it made the reel that sent you here.

This page is the exact method. It works for any field: accounts, design, medicine, law, marketing, teaching. You do not need a CS degree to start. You need one boring task and one hour.

install it (needs Node.js)
npm install -g @anthropic-ai/claude-code

Claude Code is a paid tool. Any AI coding tool works with this method: Cursor, Codex, Gemini CLI. The method matters more than the tool.

52 days24 tools32 skills26,982 lines45+ reels madecounted 2026-09-20
01

The one idea behind all of it

When AI arrived, everybody got the same tools. Same ChatGPT. Same Claude. Same models.

A non-technical person got a better assistant. They ask, it answers, and tomorrow they ask again.

A technical person got a factory. They build a small tool once, and the tool does the task every day after that.

So the question to stop asking is "can AI do my job?" The question to start asking is "can we build a tool that does one repetitive part of my job?"

02

Proof: day 1 and day 52

Same person. Same account. No team. The only thing that changed is the system.

A frame from my first reel: dark background, text only, no face
Reel #1, 30 July 2026. Text on a dark screen. No face.
A frame from reel 48: my first reel small and dim on the left, a new reel large on the right with me on camera, and a date rail reading DAY 51
Reel #48, 20 September 2026. Built by the system.
Instagram Reel Insights for reel 41: Views 236,576, Viewers 192,909, Follows 1,645

My own Instagram insights for reel #41, screenshot taken 2026-09-20. It passed 215,575 views in its first 8 days.

03

The 8 steps I actually used

Nothing here is theory. Every step is something I did, in this order.

1Pick one boring task you repeat every week

Not your whole job. One part. A weekly report. Invoices. Renaming files. Sorting emails. Cutting silences out of a video.

The test: you do it at least once a week, it follows the same steps each time, and you could explain it to an intern in 5 minutes.
2Write down what "done" looks like, before you open any AI

What goes in. What comes out. What a good result looks like. Use plain words. A rough drawing is fine.

I drew my editor as text before a single line of code existed:

my real sketch, from the project README
 R | DRAWER   |        THE PICTURE        | THE CARD
 A | Media    |   click, drag, corners    |  Position  54  236
 I | Text     |   double-click to type    |  Size     972  560
 L | Captions |                           |  Opacity  ====
   | Scenes   |  SCENES  F C N C C N C F  |  > Animation
   |          |  V1  [facecam .........]  |  > Media
Why this matters most: the AI can write the code. It cannot know what you want. You are the expert in your field. That is your real advantage over a programmer.
3Ask for the worst version that works

Open your AI coding tool in an empty folder. Paste the starter prompt below. Ask for the smallest thing that runs today. Ugly is fine. One file is fine.

The trap: people ask for the finished product on day one, get a big broken mess, and quit. Version one only has to run.
4Use it on real work the same day

Not a test file. Your real task. Write down every single thing that annoys you while you use it.

My first editor: grey blocks on a plain timeline, a notes box, no picture tools

My first editor, 11 August 2026. Grey blocks and a notes box. It could only make small changes. I used it anyway.

5Fix one thing per session

Take the most annoying item on your list. Ask the AI to fix only that. Test it. Stop. Next session, the next item.

Why one: when you change five things and it breaks, you do not know which change broke it. One change, one test. That is the whole method.
6Write your rules in a file the AI reads every time

Every time you correct the AI, write the correction down as a rule in a plain text file in the project. In Claude Code that file is called CLAUDE.md. The AI reads it at the start of every session.

This is how the tool starts to work the way YOU work. My rules file holds things like "never invent a number" and "show me still frames before you build anything".

Without this you repeat the same correction forever. With it, a mistake only happens once.
7Turn every mistake into an automatic check

When something goes wrong, do not just fix it. Ask the AI: "write a check that fails if this ever happens again." Run all the checks before anything goes out.

A terminal showing my checker: FAIL 34 pass, 6 warn, 9 fail, and a red bar reading RENDER BLOCKED exit code 1

A frame from the reel, built from my checker's real output on an old video: 9 fails, so the render is blocked.

This is the step that makes it a system. Mine started as 27 checks on 26 August. Every note I gave on a video became a new one, and it now runs over 40. It refuses to render a video that breaks my own rules.
8Only now, connect the pieces

After a few weeks you will have several small tools. Now ask the AI to connect them, so the output of one becomes the input of the next.

My control room: columns for Topic picked, Script, Approved, VO done, Board, Building, with reel 48 sitting in the Script column

My control room today. One card per video, moving left to right. This reel is the card in the SCRIPT column.

04

The starter prompt

Fill in the four lines in CAPITALS, then paste it into your AI coding tool in an empty folder.

paste this
I am not a programmer. I work as a YOUR JOB.

Every week I do this task by hand: DESCRIBE THE TASK IN 2 OR 3 SENTENCES.
What I start with: WHAT GOES IN (files, emails, a spreadsheet, a video).
What I need at the end: WHAT COMES OUT.

Build me the simplest possible tool that does this. Rules:
1. The worst version that works. One file if you can. No extra features.
2. It must run on my computer today. Tell me exactly what to install
   and the exact command to run it.
3. Before you write any code, ask me up to 5 questions about how I do this task.
4. Explain every step in plain English. I want to understand what you built.
5. Create a file called CLAUDE.md in this folder. Every time I correct you,
   add the correction there as a rule, and read that file at the start
   of every session.

When it runs, I will use it on real work and come back with ONE thing to fix.

The line that matters most is number 3. Let it ask you questions. Your answers are the part no programmer could have written.

05

How mine actually went

Real dates from my build log. Notice how small the early steps are.

29 JulyProject folder created. A scraper that finds videos that blew up, and a radar that scores the day's AI news. Nothing that makes video yet.
30 JulyReel #1 posted. Text on a dark screen. No face. It did its job: it existed.
11 AugustThe first editor. A small page for minor changes, built because the tool I was using kept breaking.
12 AugustI threw away two visual styles and rebuilt the look by measuring a video I admired, frame by frame.
26 AugustTwo rules that changed everything. One: I approve still frames before anything gets built. Two: one command runs every check, and one fail blocks the video.
3 SeptemberCutroom, my real editor, built in a single day. It only took a day because the 5 weeks before it taught me exactly what I needed.
8 SeptemberReel #41 goes out. 215,575 views in 8 days.
20 SeptemberDay 52. 24 tools, 32 skills, 26,982 lines. The reel that sent you here.
Cutroom, my editor, today: a video preview with handles, a properties panel on the right, a multi-track timeline with scenes and captions

Cutroom today, with a finished reel open in it.

06

The honest part

It did not replace me. I still record my own voice and face. I still decide what the video says. I still give notes on every one. The system does the hours of repeated work. The taste is still mine.

It broke constantly. Most sessions started with something broken. That is normal. Broken and improving beats perfect and imaginary.

I still learned real technical things along the way. What a file path is. What a terminal is. How to read an error message. You will pick these up as you go, and they are the part that makes you hard to replace.

So should you study computer science? If you can, yes. Understanding how software works gives you leverage in almost every field. But if you already chose another path, you are not late. Learn enough to build. That is the new floor.

07

What my system is made of

The AI tool is paid. Everything else here is free to use.

08

Your turn. One hour.

Pick the task. Write what "done" looks like. Paste the prompt. Get the worst version running today.

Then fix one thing tomorrow.

Keep going

More free drops from my reels

See all 44 drops →
Reel #55 · comment PAPERSFree past papers for all of Pakistan. Built in one day./papers → Reel #54 · comment FREELANCEHafiz Basit Ali. Freelancing, taught free./freelance → Post #8 · comment BANAO5 apps Pakistan needs. Nobody built them right./banao →
Rahman waving
Who made this

Hi, I'm Rahman.

I've been building things people pay for since I was 10. Online game servers first, then $250K+ earned in tech. Now I build with AI in public, and every free thing from my reels lands on a page like this.

Questions? Ask in the Discord.

Free tools, honest feedback on your work, and people who answer.

Join free
Know someone who needs this? Send them the page.
rahmanbuilds · free, no sign-up