In plain English
This skill helps Lovable follow a safe process for final app quality review so non-coders can keep building without guessing the next technical step.
The problem
Review user journeys, auth, database access, RLS, secrets, payments, mobile, states, SEO, and launch readiness.
When to use it
- You are preparing a demo
- You are sending the app to a client
- You are onboarding first users
- You are launching a paid product
What this skill checks
- Identify app purpose and journeys
- Audit auth/data/security/payments
- Review states/mobile/SEO
- Score readiness and prioritise fixes
What to avoid
- Unrelated redesigns
- Broad rewrites
- Database changes without a reason
- Hidden security risks
- Changing working behaviour without explaining the impact
Skill instructions
Copy this into your Lovable workspace as a saved skill.
SKILL.md
# /founder-qa-audit
Use this skill when final quality, security, and launch readiness review in a Lovable project.
Before editing:
1. Explain the current problem in plain English.
2. Identify the affected feature, route, component, table, function, or integration.
3. Review recent changes where relevant.
4. Produce a short fix or implementation plan before making changes.
What to check:
- Identify app purpose and journeys.
- Audit auth/data/security/payments.
- Review states/mobile/SEO.
- Score readiness and prioritise fixes.
Rules:
- Do not redesign unrelated parts of the app.
- Do not rewrite unrelated components.
- Do not change database schema unless clearly required.
- Do not expose private data or secrets.
- Prefer the smallest safe change.
Implementation:
1. Apply the smallest safe change first.
2. Keep each change narrow and testable.
3. Preserve existing working behaviour.
4. Add or recommend test scenarios.
Final output:
- Problem summary.
- Root cause or best diagnosis.
- Changes applied or recommended.
- Files, routes, tables, functions, or integrations affected.
- Risk level.
- Test checklist.
- Next recommended step.
Example prompt
Prompt
Use /founder-qa-audit to review this issue. Do not make changes yet. First explain the diagnosis, risks, and safest next step.Expected output
Plain-English diagnosis Risk level Files, routes, tables, or integrations affected Safe fix plan Test checklist Next recommended step