Everyone and their mothers has been

talking about vibe coding loops lately,

aka loop engineering. I mean, take a

look here. Everyone from Peter Steinberg

has been saying, "Hey, don't prompt your

agents anymore. You should be building

your loops." Even Boris from Claude

Code, the guy who invented Claude Code,

all he's talking about is loops. "I

don't prompt Claude anymore. What I

mostly use now is loops. I create loops.

They do my entire job." Well, I'm here

to tell you they ain't lying. Here is

the issue though with all this. They've

all been talking about loops, but nobody

is telling you how to build a loop.

There's no one out there directing you

on what a loop actually is. I have good

news for you. I'm about to show you. I'm

here to report I've built an incredible

loop that's basically automated 95%

of the vibe coding work I do. In this

video, I'm going to show you how to

build it and use it. The most

beginner-friendly

loop engineering video you've ever seen

in your life. If you stick with me here

and build out the things I'm about to

show you with you. I'll include all the

prompts, instructions, everything. You

will produce 100x more with your vibe

coding, or I'll refund you all the money

you spent on this video. You are about

to watch a historic first video. The

first video that deep dives into

building an extremely powerful vibe

coding loop. This is loop engineering

101. Now, let's lock in and get into it.

So, let's talk about how you vibe code

before loop engineering and after loop

engineering. This is how you vibe code

before loop engineering. This is

probably what you're doing today. You go

to Claude Code, you go to Codex, you

send it a prompt, you say, "Hey, build

this UI, build this game, build this

feature." It builds it, and then you

test it, and you sit there and manually

test it. When that's done, you send

another prompt, "Okay, now add this

button." Then adds the button, and then

you test it. Every part of this is

manual, right? Everything you do is

completely manual. Everything you do

requires either you typing a prompt or

you testing it out. And here's the

biggest issue with it all. If you're not

at your computer and you're not actively

prompting or testing, nothing's

happening. Nothing's advancing. I'm

juggling like six different projects at

once right now. And before, if I wasn't

spending time on each one of those

projects, they weren't advancing. Only

one project was advancing at once. You

as the human being are the bottleneck.

And while this was a big advancement

over just manually writing code, right?

That's what people were doing before a

couple years ago. Insane, right? While

this is a big efficiency gain over just

manually writing code, it's still not

maximum performance. It's still not

maximum automation because you're still

doing everything manually. Let me

introduce you to the new age. Let me

introduce you to how you will be vibe

coding after you're done watching this

video. We're going to go over here. This

is the fin loop. That is right. I named

the loop. I've Hey, I invented the loop.

I'm allowed to name the loop. This is

the fin loop. Here is how it works. It

consists of three different skills:

spec, build, review. You spend a couple

minutes telling the agent exactly the

ideas in your head, and then it goes in

a loop and all day builds it out,

reviews it, tests itself, builds it out,

reviews it, tests itself over and over

and over again completely autonomously.

And then, at the end, you quickly click

through and it all merges. Instead of

having to work all day completely

manually prompting your agent and

testing it yourself, the only thing

you're doing is kind of loosely telling

it the ideas in your head, and it goes

and it just builds and reviews, builds

reviews tests, builds reviews tests, and

merges it all. Your work goes from

sitting at your computer all day to

coming in, waking up in the morning,

giving a couple ideas, and at the end of

the day you come back to computer and

they're all done and merged. 95% of your

work now is completely automated. You're

not sitting there and prompting over and

over again. You're giving a couple ideas

and the AI figures it all out on its

own, builds it all out, tests it. It's

constantly working even if you aren't

there. So, even if you have just 5

minutes free in the morning, you go into

this loop, which again, I'll show you

how to build out in just a second, stick

around here, and it will go and work

autonomously for you, knowing exactly

what to build, knowing exactly how to

test, knowing exactly how to merge. This

can be done with any vibe coding tool on

planet Earth you're using, whether it's

Codex, Claude Code, whatever you prefer.

Plus, there are some additional tools

added on, which I'm going to show you,

