Grok Instructions for making a Lovable Prompt
Here is the full wording of the instructions I use for making a Lovable prompt for a project I was working on for the Australian Political space.
Business
Here is the full wording of the instructions I use for making a Lovable prompt for a project I was working on for the Australian Political space.
Just note that you will need to tweak this for your own use case.
MAIN Prompt Template
Prompt #[XX]: [Name of Feature or Function]
Objective:
[Describe the goal of this prompt in one or two sentences, clearly stating the intended feature or functionality.]
Implementation Instructions:
Build exactly what is described, no more and no less.
Break tasks into clear, actionable bullet points.
Make certain that all designs are completely responsive at every breakpoint, adopting a mobile-first strategy. Apply contemporary UI/UX best practices to define how components should adjust for varying screen sizes, utilising ShadCN and Tailwind’s standard breakpoints. Steer clear of custom breakpoints unless specifically requested.
Always make things responsive on all breakpoints, with a focus on mobile first.
Use modern UI/UX best practices for determining how breakpoints should change the components.
Use shadcn and tailwind built in breakpoints instead of anything custom, unless the user prompts for custom breakpoints directly.
List required database fields and triggers.
Include any role-based visibility or user permissions.
Avoid vague instructions, placeholder components, or unspecified functionality.
---
Strict Compliance Rule:
You must implement this prompt exactly as written. No improvising, no skipping steps, no combining with other prompts. Do not add placeholder code or design unless explicitly allowed in the instructions.
---
AUDIT Prompt Template
Audit Prompt #[XXa]: Verification for [Name of Feature or Function]
Purpose:
Use this checklist to confirm that Prompt #[XX] was implemented correctly. Every item must be verified before proceeding to the next prompt.
Verification Checklist:
[ ] Was the feature built exactly as described in Prompt #[XX]?
[ ] Are all specified database fields present and fully functional?
[ ] Does the UI match the layout and styling instructions provided?
[ ] Are all buttons, links, and actions fully functional as specified?
[ ] Is the feature only visible or accessible to the intended users or roles?
[ ] Is the feature complete, with no placeholder logic, visuals, or unfinished components?
[ ] Does the feature operate without bugs or unintended side effects?
[ ] Did this implementation break any existing functionality?
Additional Notes:
If any checklist item fails, document the issue and revise the implementation before re-running the audit.
Do not proceed to the next prompt until all checklist items are confirmed.
********
Usage Guidelines
Project Initialization:
Begin with an Overview Prompt that outlines the project’s goals and product vision.
Follow with a Strict Compliance Prompt to enforce precise adherence to instructions.
Prompt Execution:
Write and implement each MAIN Prompt for a single feature or function.
Use the provided template to ensure clarity and specificity.
Audit Process:
After implementing the MAIN Prompt, run the corresponding AUDIT Prompt.
Verify each checklist item to ensure full compliance.
Iteration:
Address any audit failures by revising the implementation and re-running the audit.
Prompt #[XX]: [Name of Feature or Function]
Objective:
[Describe the goal of this prompt in one or two sentences, clearly stating the intended feature or functionality.]
Implementation Instructions:
Build exactly what is described, no more and no less.
Break tasks into clear, actionable bullet points.
Make certain that all designs are completely responsive at every breakpoint, adopting a mobile-first strategy. Apply contemporary UI/UX best practices to define how components should adjust for varying screen sizes, utilising ShadCN and Tailwind’s standard breakpoints. Steer clear of custom breakpoints unless specifically requested.
Always make things responsive on all breakpoints, with a focus on mobile first.
Use modern UI/UX best practices for determining how breakpoints should change the components.
Use shadcn and tailwind built in breakpoints instead of anything custom, unless the user prompts for custom breakpoints directly.
List required database fields and triggers.
Include any role-based visibility or user permissions.
Avoid vague instructions, placeholder components, or unspecified functionality.
---
Strict Compliance Rule:
You must implement this prompt exactly as written. No improvising, no skipping steps, no combining with other prompts. Do not add placeholder code or design unless explicitly allowed in the instructions.
---
AUDIT Prompt Template
Audit Prompt #[XXa]: Verification for [Name of Feature or Function]
Purpose:
Use this checklist to confirm that Prompt #[XX] was implemented correctly. Every item must be verified before proceeding to the next prompt.
Verification Checklist:
[ ] Was the feature built exactly as described in Prompt #[XX]?
[ ] Are all specified database fields present and fully functional?
[ ] Does the UI match the layout and styling instructions provided?
[ ] Are all buttons, links, and actions fully functional as specified?
[ ] Is the feature only visible or accessible to the intended users or roles?
[ ] Is the feature complete, with no placeholder logic, visuals, or unfinished components?
[ ] Does the feature operate without bugs or unintended side effects?
[ ] Did this implementation break any existing functionality?
Additional Notes:
If any checklist item fails, document the issue and revise the implementation before re-running the audit.
Do not proceed to the next prompt until all checklist items are confirmed.
********
Usage Guidelines
Project Initialization:
Begin with an Overview Prompt that outlines the project’s goals and product vision.
Follow with a Strict Compliance Prompt to enforce precise adherence to instructions.
Prompt Execution:
Write and implement each MAIN Prompt for a single feature or function.
Use the provided template to ensure clarity and specificity.
Audit Process:
After implementing the MAIN Prompt, run the corresponding AUDIT Prompt.
Verify each checklist item to ensure full compliance.
Iteration:
Address any audit failures by revising the implementation and re-running the audit.
Only move to the next MAIN Prompt once the audit passes fully.
Members Discussion