Get useful understanding before the first explanation meeting.
Move through an unfamiliar product from the level of behavior and rules, then go down to implementation only when you need it.
On a project you were invited to, the description of the product is already written and waiting. You see which areas the product is made of, how much lives in each, and which areas lean on which — then open the code only when a question actually needs it. Nothing has to be set up by you to start reading.
Accept the invite and open the project — you do not need to build anything yourself.
On the repository page, read what the product turned out to be made of and open the drawing of its areas; click into one to go inside it.
Ask the starting questions offered — they are written from this product's own area names, so the first question is not a blank field.
Read "What changed in the product" to catch up on what has moved since the model was first read.
Practise before your first day on a published model: Supabase Studio is a real 459,000-line product, open to anyone.
Somebody has to have built the model first, and that costs credits: a person with viewer access can open and ask, but cannot start a build. What you get is a description of behaviour read out of the code — it never contains reasons, decisions, or history that only live in people's heads or in a wiki. There is no import from your existing documentation.
See it on a real product.
Three models are published in full and open without an account. Ask one of them the question this page is about.