I went to church today by the way I was really really feeling down for some reason , as I entered the church a Kidβs church pastor(akka) came me to asking which grade I was in because they was some competition for kids going on in the Sunday class so she wanted to not to miss it.
And then I told her Iβm in my second year of college , and then we both started laughing and she said that I look very young ππ
God really knows how to put a smile on my face.Amen !!
Stop building UI from scratch π
6 UI libraries worth stealing from Part 3 π
https://t.co/HL1YgAxWb0
https://t.co/HDO36vbPxf
https://t.co/JDT9QLjQmK
https://t.co/irUfxiFfsq
https://t.co/oNiXDOxyu8
https://t.co/fncaXmsFGy
Save this for your next build π
Every vibe coder's security prompt:
"My vibe-coded app just leaked user data.
- Move every API key to env variables.
- Rotate the keys I already pushed to GitHub.
- Add .env to .gitignore.
- Turn on row-level security in Supabase.
- Never trust the client, validate on the server.
- Add auth checks to every API route.
- Rate-limit login and signup.
- Hash passwords, never store them raw.
- Use HTTPS everywhere.
- Set CORS to my domain only.
- Sanitize every input against SQL injection.
- Escape output to block XSS.
- Add CSRF protection to forms.
- Lock down file uploads by type and size.
- Hide stack traces in production.
- Set secure, httpOnly cookies.
- Update every outdated package.
- Log every failed login.
- Back up the database daily.
- Add a spending cap on my AI API keys.
Make it unhackable by Friday. Make no mistakes."
Funny thing is, this is actually the whole security checklist.
Bookmark it. Paste it into Claude Code. Then actually check the last two yourself.