Getting started
Regular builder
This path is for users who already know the basics of repos, installs, and deployment but want Virex to give them a stronger structured baseline, clearer rebuild paths, and a better continuation shape after generation.
How to use Virex well
Treat Virex as a serious starting repo and continuation layer, not as a replacement for product judgement or deeper engineering choices.
- Generate the baseline repo around clear product intent.
- Inspect the resulting structure before making deeper custom decisions.
- Use the generated README and setup notes as the first source of truth for project-specific steps.
- Use Edit / Repair when you need continuation without throwing the repo away.
Where env vars, README guidance, and deployment fit
The repo is real from the start, but project-specific setup is still normal.
What to do first
Run the repo locally, read the README, identify any required service keys or URLs, then move into GitHub, deployment, and backend wiring only after you understand the baseline.
Practical expectation
Virex gives you structure, grouping, and continuation shape. It does not eliminate real setup work such as environment variables, auth keys, backend credentials, or billing configuration when the product needs them.
How GitHub, Vercel, Supabase, and Expo fit the workflow
The tools matter most when they are connected to the repo lifecycle instead of explained as isolated products.
Typical continuation flow
- Generate and download the repo from Virex.
- Run it locally first so you understand what the baseline already includes.
- Push it to GitHub when you want remote backup, version history, or collaboration.
- Connect the GitHub repo to Vercel when you want a web project live quickly.
- Add environment variables in Vercel when the project needs real keys or service URLs.
- Use Supabase when the app needs auth, database, storage, or saved user state.
- Use Expo when the project is mobile and you need the native continuation path.
How to read the plan differences
Do not read Standard Engine, Deep Engine, and Deep Engine Plus as skill labels. Read them as different levels of structural depth, breadth, and continuation strength for the repo you are building on.