Analyze Existing Project

# Analyze Existing Project

## Recipe

- Category: Planning
- Recommended mode: Plan Mode
- Risk level: Low
- Estimated scope: Medium

## Purpose

Build an evidence-based understanding of an existing Lovable project before planning or changing it. The result should identify the product, architecture, data flow, conventions, risks, and unknowns without modifying the project.

## Use When

- joining or revisiting an existing project
- preparing a feature, refactor, migration, integration, or security review
- Project Knowledge may be incomplete or outdated
- the relevant implementation area is unclear
- previous changes caused regressions or architectural inconsistency

## Do Not Use When

- the task is already small, isolated, and fully understood
- implementation has already been approved and only execution remains
- the user asked for a targeted debugging or security recipe instead

## Required Context

Provide when known:

- `[ANALYSIS_SCOPE]`: Whole project or a specific area
- `[PROJECT_GOAL]`: What the product is intended to achieve
- `[FOCUS_AREAS]`: Features, routes, flows, integrations, or concerns to prioritize
- `[KNOWN_CONCERNS]`: Suspected risks, inconsistencies, or failures
- `[EXCLUDED_AREAS]`: Areas that must not be inspected or discussed
- `[OUTPUT_DEPTH]`: Concise, standard, or deep

## Prompt