I Created a Vibe Coding Checklist Nobody Asked For

#vibecodingtools #vibecodingchecklist #vibecodingguide #generativeaitools

And put 101 checkpoints in it, that nobody would ever be able to check off.

In case you are not a reader and want to checklist right away, here is the link .

There comes a point in your life when you remember that you can do things just because.

I started learning Spanish. Why? Just because.

I went without speaking for 3 hours. Why? Because I wanted to.

I put together a Vibe Coding Checklist that is longer than my resume even though I have been Vibe Coding for only 3 months. Why? Because I wanted to.

And because I can.

And of course, because I like to research.

In case this is the end of your attention span, here is the link to your too long checklist for vibe building .

So here is how it works.

It has 5 sections and (I hope) walks you through the complete journey of Vibe Coding a solution you have in mind.

And that means the foundation which where you actually put things down like what exactly are you trying to solve?

Because I realized a lot of people don’t know their why.

And as Simon (Sinek) says, know your why.

And then there are detailed things like what features do you want?

What exactly is you think you are building or you know some technical stuff that half of which I don’t even understand.

I don’t even know if it’s worth reading anymore. Here is the link to your vibe coding checklist.

AND It’s Inter… Wait for It… Active, Interactive

So like a propa vibe coder, So I went ahead and put it on GitHub so nobody can ever look at it and it goes down the black hole of the internet.

Now I have put some features on it so that it could look shiny but not usable at all.

If you are a procrastinator like me, you will start with adding the project name and summary and look at the long list of checkpoints and never come back to that checklist

Play things really!

but hey, I could do it with codex and so I did. If you are still reading here are some shiny things you will see:

Project name & Project summary (I know I already said it.)
Interactive checklist & Checkboxes with a Progress bar that will never be completed.
Phase grouping, Phase progress summary (So that at least I feel good about myself.)
Generic vs project-specific labels, Item filters, Show/hide completed toggle (You know, the generic vibe coding stuff.)
The best one: DOWNLOAD as a CSV (Ohhh, how exciting because you couldn’t ask your AI to make the checklist, so you need my checklist in CSV which nobody ever uses.)

How to Use It?

Gitpage

If you are a vibe coder, then I am not sure if you can do this whole GitHub repository thing where you have to clone the repository locally and then you can open the file in your browser locally and then so on.

For us uneducated builders, I just created a gitpage.

You just open it and start using it. Hope then it’s very easy for you to use it.

As for the GitHub page, if you haven’t noticed, I have it linked everywhere in this blog.

Sounds easy right?

I mean try doing it. It is 100% not easy.

Cloned Repo

And if you are someone who understands GitHub repo, congratulations!

You can just do the cloning thing, get it on your laptop and start using it.

Bonus (Not really)

Plus like I said, there is a CSV download feature so you could just probably download it if you don’t like the shiny things I added.

So that’s how you use it.

But one of the things I do want to point out is to use the security checklist. So you don’t miss stuff like exposing your tools user-base to some random person. Who can ask you to pay them $10,000 to just take care of things AI already could.