What this screen does
Generate Application turns your locked specification into working code through four tabs: Entities (the domain diagram), Database (the schema), Models (Eloquent models and relations), and Laravel (the generated codebase itself). The first time you open it, the entity diagram is seeded automatically from the specification.
Typical workflow
- Start on Entities — review and adjust the seeded diagram; it is the source the other tabs derive from.
- Move through Database and Models, regenerating each from the previous step and adjusting where needed.
- On Laravel, pick your generation options, generate the codebase, browse the files, and Download Archive.
- Save your work explicitly — the Save button (or Ctrl+S) writes the current state; the pill next to it shows unsaved changes. Nothing autosaves.
- Use the version picker to restore an earlier saved state, and the stack switcher to change between Laravel + Blade and Laravel + Vue output.
Examples & tips
- Saving is deliberate: experiment freely, and only save states you would want to come back to. Leaving with unsaved changes triggers a warning.
- Re-seed from spec regenerates the entity diagram from the current specification — useful after a spec revision, but it replaces the diagram, so save the old state first.
- Code generation bills credits per generated file batch; the Q&A affordance works here too if you want to ask why something was generated a particular way.