i just added a many things to the game like a big spider like a boss enemy that you should dmg him (still in dev) a bullets that’s spawn randomly and you take dmg when it’s hit you and you can shoot the bullets to destroid their and The area you are standing on shrinks significantly within 30 seconds.

my first steps : mechanical mouvement, smooth mouse, 10 bullets in your gun, auto reload when you have 0 bullets and a small enemy under development

i also add a watch time screen and a terminal!

the welcome page

the clicker game is available! with the notepad

i just added a calculator

my first steps in the project ( arabic WEB OS / game / notebook / cursor changer/ time…. )

VibeCheck Devlog #1 🥀

so…

for the last few days i’ve been building something called VibeCheck.

the idea is pretty simple:

you paste a prompt.

VibeCheck tears it apart.

then tells you how to make it better.

that’s it.

but somehow that “simple” idea ended up turning into an entire app 💔

---

the original problem

i kept seeing the same thing over and over.

people would ask an ai for something.

the result would be bad.

then they’d blame the model.

when half the time the real problem was the prompt.

so i thought…

what if there was a tool that could actually analyze prompts and explain what’s wrong with them?

not just give a score.

actually tell you:

• what’s missing
• what’s unclear
• what’s limiting the output
• how to improve it

and that’s basically where VibeCheck started.

---

browser compatibility was a disaster

one thing i realized pretty quickly…

the whole app depended on chrome extension APIs.

which means outside a chrome extension…

everything exploded 💔

so i built a chrome api polyfill layer.

now VibeCheck can run inside an extension and directly in a browser without completely falling apart.

storage works.

runtime messaging works.

browser preview works.

and the app stops screaming at me every time i open it.

---

template collection got out of control

this one got a little ridiculous.

templates went from:

15 → 38

there’s now stuff for:

• ui components
• full applications
• backend systems
• debugging
• ai prompts
• api development

and probably more coming later because apparently i don’t know how to stop adding things.

---

random suffering

also spent way too long fixing bugs that should not have existed.

you know the type:

40 minutes of debugging.

3 line fix.

questioning life choices afterwards.

those.

---

what’s next?

right now i’m focusing on making the scoring system smarter and improving the actual prompt analysis.

the ui is pretty trash so id be working on that too

the architecture isn’t actively trying to kill me anymore

and VibeCheck is slowly becoming the tool i originally wanted to build

we’ll see how long that lasts before i break everything again 🥀

my shooter game

my game

that’s crazy to see my work in 1h