Vibe Coding Prompts

Lovable Feature Update Prompt

Turn a feature idea into a clear, structured instruction ready to paste into Lovable without breaking existing functionality.

✱ By PiSkill TeamFreeClaudeChatGPTGemini

Best for

Founders and no-code or low-code builders using Lovable who want to plan a feature clearly before instructing the AI builder, reducing the risk of breaking existing functionality.

Suitable LLM groups

FrontierReasoning

Prompt

You are acting as a product and prompt engineering assistant who helps me turn a feature idea into a clear, structured instruction for Lovable. You must not ask Lovable to break, remove, or overwrite existing features unless I explicitly say so. Do not add payment logic or billing features unless I explicitly request them.

Here is my information:

Feature idea: {{goal}}
Current app context, such as what the app does today: {{context}}
Who will use this feature: {{audience}}
Any constraints, such as existing design system or tech stack: {{constraints}}
Examples of similar features elsewhere, if any: {{examples}}
What success looks like for this feature: {{desired_output}}

If you need more detail about the current app, the data involved, or how this feature should behave before writing the final instruction, ask me clarifying questions first.

Please produce a structured feature update plan with the following sections:

1. Feature goal: A clear one to two sentence statement of what this feature should accomplish.
2. UI changes: Describe the visual and interface changes needed, screen by screen.
3. Database changes if needed: Describe any new fields, tables, or relationships needed, or state that none are needed.
4. User flow: Describe step by step how a user will interact with this feature from start to finish.
5. Edge cases: List situations that could cause errors or confusion, such as empty states or invalid input.
6. Acceptance criteria: List specific, testable conditions that confirm the feature works as intended.
7. Testing steps: Describe how to manually verify the feature works after it is built.
8. Final Lovable-ready prompt: Write a single, clear, copy-paste-ready instruction combining the above details, written the way you would speak to Lovable directly, explicitly stating that existing features and flows must not be broken.

Do not introduce payment or billing logic unless explicitly requested in the feature idea. Be explicit in the final prompt that existing functionality must remain intact.

How to use

Describe your feature idea and current app context in the placeholders.
Add any constraints like existing design patterns or tech stack.
Run the prompt in your preferred AI tool to generate the structured plan.
Answer clarifying questions if the AI needs more detail about your app.
Copy the final Lovable-ready prompt directly into Lovable.

Example input

Feature idea: allow users to save posts to a personal favorites list. Current app: a content feed app where users can view and comment on posts. Audience: everyday app users. Constraints: existing design uses card-based post layout. Success: users can save and view their favorites from a dedicated tab.

Example output

Feature goal: allow users to save any post to a personal favorites list they can view later.
UI changes: add a save icon to each post card in the feed, add a new Favorites tab in the main navigation showing saved posts in the same card layout.
Database changes if needed: add a favorites table linking user IDs to post IDs with a timestamp.
User flow: user taps the save icon on a post, the icon changes state to show it is saved, the post appears in the Favorites tab, tapping the icon again removes it from favorites.
Edge cases: handle the case where a post is deleted after being favorited, handle an empty Favorites tab for new users with a friendly empty state message, prevent duplicate favorite entries for the same post.
Acceptance criteria: users can save and unsave a post from the feed, saved posts appear correctly in the Favorites tab, removing a favorite updates both the tab and the icon state, existing feed and comment functionality remains unchanged.
Testing steps: save a post and confirm it appears in Favorites, remove it and confirm it disappears, confirm the feed and comments still work normally, test the empty state with a new account.
Final Lovable-ready prompt: Add a favorites feature to the app. Add a save icon to each post card in the feed that toggles saved state. Create a Favorites tab in the main navigation showing all saved posts using the existing card layout. Store favorites linked to user ID and post ID. Handle empty state in the Favorites tab with a friendly message for new users. Do not modify or break the existing feed, comment, or navigation functionality.

Customization tips

— Add specific field names or data structures if you already know your database schema.
— Mention any design system component names so the UI changes match your existing style.
— Ask for a simplified version of the final prompt if the feature is very small.
— Request the plan to be split into phases for larger, more complex features.

FAQ

No, it explicitly avoids adding payment or billing logic unless you request it in your feature idea.

Rate this prompt

How helpful was this?

Comments

Sam O.

Used this to ship 6 SEO articles in a week — the FAQ block alone is worth it.

Ines P.

Wish it had a Spanish voice preset, but overall very solid.

Related skills coming soon — browse all skills.

Related articles coming soon — visit the Learn hub.