generate-prototype

To create a standalone prototype, provide the baseline directory, an optional prototype directory, and a design spec. The workflow copies the baseline, applies changes, and runs the new isolated web app on its own port.

Tunnel creation exposes the running isolated prototype externally via an automated end-to-end MCP-guided process. The workflow builds and serves the app, then creates the tunnel to provide an accessible URL for validation.

Canvas registration is used to log and organize isolated prototypes for visual comparison and review. After the prototype is built and exposed via a tunnel, it is registered on the canvas to validate the design concept.

Yes, you need an existing baseline app directory to generate a runnable prototype. The workflow clones the baseline directory and applies your provided design spec to produce an isolated instance with its own tunnel.

Yes, you can validate a design spec without affecting your original web app. The workflow creates an isolated clone of the baseline, running the modified prototype independently on a separate port with its own tunnel.

The best way to compare design changes is generating an isolated prototype from the baseline and registering it on the canvas. This end-to-end MCP-guided process produces a runnable instance for direct visual comparison.