Getting started
Advanced / developer
This path is for users who already think in repos, diffs, deployment, and continuation workflows. Virex should feel like a structured repo accelerator, not a locked environment or a replacement for your own engineering judgement.
How to read Virex as a developer
The value is in structured generation and controlled continuation, not in pretending deeper engineering workflow disappears.
- Use Virex for baseline generation, structured rebuilds, and safer continuation direction.
- Inspect the repo directly in the editor, git workflow, CI path, and hosting stack you already prefer.
- Treat README and setup notes as the project-specific bridge between generated baseline and live infrastructure.
- Keep hosting, runtime, backend, and infra decisions in your own hands where needed.
Ownership, hosting, and extension freedom
The repo is yours. That is the important difference.
What that gives you
You can self-host, move to your own infrastructure, integrate the repo into an existing workflow, or continue with a preferred editor and git host instead of being trapped inside one interface.
How Virex fits a technical workflow
The intended use is straightforward: generate the structured baseline, review it like any other repo, extend it where you want, and keep the long-term asset value instead of treating the output as disposable conversation state.
Where to read next
Use the practical docs where they add leverage rather than rereading beginner-level material.