AI Engine
Validation
What is checked before anything renders — and what happens to input that does not pass.
The schema
Every specification is parsed against the schema before it is saved or rendered. A section of an unknown type, a missing required field or a page with no sections cannot get through. Limits are part of it: 12 pages, 20 sections a page, and a length for every piece of text.
Repairing rather than rejecting
Some input is corrected instead of failing the whole build:
- Text that is too long is cut at the last word boundary within its limit.
- Links are kept only if they are
https://,http://,mailto:,tel:, a path or an in-page anchor. Anything else — includingjavascript:anddata:— becomes#before it can be stored. - In-page links written as /#section are rewritten to #section, so they work wherever the site is served.
Beyond the schema
- Audits score the result on structure, conversion, copy, SEO, accessibility and mobile, and say what to fix — see AI Agents.
- App specifications are also checked for screens nothing navigates to and navigation to screens that do not exist.
- 3D games are started in a real browser and played through before you see them.
- Sandbox builds run in a frame on an opaque origin, so even a faulty program cannot reach your account.
Developers can run the same validation with the
validate_spec MCP tool before submitting a specification of their own.