You are browsing as a guest. Sign up (or log in) to start making projects!

Mad_Magnetar

@Mad_Magnetar

Joined June 20th, 2026

  • 2Devlogs
  • 3Projects
  • 1Ships
  • 15Votes
Open comments for this post

1h 1m 44s logged

devlog no. 2!!!!!!. so finally i added spotify and it was lowkey easy than i thought yayayayaya!! i was thinking of adding smth else like a sat tracker or a star tracker but ig its good as it is.

0
0
3
Open comments for this post

4h 50m 55s logged

first devlog yayayayayyaya!!!!!!! so this is me first time making something on my own (ofc with gemini)so basically ts was not smth i was planning to build but since i wanted the sticker so bad i decided to build a personal portfolio because ik it takes less time. So i only have to add spotify add smth cool and then i will just smash ship.PROBLEMS: 1)Since my laptop is damn cooked i cant use vs code so i use github codespace and when i wanted to add images i tried many ways but it didnt work at the end i hosted them online and used the direct link 2) choosing right bg colour i tried many combinations then i setteled with ts after my hg told me to just use ts one and sybau.P.S. since ts was my first project please give me some suggestions. THANKS FOR READING!!!!!!

0
0
21
Open comments for this post
Reposted by @Mad_Magnetar

11h 31m 33s logged

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 🥀

39
4
875

Followers

Loading…