Build
How Virex turns product intent into a working repo
Every build follows the same predictable path: you describe the product, Virex picks a fitting template, assembles the shell, fills in the pieces that matter for your prompt, and hands you a real downloadable repo. Nothing hidden, nothing disposable.
Build overview
What happens when you build
A build is not a single AI call. It is a sequence of deterministic passes with a few guarded deep passes layered on top where they add real value.
1. Template selection
Virex classifies your prompt and picks the best-fitting template from its registry — webshop, marketplace, dashboard, portfolio, chat, landing, mobile app, and more. Your appType hint speeds this up but is never required.
2. Shell + token substitution
The chosen template is copied into a fresh workspace and your product details (app name, description, colors, brand tokens) are substituted into the right places.
3. Slot composition
The engine fills in template slots — hero sections, product grids, dashboards, navigation, and more — using deterministic content first. Anything it cannot fill deterministically falls back to foundation sampling, then optionally the Deep Engine.
4. Feature expansion
On Premium and Pro, the Deep Engine can add real feature code on top of the template — new routes, API handlers, components, and types — validated before anything is written to disk.
Deep Engine credits
One shared allowance covers builds, edits, and repairs
Your monthly plan comes with a transparent Deep Engine allowance. Every deep pass — building, editing, repairing, augmenting — draws from the same pool. No hidden per-feature fees, no separate buckets to keep track of.
What counts against the allowance
Full builds, structural edits, repairs, deeper feature expansion, and the theme generator. These are the passes that actually need the Deep Engine.
What is always free
Cosmetic edits — color changes, sizing, logo positioning, button rounding, dark/light mode — run on the Standard Engine without touching your allowance. Unlimited on every plan, including Starter.
What happens near your cap
Around 85% you'll see a gentle notice and complex edits automatically downgrade to the lighter lane. Around 95% only smaller edits run. At 100% cosmetic edits still work and the Standard Engine keeps building — the Deep Engine resumes next month.
Why splitting them saves you money
Most builders charge the same for a one-line color tweak as they do for a full page rewrite. Virex classifies every change on the way in and routes cosmetic work to the deterministic Standard Engine — zero credits. This can save 40–60% of a typical month's allowance compared to tools that bill every request to a deep model.
Plain English
Think of the allowance like a monthly meal plan for the heavy kitchen. Salads (color tweaks, resizes, repositions) come from the cold bar and don't count. Full mains (new pages, structural edits, repairs) come from the kitchen and use a portion. You always see how much is left.
When the Deep Engine credits run out for the month
On Premium and Pro your account never gets locked. Once the Deep Engine allowance is at zero, the engine quietly switches to the Standard Engine for the rest of the month. You can keep building, keep editing cosmetically, and keep importing repos — without ever paying overage.
Builds keep working
The full template + slot composer + foundation extraction + library all run without touching the Deep Engine. Premium and Pro have no monthly build ceiling, only a Deep Engine credit pool — when that pool empties, builds stay unlimited on the Standard Engine.
What you give up temporarily
Roughly 10× less depth per build: no LLM-driven feature codegen, no deep edit reasoning, no LLM theme generation, no reference-pattern rewriting. Slots fall back to deterministic fillers, library copy, and component extraction. Builds still ship, they just look closer to a Starter build.
Next month — back to full depth
On the first of the next billing month the Deep Engine credit pool refills automatically. The engine returns to its full capability with zero action required from you. Any builds done during the depleted window stay valid — you can re-run any of them at full depth once credits are back.
Starter is different
Starter is built around the Standard Engine permanently — 0 Deep Engine credits, deterministic + extraction + library only, and a 15 builds/month cap as a soft upsell trigger. If you find yourself wanting deeper edits or more headroom, Premium opens both at once.
Edit / Repair
Continuation on the same repo you already have
Once a repo exists — whether Virex generated it or you imported it — every follow-up change lands as a bounded, guard-railed edit. You keep what works and improve what doesn't, with full history.
Edit tiers
Every edit request is classified into one of four tiers: micro (cosmetic, free), small (simple content changes), medium (new components or sections), large (multi-file or structural). The right tier picks the right lane automatically.
Repair mode
Paste an error message or describe the failure, and Virex focuses the engine on the affected files with stricter guardrails — tighter scope, fewer touched files, safer suggestions.
What the engine will not touch
Package manifests, lockfiles, middleware, environment files, and build config are protected by default. Edits stay inside source directories so nothing critical to the build gets rewritten by mistake.
History and rollback
Every edit is a new version on the same project. If an edit lands in a place you don't like, the previous version stays downloadable. Nothing gets overwritten permanently without your say-so.
Import existing repos
Bring your own codebase into the continuation loop
Virex is not only for net-new generation. If you already have a Next.js or Expo repo, you can import it and use the same edit, repair, and rebuild flow on top of what you've already built.
- Upload a ZIP of the repo or connect a Git source where supported.
- Virex reads the existing structure, respects your current file layout, and treats unknown files as protected by default.
- Edits, repairs, and feature expansions run with the same guardrails as a freshly generated repo.
- You keep the exact same ownership story — download, self-host, version — at every step.
When importing works best
Virex continuation is strongest on Next.js 15/16 and Expo projects that follow standard conventions (app router, file-based routing, conventional config). Heavily customised build pipelines may need light cleanup before the engine can assist confidently.
Images
How Virex fills images in your build
Every generated app ships with placeholder images already wired in so nothing ever looks empty. You can swap them for your own without touching any Virex logic.
The default — curated stock photos
Virex uses picsum.photos with a deterministic seed per app and slot. That means the same app always gets the same images across builds, and different apps get different ones. Zero setup, zero cost, nothing to configure.
Your own — drop them in public/images/
Create a folder called public/images/ in your repo and add any .png / .jpg / .webp / .svg files. Virex detects them automatically on the next build or edit and cycles through them in every slot that needs an image. The stock fallback disappears the moment you add one of your own.
Importing an existing repo with images?
When you import a repo that already has files under public/images/ or public/assets/, Virex recognises them and treats them as the source of truth. New generations on top won't overwrite your own images — they just pull from the folder.
Next
Where to go from here
Pick the docs that match what you're about to do.