Open-sourced something (MIT) that might save you a boring week. Every time someone vibe-codes a prototype with Claude Code or Cursor, the demo works, then they hit the same wall: real auth, roles, and actually-secure data access. Most people end up hiding buttons in the UI and calling it security. One open DevTools and it's gone. So I built a Next.js + Supabase starter that handles that part properly: - Google OAuth, no passwords to store - Three roles out of the box: admin, manager, viewer - Security enforced at the database with RLS, not in the UI. The database refuses the write. That's the difference. - CSP and security headers preconfigured - CI/CD on every PR, one-click Vercel deploy It's the layer between "the prototype works" and "I can let real users in." link Free to fork. I'd genuinely like eyes on it, tell me what you'd change, what's missing, or where the security model could be tighter. PRs welcome. What do you normally reach for to handle this part?

I am in the process of learning how to build with Claude Code. Who in this community wants to get involved in my journey to mastering this new tool? Comment below if you... 1. Have been using Claude Code for at least 6 months 2. Speak fluent English and live in Americas or Canada 3. Eager to teach and grow with me! Who wants to bond with me over the next 3 months?! Tell me about your experience with Claude Code and why you'd be an awesome partner to help me learn! I am non-technical but VERY good with N8N and I learn fast!