and they're all free. You just add them

onto your coding agent and you have this

really, really nice loop set up that you

can manage and control from anywhere in

the world. You don't even have to touch

Codex or Claude Code anymore. I'll go

into more details in a second. This is

super simple, super easy. I'll give you

the exact prompts on how to set up the

skills you need to set up this loop. And

now, what I'm going to do is show you

how it works, then show you how to set

it up. But before we do that, building

loops for your agent basically just

makes your agent way more reliable.

There are many other ways to make your

agent reliable as well, and thank God

for my friends at HubSpot. They built

the Claude Code Playbook, build systems

that make AI reliable. Just for the

subscribers of my channel, you get this

playbook for free. This playbook gives

you systems that help your agents go

from sometimes doing what you say to

always doing what you say and being

incredibly reliable. In this

easy-to-read playbook, you'll learn all

the systems and tricks to create a

really impactful, powerful Claude rules

file. You'll learn how to prompt your

agent better so you get better results.

Hooks that make sure your agent don't go

off the rail. And by the way, these all

work with the loop I'm about to show

you. They all integrate perfectly. It'll

make the loop I'm about to show you even

more reliable. Sub-agents so you can

have armies of agents working for you,

and so much more. It's going to improve

the quality of your Claude code output

by a ton. My favorite part is the

section on dynamic workflows. You can

have Claude write an orchestration

script that runs up to 1,000 agents

while keeping the lead agent's context

completely clean. That's really, really

relevant to if you're going to build out

the coding loop we're talking about in

this video cuz it all ties together.

This is one of the best educational

materials I've ever read about Claude

code. So, make sure check it out down

below. Link for this free playbook down

below. You got nothing to lose. And

thanks to my good friends and partner at

HubSpot for supporting the channel and

the Fin Fam community. So, as I talked

about earlier, there are three skills

involved this loop. I'm going to be

doing this in Claude code. You can do

this in Codex, Claude code, any tool you

want as long as you can build custom

skills, which basically every tool on

planet Earth allows you to do right now,

you can run this loop. Again, three

skills involved: spec, build, and

review. Mine are called him spec, him

build, him review. So, I'm just doing it

in my him project. But, all you need to

know is spec, build, and review. First

is spec. Again, spec is the first part

of this loop. This is what helps the

coding agent capture all of your ideas.

This is what's going to kick off the

entire loop you see here. Basically,

what I'm about to show you is the only

manual work you need to do to pump out

tons and tons of high-quality code. So,

you wake up in the morning, you grab

your cup of coffee. Now, you want to get

some things built out. So, you're

basically going to your agent saying,

"Hey, here's everything that's top of my

mind." What you do is you use the spec

skill, you give a high-level what your

idea is, what the feature is, and what

the spec skill is going to do is going

to ask you enough questions about what

your idea is until it understands it

completely and can build out a ton of

features for your agent to build. It's

basically going to interview you, come

up with a ton of details. So, To you

have a game you want to build, you do

{slash} spec, then say I want to build a

game, then you hit enter. And now my

agent's going to start asking me a bunch

of questions until it feels fully

confident it can spec out everything it

wants to build in detail. So, I just

answered about 15 questions that allows

it to understand in detail exactly the

feature I'm trying to build in my app,

Henry. It came back and now has five

issues it's going to file for me and

send to the building loop. Again, the

spec skill comes up with a bunch of

issues. Issues are basically detailed

tasks with acceptance criteria, sends it

to our loop, build review test, build

review test. The agent handles all this

for us, and then we come back at night

after all the work is done and merge it

really quick. So, we did spec, it came

up with five different issues it's going

to send to the loop, we just need to

approve it. So, as you can see here, the

spec skill filed five new issues. And

now if we go into Linear, which is the

free app we're using to track all these

issues, we can check them all out. So,

here's an example one of the issues it

made. The AI built out this incredibly

detailed document with everything about

the issue or the task the AI agent needs

to build, all the acceptance criteria

including the non-goals, so what it

