// the find
guillermoscript/lms-front
AI Powered LMS app for the future of learning
A multi-tenant SaaS LMS built on Next.js 16, Supabase, and Stripe Connect, with AI tutoring features via OpenAI/Gemini APIs. It targets indie developers or small ed-tech teams who want a starting point for a school-as-a-subdomain platform. The feature set is genuinely broad: course creation, student enrollment, payments, i18n, and AI chat.
- The local dev setup is well thought out—Supabase migrations with seed data, a db:reset script, and documented subdomain testing via lvh.me means you can actually run the full multi-tenant flow locally without fighting config.
- Documentation is unusually thorough for 18 stars: separate docs for auth flows, DB schema, monetization/Stripe Connect, and a CLAUDE.md architecture reference that doubles as onboarding for AI agents and human developers alike.
- Stripe Connect integration for educator payouts is non-trivial and often missing from open-source LMS projects—having it stubbed in reduces the scariest part of a real deployment.
- The .agents/skills directory shows the project is being developed with AI coding assistants in mind and includes structured prompt references for Next.js, Supabase, and security review patterns, which is practical if you're using Cursor or Claude to extend it.
- 18 stars and 12 forks with a last-push date of mid-2026 suggests very little community validation—there's no evidence of anyone running this in production, so you'd be the first to hit the edge cases.
- The .agents/skills tree is massive (hundreds of files) and ships as part of the repo rather than a dev dependency or submodule, bloating the clone and making it unclear what is application code versus AI scaffolding noise.
- No unit or integration tests visible in the tree—only Playwright E2E. For a multi-tenant billing app, missing server-side tests around RLS policies, Stripe webhook handling, and tenant isolation is a real gap before you'd trust it with money.
- Cutting straight to Next.js 16 and React 19 (both pre-release/RC at time of writing) means dependency churn is likely and some ecosystem packages won't be compatible, which will bite anyone trying to add common libraries.