Audit the codebase to find structural issues
Runs a comprehensive audit to identify misplaced files, coupling, and complexity without changing code.
When to use it
Your app works but has grown complex and you suspect structural issues.
Why it is worth it
Identifying structural problems early prevents larger refactoring work later.
The prompt
Perform a comprehensive audit of my note-taking app codebase and report without changing any code. Identify files or components that are misplaced or not well organized. Check separation of concerns between data handling, UI, and state management. Highlight overly complex code or sections that are tightly coupled. List findings as ordered steps from most critical to optional.
Replace note-taking app with the name of your own app.
What you get
You have a prioritized list of structural improvements to implement one at a time.
From docs.lovable.dev/prompting/prompting-debugging