if your vibe coded app takes payments, ask Claude today:
"do we verify the Stripe webhook signature?"
if the answer is no, anyone can send your server a fake "payment succeeded" and unlock your paid stuff for free
the fix is a few lines only, Stripe's docs show it
when claude code keeps going in circles:
1. esc to stop it
2. /rewind to before it went wrong
3. /clear for a fresh start
4. give it only the file and the exact error
5. ask for 2 possible causes before any fix
30 second test for your vibecoded app:
log in on your phone and laptop. change your password on the laptop
is your phone still logged in?
if yes, someone who stole a password keeps access even after it gets changed
fix: ask claude to end all other sessions when the password changes!
most vibecoded free plans have a HUGE hole:
nothing stops someone from making 100s of free accounts..
so they use your paid features (and burn your credits) for free forever
ask your agent: "what stops someone from making 100 free accounts?"
possible fixes
- verify emails
- block throwaway email domains
- cap free usage / day
I gave claude a map from a random town generator without any notes, extra ideas or anything inside Omniscio
only asked it to write a real travel guide for this nonexisting town
it came back with a full guidebook: history, every neighbourhood, where to eat, what to avoid, a 3 day plan and all 33 places pinned to the mapπ
cant think of a more useful use case of AI!π
vibecoders:
reminder for what should NEVER be sent to the browser:
> other users emails or phone numbers
> password hashes
> API keys or secret tokens
> fields the page doesnt even show
if its in the API response, anyone can read it in dev tools!
ask your agent: "does any API return more data than the page shows?"
signs your app was vibecoded:
> every button has a gradient
> 4 different fonts
> the loading spinner never stops
> "built with β€οΈ" in the footer
what else would you add?
does your vibecoded app have a search bar? ask your agent:
"is user input ever put straight into a database query?"
if yes, someone can type a few characters and read or delete your whole database..
fix: use parameterized queries or your ORM, never glue user text into SQL!
reminder for what should NEVER be in your git repo:
> .env files
> API keys or tokens
> database dumps
> user uploads
if one already got pushed it doesnt help to delete it. rotate the key immediately
how i start every new claude code session:
1. /clear
2. tell the goal in 1 line
3. ask for a plan first before any code
4. ok the plan
5. let it cook
6. ask it to test what it just built
reminder for where user roles should be checked (for vibecoders):
> on the server: every request
> in your database rules: yes
> a hidden admin button: not a check
> a role saved in the browser: NEVER trust it
ask your agent: "can a normal user make themselves admin by editing a request?"
stop guessing which AI model is best for your project
in Omniscio you can send the same prompt to several models at once and watch them build side by side, in parallelπ
i tested it by asking opus 5.5, fable 5.1 and sonnet 5.5 for a beautiful simulation of the solar system:
fable: 11 min
sonnet: 13 min
opus: 15 min
which do you think looks best?π€
if your vibecoded app uses the claude or openAI API, ask your agent one thing today:
"can someone who isnt logged in call our AI endpoint?"
if yes, anyone can run up your AI bill overnightβοΈ
fix:
- require login
- cap requests per user per day
- set spending limit in the provider dashboard
i just gave claude a random house from a floor plan generator. 3 floors, nothing else
then asked it to turn it into a murder mystery party game in Omniscioπ₯³
it made the whole box:
- case file
- 6 suspects with secrets
- police floor plans with red pen
- sealed evidence tags for every room
etcetc
then it hosted a FULL GAME itself and the detectives caught the killer!
i just love trying out new use cases with ai man
reminder for how file uploads should work (for vibecoders):
> size limit: checked on the server
> file type: checked on the server (not just the extension)
> private files: links that expire
> public by default: NEVER
ask claude: "can anyone open a file another user uploaded?"