Squid turns a prompt and optional visual references into a multi-file React project. The product keeps the generated files, preview, follow-up history, quality evidence, and export path connected so you can evaluate the result as code—not only as an image.
Code ownership
Understand checkpoints, generated files, and portable exports.
Read guideQuality checks
Use diagnostics and verification evidence without confusing them with production acceptance.
Read guideCredits and models
Choose a model with the visible estimate and understand how successful work is recorded.
Read guideProject lifecycle
- A project starts from a text prompt, screenshot, or website reference.
- Squid selects the requested model and generates a structured React application.
- Generated files are normalized and checked before the result is saved.
- The preview and file view expose the current checkpoint.
- Follow-up requests create new project history instead of erasing the earlier result.
- Export packages the accepted source for work outside Squid.
Use the right evidence
The preview answers “what does this version look and feel like?” The file view answers “what was generated?” Quality information answers “which known structural checks passed or need attention?” A clean external build answers “can this bundle run in a fresh environment?”
No single one replaces the others.