Three ways in, and what happens in the first minute.
There are three ways into a project. Which one you pick decides what Flexi reads first; everything after that is the same project.
Paste the address of the site you have, on the home page or on the new-project page. FlexOS reads it before you sign in and shows a picture of the site as it is beside a first sketch of what Flexi would build. When you say yes, the project starts with that read as the first message of its first chat, so Flexi already knows your business, your pages and what is missing.
Say what slows your business down, in a sentence. The new-project page asks one of three questions: what's slowing your business down, what you hate most about your job, what keeps you from getting home on time for dinner. Your answer becomes the first message of the first chat. A complaint is a fine first message: Flexi's job is to turn it into the site, the pages and the agents that fix it.
Bring a zip of what you already have: a Lovable export, a FlutterFlow export, any website. Your files go into the repo in one commit, as they are, with installed packages, git history and build output left out. Keys found in a .env go into the Vault, never the repo. The folder with the website in it becomes the one that gets built.
A zip with no website in it puts nothing online. A FlutterFlow export lands in the repo's
app/folder beside the site, off the website, and ships from Settings › Deployment › Mobile app.
your-name.flexos.site.