Lovable Prompts for DevOps Engineers
DevOps engineers need help writing and reviewing infrastructure as code, CI/CD pipeline configs, shell scripts and monitoring rules, and with diagnosing failed deploys from logs. These Lovable prompts start from that: fill in your situation once and reuse it. The worked example below is a debugging task, one of the most common for devops engineers.
I'm a devops engineer and need help with [task, e.g. ci/cd pipelines]. What I have: - [the material involved: code, draft, notes or data] What a good result looks like: - [the outcome and its format] Ask me one clarifying question if something important is missing, then give the result. About my work - Platform and tools: [e.g. AWS, Terraform 1.8, GitHub Actions, Kubernetes 1.30] - Environment this affects: [e.g. staging only, production with 3 regions] - Constraints: [e.g. no downtime, must stay within the current IAM roles] Context - App and screens involved: [framework, page or component names] - Leave unchanged: [features, routes or styling that must not change]
How to use this prompt
- 1
Open Lovable
Paste the prompt into Lovable's chat for your project.
- 2
Give it context
Describe the user, the screen and the data involved. If the project uses Supabase, say which table or auth flow is affected.
- 3
Review and iterate
Test the change in the preview, then send one follow-up per problem.
Working in Lovable
- •Lovable generates full-stack code, so state what must not change (routes, data model, styling).
- •Describe behavior in user terms ("when a signed-out user clicks Save") rather than only in code terms.
- •Ask for a summary of changed files so you can review them in GitHub if the project is synced.
Example task: Debugging
What you give it
Symptom: add_tag returns tags from earlier calls. Calling add_tag("a") then add_tag("b") gives ["a", "b"] on the second call instead of ["b"].
Environment: Python 3.11, local script.
def add_tag(tag, tags=[]):
tags.append(tag)
return tags
What changed: nothing, it has always done this.What a good answer looks like (shortened)
1. Mutable default argument (very likely). The list [] is created once, when the function is defined, and every call without a tags argument reuses that same list.
Check: print(id(tags)) inside the function. If the id is the same on every call, this is the cause.
2. A caller is passing the same list in each time (less likely, since the calls you showed pass only one argument).
Check: search for calls to add_tag that pass a second argument.
Run check 1 first. If confirmed, the fix is:
def add_tag(tag, tags=None):
if tags is None:
tags = []
tags.append(tag)
return tagsTips for better results
- •Always say which environment the change targets and ask for a plan or dry-run command before the apply step. It keeps a test idea from turning into a production change.
- •Describe the user, the screen and the data involved. If the project uses Supabase, say which table or auth flow is affected.
- •Check this before you use the output: check IAM permissions, open ports, secrets handling and destructive commands in any generated config or script before it touches a real environment.
Check before you use it: Check IAM permissions, open ports, secrets handling and destructive commands in any generated config or script before it touches a real environment.
Get the free prompt pack
Our best coding prompts in one Markdown file, delivered by email. The templates here stay free either way — the pack just saves you the copying.
Variations
Task
Debugging: Replace the first line with: Help me debug a problem. I want to find the cause, not just patch the symptom.
Intermittent bug
Add this line to Symptom: It only happens [e.g. 1 in 20 requests, under load, after midnight UTC]. Focus on timing, concurrency and caching causes.
Second task
Change the task line to: [Infrastructure as code].
Save it as a Retext snippet
Retext is a free text expander for Mac. Save this prompt once, then type ;devops-lovable in any app (ChatGPT, Claude, your editor, a browser tab) and the full prompt is pasted in.
- Click Add to Retext. The prompt installs as a snippet with the trigger ;devops-lovable.
- Change the trigger in Retext if you prefer a different one.
- Type the trigger wherever you want the prompt, then fill in the brackets.
Frequently asked questions
Is it safe to use AI for Terraform or Kubernetes configs?
It is useful for drafts and reviews, but configs can contain subtle mistakes like overly broad permissions. Review every change with a plan or diff and test in a non-production environment first.
Can I use a coding prompt like this in a no-code-style builder?
Yes. Lovable writes real code, so a prompt that names inputs, expected behavior and constraints gets better results than a one-line request.
How do I review what Lovable changed?
Ask it to list the files it touched and why. If your project is connected to GitHub, review the diff there.
How do I reuse this prompt without copying it every time?
Click Add to Retext to save it as a snippet. Then type ;devops-lovable in any Mac app, including your AI tool, and the full prompt is pasted in.
Related Templates
Get the free prompt pack
Our best coding prompts in one Markdown file, delivered by email. The templates here stay free either way — the pack just saves you the copying.