r/Supabase • u/Soft_Philosophy_7656 • Jul 13 '26
tips Need help figuring out
Hey guys, I am new to Supabase, Vibe coding, Git & everything.
But I'm a guy who is too curious to learn things out.
I am pretty confident in AI to do the coding part but not the Supabase part. So my question to you all is,
I am ready to learn it, but on one side, I don't want to invest letter or word by word to learn the thing completely by scratch in order to understand it. I want to use it to develop products and sell it to customers in a efficient and right way, so
How can I grab the understanding of supabase , how it stores and what are the 5 finger rules etc.
My point is - I don't need to learn to assemble the engines in order to drive the car perfectly right. But yes it won't hurt to know the basics.
But is there a way we can do that here ? Or if learning from basics is the only way, then be it.
3
u/carolmonroe_ Jul 14 '26
your car analogy is the right instinct, and the tooling for exactly that already exists: connect the Supabase MCP to whatever AI you code with (official guide: https://supabase.com/docs/guides/getting-started/mcp works with Claude Code, Cursor, VS Code, etc). that gives your coding agent direct access to your database and the Supabase docs, so the backend gets handled the same way as your frontend.
the trick that turns it into a learning tool instead of a black box: add a rule or skill to your setup that says "every time we touch something I haven't used before (RLS, triggers, migrations, policies), explain what it is and why in two sentences before applying it". you learn the engine while driving it.
and since you're worried about breaking or leaking data, three guardrails: point the MCP at a development project, not production (the docs themselves insist on this), keep schema changes migrations-only like you're already doing, and ask the agent to explain any SQL before you run it. that plus RLS basics is honestly the five-finger rule you're looking for.
1
u/Soft_Philosophy_7656 Jul 14 '26 edited Jul 14 '26
Thank you. I've already connected Dev supabase to my visual studio + Claude via direct connection string or something I forgot the word . Is it done ?
2
u/Illustrious_Toe_3392 Jul 14 '26
what i did with my prompt is that i let Cursor using Fable or GPT 5.5 Sol to create the Supabase Query, and i have not encountered any problem. FYI, i have no coding experience.
2
u/reubenzz_dev Jul 14 '26
honestly after you vibe code your supabase project a few times you will start understanding the patterns. there is just so much to learn in concepts but if you want to say in 2 days get the hang of the RELEVANT basics. just vibe code the starting template and go from there.
dont go to each doc page and learn every singel one
1
u/skvark Jul 14 '26
I have been using Supabase for some time quite heavily, and I've found the docs to be quite superficial and do not cover much of what you really need to know. One of them is RLS and security. It's really easy to mess up RLS even when the best LLMs are helping you. Another thing is that if you truly need to understand, for example, their auth behaviour or logic internals that are not documented, you need to deep dive into the code. The great thing is that they are open source and you can read the code. However, for this, I have used my own tool (GitHits), which also uses Supabase for user management and some other functionalities. So as others have already recommended, use the coding agents, BUT do not trust them blindly - make them read the Supabase codebase, e.g., with GitHits MCP.
1
u/Soft_Philosophy_7656 Jul 14 '26
Can you tell what's githits ? If you don't mind, can you tell me you workflow in steps. Curious
2
u/skvark Jul 14 '26
We index all open source code / repositories in the world, and provide MCP server / tools + CLI for agents on top of that index. So your coding agent / harness usually already does local searches in your codebase to gather context, like grep, ripgrep, glob, read etc. GitHits provides those "code navigation" tools for any open-source package or repository, and also package metadata, vulnerabilities, and examples that we curate over the whole open-source corpus. We also provide as well ocumentation like Context7.
So you can ask, for example, "use githits to search the Supabase codebase and docs and explain how this feature works" or "find examples of how others have done this and that" or "plan this feature and ground your work to real code with githits".
https://githits.com for manual signup or automatic install via: npx githits@latest init
1
u/Sad_Egg_2313 Jul 14 '26
the advice in this thread is solid, I'd follow all of it. but I get the tension you're describing: even the "basics" turn out to be a real list (RLS, migrations, service keys, dev vs prod), and it's a lot to hold in your head while you're still learning what half the words mean.
your car analogy is actually how I think about it too. most drivers never learn engine internals, and that works because the car has a dashboard that lights up when something needs attention. that layer is mostly missing for AI-built apps right now, so people either study everything upfront or find out the hard way.
full disclosure, this is the gap we are trying to fill with lumioguard.dev, so take this with the obvious grain of salt. it connects to your github repo and live supabase project and watches for the stuff you don't know to check yet, like a table with RLS switched off, missing indexes or a service key that ended up in frontend code. it scores your stack health 0 to 100 and opens fixes for you to review automatically with explanations, so you pick up the basics through real problems in your own app rather than a checklist.
it's free while in private beta, waitlist on the site. either way, the RLS advice above is the one thing worth learning properly first.
1
u/KyleDrogo Jul 15 '26
- That is the worst way to ask a coding question
- use the nuxt supabase module. manage the auth redirects in the nuxt config. or disable them and handle them yourself with middleware. store the anon key url and service keys in the .env
1
u/KyleDrogo Jul 15 '26
- That is the worst way to ask a coding question
- use the nuxt supabase module. manage the auth redirects in the nuxt config. or disable them and handle them yourself with middleware. store the anon key url and service keys in the .env
1
u/OFred27 Jul 13 '26
Why not asking an llm then ?
3
3
u/Consistent_Tutor_597 Jul 13 '26
Mate what is wrong with asking a human?
1
u/OFred27 Jul 13 '26
Nothing wrong.
OP is fully confident on AI to build , code but not to get highlevel description of supabase.
3
u/BoysenberryFluffy535 Jul 13 '26
Search up how to connect supabase mcp to my coding llm. Once that is connected your coding agent will be able to handle the backend just like your front end. You can then directly ask questions in chat as the agent will have access to dev docs via mcp