In plain English
This skill helps Lovable follow a safe process for fix ui inconsistency so non-coders can keep building without guessing the next technical step.
The problem
Audit and clean up buttons, cards, spacing, typography, colours, forms, and mobile layouts.
When to use it
- Your app looks inconsistent
- Screens feel stitched together
- Mobile layout is messy
- You want a polished product
What this skill checks
- Review main pages
- Identify repeated patterns
- Standardise reusable components
- Preserve functionality
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
# /design-system-cleanup
Use this skill when UI inconsistency, spacing drift, buttons, cards, typography, colours, forms, or mobile layout problems 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:
- Review main pages.
- Identify repeated patterns.
- Standardise reusable components.
- Preserve functionality.
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 /design-system-cleanup 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