Export

The Export tab is where the connected workspace becomes a project you can hold: a generated file tree to review, starter code to fill it, three ways out — a .zip, a GitHub push, a report — and the conflicts to resolve before any of them.

Scaffolding

Scaffolding translates the live plan into a complete generated file tree: Structure's routes and components, Backend's endpoints, Data's entities and types, the Domain notes, shortcut bindings, and the theme. The tree is per-target — a Next.js App Router project on Web, the same routes inside a Tauri host on Desktop, an Expo Router app on Mobile, an Ink CLI on Terminal, a Manifest V3 extension on Extension — so what you preview is what your platform actually builds.

Conflict indicators flag the parts of the plan that cannot map cleanly to one output path, each with a severity and a suggested fix. Warnings export anyway; blocked conflicts are worth resolving first, because the preview, the download, and the push all read the same merged file set and cannot disagree.

The scaffold also derives a build order — stores first, then components, guards, layouts, and pages, each file after the files it imports — which is the order a human or an AI coding agent should implement the tree in.

Generate code

Beneath the file tree, Generate code turns the skeletons into working starter code, walking the build order one file at a time at 1 AI credit per file — sequentially, so each file is written knowing the exports of every file already generated above it. Runs are batched and resumable: files that already have code are skipped, so a second run continues where the first stopped. Generated files replace their skeletons in the preview, the download, and the GitHub push alike. The generate initial code guide covers what informs each file and how runs behave in detail.

Download or push

Download .zip packages the complete scaffold — generated code included — entirely in the browser; nothing passes through a server.

Push to GitHub commits the same file set to a repository and branch you choose, authenticated with a personal access token you paste (needing only repo scope). The token is kept for the browser tab only — never stored in the database — and the push is deliberately conservative: it adds and updates files but never deletes, and it never force-pushes, so a branch that moved underneath you is a conflict to review, not an overwrite.

Report

Report turns the workspace into a shareable planning document: the Domain context, routes, data model, endpoints, types, shortcuts, roles, features, the Security policy, and Traceability links. Choose which sections to include, pick a report theme — including the project's own generated theme, so the document is styled like the product it describes — and preview before exporting. The same report is what a share link renders in its report view, so stakeholders can read it without an account.