Total revamp of the prompting page, much more structured and less slop #119
Conversation
Summary of ChangesHello @danielandreasson, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a comprehensive rewrite of the prompting guide, transforming it from a verbose and less structured document into a practical, phase-based playbook. The update aims to provide users with clearer, more actionable strategies for effective prompting within Lovable, directly integrating insights from an external "Mastering Lovable" guide to enhance the quality and consistency of UI generation. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request is a total revamp of the prompting guide, replacing the previous lengthy and verbose content with a much more structured, concise, and actionable guide. The new version is a significant improvement, broken down into clear phases with practical tips and examples that will be very helpful for users. I've included a couple of minor suggestions to enhance formatting consistency. Overall, this is an excellent rewrite.
|
|
||
| <Info> | ||
| _Please refrain from modifying the homepage, focus only on the dashboard component._ | ||
| Even a simple three‑step sketch — Hero → Features → CTA — can make your prompts 10× more effective. |
There was a problem hiding this comment.
For consistency with the rest of the document, consider removing the spaces around the em-dashes (—). All other em-dashes in this file are used without surrounding spaces.
Even a simple three‑step sketch—Hero → Features → CTA—can make your prompts 10× more effective.
| <Info> | ||
| _Connect the form to Stripe (test mode) for payments. On success, redirect to /thank-you._ | ||
| </Info> | ||
| > Tip: You don't need a working backend during design—but shaping your UI as if it's already there is how you future‑proof your layout. |
There was a problem hiding this comment.
This blockquote is used for a tip, which is inconsistent with other blockquotes in the file that are used for direct quotes. For better consistency and to visually distinguish this as a tip, consider using the <Info> component, similar to its use on line 41.
<Info>
**Tip:** You don't need a working backend during design—but shaping your UI as if it's already there is how you future‑proof your layout.
</Info>
prompting/prompting-one.mdx
Outdated
| ## Phase 4: Iterate and Ship | ||
|
|
||
| You might not prompt these platforms in natural language the same way, but designing an automation **still benefits from clear AI instructions**. | ||
| ### 11. Build with Supabase in mind |
There was a problem hiding this comment.
@danielandreasson this whole section should talk about Cloud now though?
|
|
||
| To help you make the most out of Lovable, we compiled a list of prompting strategies and approaches. Some of these were collected from our team's experience, and others were shared with us by our community members. Since Lovable relies on large language models (LLMs), effective prompting strategies can significantly improve its efficiency and accuracy. | ||
| Use this practical playbook to get consistent, high‑quality results in Lovable. The content below mirrors the public guide at [mastering-lovable.lovable.app](https://mastering-lovable.lovable.app/). | ||
|
|
There was a problem hiding this comment.
I don't think we need the image or link to the guide if we copied it. @danielandreasson
There was a problem hiding this comment.
And this is great, my plan was to run this guide by Lazar and see if he had any more ideas and then turn it into a "basics of prompting" guide that would be a section on the landing page.
Do you think that's a good next step? @danielandreasson
There was a problem hiding this comment.
Will remove the link etc, I do like the image though. Nice "entrence" to this otherwise quite long doc
There was a problem hiding this comment.
it's an image of nothing :D Maybe add something prompt related at least :)
prompting/prompting-one.mdx
Outdated
| - Utilize developer tools: open the browser DevTools console to inspect an element or debug a JavaScript error in real time. Once you identify the fix, you can either implement it directly or confirm via a prompt. | ||
| **This video will further help you master prompt engineering inside Lovable.** | ||
| <iframe width="100%" height="315" src="https://www.youtube.com/embed/IqWfKj4mUIo?si=aHVQNRgD8xF7EW06" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen /> | ||
|
|
There was a problem hiding this comment.
@danielandreasson do we want to keep this 1h video? also feels out of place here under visuals?
Removed all the made up info that was there prior. Had 0 value and was very wordy. Replaced it by rewriting Felix's prompting guide (which can be in found in the PR at the start) to a Mintlify version