Activity
Mon
Wed
Fri
Sun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
What is this?
Less
More

Memberships

1 contribution to A2B - Go From App to Business
FREE PROMPT PACK - Login Security | June 17th
Copy/paste these into Claude Code/Codex: - Move the session out of localStorage: "My vibe-coded app stores its auth/session token in localStorage. Migrate me to httpOnly, Secure, SameSite=Lax cookies using [Supabase @supabase/ssr | Clerk]. Show the exact client + server changes, confirm no token is ever readable from window.localStorage, and tell me how to verify it in DevTools." - Enforce auth on the server, not the browser: "Audit every API route / server action in my app for missing server-side authorization. For each protected action, add a check that re-verifies the user's identity and role from the server session (and add a matching Supabase RLS policy). List which routes were unprotected and show the before/after for each." - Require email verification: "Enable required email verification in [Supabase Auth | Clerk] and block unverified users from any write/sensitive action. Show me the provider setting to flip, the server-side guard that checks email_confirmed_at (or Clerk's verified status), and a redirect to a "please verify" screen." - Rate-limit login / signup / reset: "Add rate limiting and temporary lockout to my login, signup, and password-reset flows. Use [Supabase Auth's built-in rate limits | Upstash Ratelimit middleware]. Specify sensible limits (e.g. 5 attempts / 15 min per IP+email), the lockout behavior, and how to test that the 6th attempt is blocked." - Strong + non-breached passwords: "Enforce a strong password policy in [Supabase Auth | Clerk]: minimum length 12, block compromised passwords via the HaveIBeenPwned / leaked-password setting, and surface a clear strength error in my sign-up UI. Show the provider setting and the client validation, and confirm a known-breached password is rejected."
1 like • 21h
Solid pack Worth adding one thing since you mentioned Supabase even after you move tokens to httpOnly cookies and lock down server auth,you're still exposed if RLS isn't set up The anon key is public by design it lives in your client. So if a table has RLS off or no policies someone can just hit the Supabase REST API with that key directly and skip your server completely. Your Next.js routes can be perfect and the DB is still wide open. Prompt for the pack: "Audit every table in my Supabase project which have RLS on vs off, and for the ones that are on, list the policies. Flag any table that's readable or writable by the anon/authenticated role without a policy scoping rows to the owner, and give me the SQL to fix it." Hit this myself doing a security pass on one of my apps server was clean the DB wasn't. Keep it up man your friend, Basel❤️
1-1 of 1
Basel A
1
4points to level up
@basel-a-6243
18. Self-taught since 13. I build AI products that ship and make money real estate tech, solo. No slop.

Active 20h ago
Joined Jun 17, 2026
Powered by