isekai-backendlisted

# Isekai Backend — the other half of a $10k build A beautiful frontend with no real backend is a mockup, not a product. This skill is what turns an isekai build into something a client could actually log into, pay for, and trust with their data. Use it any time a build needs accounts, a database, uploads, or a real deploy — not just "add a backend" requests. ## Stack (free, production-grade) - **Database + Auth + Storage**: Supabase (hosted Postgres, free tier: 500MB DB, 1GB storage, 50k monthly active users) - **Framework**: Next.js App Router, deployed on Vercel's free Hobby tier - **Client**: `@supabase/ssr` — the current official package for cookie-based sessions in Next.js. The old `auth-helpers-nextjs` is deprecated; never scaffold it. - **Components**: use the `shadcn` skill for forms, tables, and auth screens instead of hand-rolling markup. ## BANNED (the default AI-backend look — never ship any of these) - Row Level Security left **off** "for now" — the #1 way Supabase side-projects leak every row to anyone with the anon key - `service_role` key referenced anywhere in a Client Component or a `NEXT_PUBLIC_*` env var - Secrets committed to the repo with no `.env.example` for the next person - One Supabase project shared between local dev and production - Forms that write straight to the client SDK with no server-side validation - Tables with no `created_at`/`updated_at`, no primary key strategy, or naming that mixes `camelCase` and `snake_case` - Auth screens buil