Focused app files
Polymai separates markup, styling, behavior, data, assets, SQL, and server functions instead of mixing the app into one large generated file.
Developers
Polymai runs inside VS Code and treats AI app building as a staged development workflow: shape the brief, plan the surface, generate a structured app, preview the result, validate setup, and keep future changes scoped.
Structured Output
Small files, clear ownership, reviewable changes.
Polymai separates markup, styling, behavior, data, assets, SQL, and server functions instead of mixing the app into one large generated file.
The generated project can include a registry that records expected files, load order, capabilities, and responsibility boundaries for future updates.
Polymai can prepare the brief, rules, plan, and task context so Codex implements against the same app contract instead of a loose prompt.
Update work is grounded in the existing structure, app map, project memory, and allowed file surface so changes can stay narrow.
Runtime Services
Polymai can plan the files and boundaries needed for data, auth, storage, server-only work, payments, email, publishing, and readiness checks.
Schema, row-level security, storage setup, and frontend-safe runtime config can be generated as app-scoped artifacts.
Email, AI jobs, scraping/fetch tasks, scheduled work, checkout sessions, billing portals, and webhooks belong behind functions.
Frontend code gets publishable runtime values. Secret keys, checkout creation, portal sessions, and fulfillment stay server-side.
Provider keys, webhook signing secrets, service roles, tokens, and database credentials are kept in VS Code or provider environments.
Local preview, screenshot review, smoke tests, and provisioning status make the next action visible before the work is treated as done.
Setup Model
Polymai runs inside VS Code. It writes real project files, keeps the app contract visible, runs previews and checks, and coordinates Codex/provider handoff without hiding the code in a closed platform.