Choose a build type, give it a name and a primary action, then test the actual browser artifact before you export it.
A small build earns its place when its primary action works now, not just in a description.
The source generates one of three small HTML templates locally: website, app or game. It inserts a project title and primary action into a fixed template and loads it in the preview iframe. No model is called and no site is deployed. The default website button replaces its label with a thanks message. The app button changes a status line, while the game button increments a local score. These are the actual template interactions, not a complete product backend. The game score starts at zero and the native button adds one each time. After one, two and three clicks it is one, two and three. These rectangles use one hundred pixels per click on a common scale. Building again replaces the iframe document and resets its transient interactions. Selecting a mode only changes selected state and saves it; it does not rebuild the current preview until the original build action runs. Thus the selected mode and current generated HTML can differ temporarily. Build trims both title and action and requires them to be nonempty. A successful build saves the complete state and generated HTML in browser local storage. Export downloads that existing HTML; editing fields or selecting another mode does not replace previously built code automatically. Reload rebuilds from the saved mode and fields. Reset creates and saves a fresh working website baseline, rather than leaving storage empty. Template text escaping does not prove arbitrary inputs form a robust production application.