shouldn't be doing, everything about the

scope, notes, and expectations on how to

test it. This is all automatically built

out by that spec skill. Multiple of

these issues, and this is all in Linear.

For those who haven't used it, I've told

you to download it a million times.

Completely free project management tool

that basically acts as a second brain

for your coding agent. As you can see

here, it has all these different issues

I'm tracking. It basically allows my

coding agents, Codex, Claude code,

whatever I'm using, to remember every

task it's working on, so that when I

come back or spin up new agents, it can

resume from its current state. It's

basically a second brain and it's

awesome, free, you should download it.

So, all those issues are here. Next,

after those issues are built, it's time

for the automated part. Our work here is

done. We came in in the morning, we

drank our coffee, we gave a couple

ideas, answered a couple questions. Now,

the AI takes it from here and now it's

going to use our two other skills, build

and review, to autonomously build

everything out, then verify what it

built works. Previously, what you were

doing in Vibe Coding was you were

saying, "Okay, now build this out."

You're waiting there while it codes and

prompts, then you were opening up

localhost, testing it out, clicking

around, then going back, "Hey, build

this now. No, change this." Now, we have

skills that describe in detail the best

practices around how to build out these

specs and how to review them and test

them. I mean, it is doing thorough

testing on its own. It's opening up

browsers, it's clicking around, it's

doing everything. Let me show you how

this works. So, let's set up the build

loop. The build loop that I'll go over

and over and over again building out

every single spec that is in our

backlog, right? As you saw in the last

screen, we had five specs built out from

our spec skill. Now, the build loop will

go through and over and over and over

again build all of them out. In Claude

Code, all we would need to do to do this

is do {slash} loop five min {slash} him

build. What this does, {slash} loop

basically tells the chat, "Do this next

thing over and over and over again."

Five min tells it how often to do it.

So, every five minutes it's going to do

it. And what it's going to do is run him

build, our new skill. Again, I'll give

you the prompt in a second how to set it

up that builds out any spec in our

backlog inside Linear. So, those five

specs that we just built out. So, it's

going to every five minutes run him

build. So, basically, put it on a loop

all day just building, building,

building, building, building for us. And

again, all the build skill is is a skill

that tells Claude code or Codex or

whatever you're using exactly how to

read and build out each one of those

issues in linear. It also tells it how

to move it along our pipeline, how to

push it to the review skill, and how to

keep our entire loop running even when

we're not at our computer. So, I'm going

to hit enter on that, and it is going to

start building out our specs. At the

same time as that, we are going to set

up our review loop. So, let's do this.

I'm going to open up another chat. I'm

going to do the exact same thing,

{slash} loop

5 min {slash} review, and I'm going to

hit enter on that. This is going to set

up another loop where our agent is now

going to review every spec built out,

every spec marked as waiting. So, when

our agent is done building out each one

of the specs, it gives it a label that

says, "Okay, ready for review." And then

our review loop waits to see that label

to start reviewing everything. And all

our review skill is is basically just

instructs the agent how to review

everything built out, so how to open it

up in a browser, test it out, click

around, how to apply the label once it's

done being reviewed, how to spin up its

own pull request with that specific code

in it, how to put that pull request into

a sandbox environment so you can test

out just that specific change, and how

to write instructions for the user on

how to test it themselves. Each one of

these new skills that I'm going to have

you build out is really, really simple

to do. It's just one prompt. All it's

doing is instructing the AI how to push

issues through our loop here, and how to

keep everything moving, and how to save

you way more time, and get you way more

productive. So, the agents are

autonomously building out the issues,

then another agent is autonomously

reviewing them. What happens when the

agent reviews an issue,

tests it out, sees that it works well,

what it does is it takes that pull

request and sends it to us in our

messaging service of choice. So, for me,

that messaging service is Slack. You can

use anything for this. You can use

Discord if you want. You can use

Telegram if you want. Slack is really

built for this type of workflow, but you

can 100% do this in Discord as well, no

big issue. One of the prompts I'll give

