How to work with existing lovable projects

[karandexhs]

The current documentation covers how to implement the tool when starting from a new PRD, but there are no clear instructions on how to integrate it into an already existing Lovable.Dev project. I have ongoing projects and need guidance on how to implement the tool without starting from scratch.

Expected Behavior

Clear steps for integrating the tool into an existing project.

Any necessary modifications or migrations outlined.

Examples or best practices for handling legacy data/configurations.

Possible Implementation

A section in the documentation specifically for existing projects.

A migration guide or checklist.

Code snippets for adapting current project structures.

Would love to see support for this! Let me know if I can help clarify anything.

[joedanz]

Hi @karandexhs - thanks for the feedback! The most likely implementation will be with a Chrome Plugin. We are working to smooth out integration, as right now it would be very manual cut and paste. We are launching MCP soon - as are they - which should facilitate everything.

We do have some ideas, and we’ll be working to make integration with Lovable super-simple.

[karandex]

Thanks for your reply. I was asking not for a Lovable integration. After importing code to cursor I want to use the tool to continue development.

[eyaltoledano]

Thanks for reporting this. Our documentation is going to get a lot of love very soon. Focused on major release first

[jivko-chobanov]

I have a big codebase I have built over the years without AI (on Phoenix Web Framework). Now I want to start using Task Master on it with Cursor.

In the PRD.txt file - shall I explain my whole project or focus mostly on the current feature I am beginning to implement? When it is finished - shall I replace the PRD.txt with a new file for the next feature I want? (I think it will be overwhelming for me and for the AI to explain all my project features, maybe just the current one is enough.)

[knoxgraeme]

@jivko-chobanov Might be good to move this to a discussion outside of the loveable request but:

The best thing to do is to take the prd template, chat w/ your preferred agent starting by giving a brief overview of the current state of your project (can be high level) and then outlining your new feature. Once that is ironed out, simply ask it to generate a PRD for the new features from the example_prd template, with a focus on integrating it into the existing codebase. It should give a mix of current context w/ new feature development.

I've found gemini 2.5 pro to be the best at this. For additional features you want to add in the future, follow the same process but use --append when parsing your PRD so it adds the new tasks to the bottom of your existing list.

One area that can help keep things smooth is ensuring your cursor rules are dialed so the agent has guardrails when working on new tasks in your existing codebase.

[BradKML]

Cross-reference to other existing/legacy codebases and how it could be improved #133