Frequently asked questions

Downloading and installing takes a couple of minutes. The ten questions usually take ten to twenty. Then you build.

No. They are written to be read by Lovable. You read them when you're curious, or when you want to check a decision.

Yes. Lovable skips the questions the code already answers, fills in the current state from what actually exists, and asks only what remains.

No. It doesn't choose your database, hosting, payment provider or frontend patterns. It helps Lovable document the choices you make. It is governance, not an application template.

The work sits with Lovable, not with you. You are involved when a product or architecture choice is genuinely yours, not because a file needs updating.

Not to get started. Once a project moves from experiment to something that has to keep going, version control is strongly recommended, with code and governance documents together.

You fetch it yourself. The framework files are replaced, but your filled-in documents and decisions are extended rather than replaced.

So the same text doesn't fill Lovable's context twice. Pick the language you want your project's documentation to be written in.

Nothing. License terms are decided before the package is published, and will appear on this site once they exist.

No. There is no form and no account. We don't need to know what you're building.

One file is enough. You drop it into the project, Lovable shows a plan, you approve and answer ten questions. The core documents are then created in the project, and the rest grows in when needed. The full package remains available as a ZIP for those who want every file right away.

So that you stay in control. Lovable shows what is about to happen before anything is created, and nothing is written until you have approved the plan. That is the framework's safety gate.