you down below as well will instruct

your AI agent on setting this all up.

You don't need to set up Slack. You

don't need to set up Linear. You don't

need to set up the loops. The AI does it

all for you with the prompts I'm going

to give you. So, I have this channel

merge ready. The review loop messages me

here. As you can see, Henry loops. It

describes the pull request. It describes

the issue, what it did. It gives me a

link if I want to test it myself, so I

can open up this preview. It's just like

a preview branch in Vercel that just has

the one change the agent made. It gives

me step-by-step on how to test it if I

want to test it myself. And then when

I'm ready, all I need to do is react

with a rocket ship emoji. When I react

with the rocket ship emoji, the agent

goes, "Got it. I'll merge it." And then

it goes, "Merged by me." and puts a nice

green check mark right on that merge to

say, "Yep, it's merged in. It's live in

the app." And just like that, the code

was built, right? All we had to do is

come in at the beginning of the day,

answer a bunch of questions from our

agent. The agent then autonomously

builds and reviews and tests everything.

Then we come in and just click rocket

emoji, rocket emoji, rocket emoji,

rocket emoji, and it's all merged and

done. Our work went from 100% manual,

take all day, you have to sit at your

computer, to you just come in at the

beginning of the day, answer a few

questions, and at the end of the day you

hit merge, and you're good to go. This

is the thin loop. This was what makes it

so powerful. If you look down below,

there is a Google Doc. The Google Doc

has several prompts in it. It has

prompts for setting up each of the three

skills, as well as a prompt you can give

to your agent, whether it's Claude,

Code, Codex, or whatever, to set up the

Slack, Discord, Linear, whatever you're

using, and get the entire system

connected in place. This isn't gate-kept

behind an email or anything. It's

completely free. Just click the link.

You don't have to do anything. It's just

a Google Doc you can copy and paste into

your agent. We don't gate-keep here on

the Fin Fam channel. AI, especially with

stable 5 and GBT 5/6, has become so

smart. There is no more need to baby-sit

every step of the way. Basically, every

part should be automated, right? And

we're still doing manual work. I'm

working on now figuring out how to

automate even the manual work. How can

we automate coming up with ideas? That's

what I'm building out right now. I want

to get the spec step even easier and

even less human-intensive. And as AI

becomes smarter, it might even already

be at that point. We don't even need to

merge it ourselves. We can probably just

trust it to merge it for us. But right

now, I still want these two manual

steps, beginning of the day, end of the

day. But all that hard work in the

middle of the day, that's done. You

don't have to worry about it anymore.

That's all handled by the Fin loop. All

the tools you need for this, completely

free. I'll link them all down below. The

prompts to set this up, completely free,

link down below. You have nothing to

lose by setting up this loop. It just

saves you tons and tons of time and

helps you get done way more. You take

this a step further, you start five or

six different projects, you just come in

the morning, answer specs for all six of

them, they work autonomously all day, at

the end of the day you have six projects

moving forward without your work all the

time. Everyone on the internet's been

talking about coding loops. Now you know

it, now you can implement it. And if you

implement this, you are ahead of like

literally 99.99999%

of people. I'm not even joking. Even the

most hardcore vibe coders right now are

not setting up loops like this. Do

yourself a favor, block off half an

hour, go through this again, take the

prompts from down below, give them to

your agent, get this set up. If you want

to take it even a step further, you can

copy the link of this video up above or

hit share down below, give it to your

agent, say, "Hey, look at the transcript

of this video and set it up for me."

Like that's actually probably the

easiest way to set this up. If you

learned anything at all, make sure to

leave a like down below, turn on

notifications, and subscribe because all

I do is make amazing videos about AI.

It's an absolute honor and a pleasure to

be helping you out, to be educating you,

to be working with you on these things.

I'm discovering new things every day.

All I do is discover things, then share

it with you. So, I hope you're enjoying

it. Hope you're learning something from

it. I absolutely love this stuff. It is

so much fun, and I hope you're having

fun with it, too, and I'll see you in

the next video.