Lovable prompt library

We are building a simple V1 MVP for a business decision-support app.

Goal:
Help a business user collect information, review it, classify it, and recommend the next action.

Constraints:
- Keep this as V1
- Do not overbuild
- Do not add login, email automation, CRM integration, or advanced analytics
- Prioritize the core user flow
- Ask before adding complex features
- Do not implement anything before planning first

First, create a simple implementation plan with:
1. Problem summary
2. Target user
3. Pages needed
4. Data needed
5. User flow
6. Decision logic
7. V1 build phases
8. What to avoid building

Do not build yet.

Now build only the V1 app shell.

Include:
1. Home page
2. Intake form page
3. Result / recommendation page
4. Simple dashboard page

Do not add login.
Do not add external integrations.
Do not add advanced analytics.
Do not add email.
Do not add team permissions.

Keep it clean, simple, and demo-friendly.

Now build the intake form.

The form should collect:
- request title
- requester name
- request type
- description
- urgency
- business impact
- supporting notes

Add simple validation:
- request title is required
- description is required
- urgency is required

Do not add AI yet.
Do not expand beyond V1.

Now add simple decision logic.

The app should classify each request based on:
- urgency
- business impact
- completeness of information
- risk level

The result page should show:
- score
- category
- explanation
- recommended next action

Keep the logic simple and easy to explain.

We want to add a simple AI decision-support feature to our V1 app.

Do not build yet.

Help us define:
1. What user input the AI needs
2. What business criteria the AI should compare against
3. What score or category the AI should return
4. What explanation the AI should show
5. What recommended next step the AI should provide
6. What should remain human-reviewed

Keep this simple and suitable for a hackathon MVP.

We are staying focused on V1 for the hackathon.

Do not add new features unless they are required for the core MVP flow.

Review your suggestion and classify it as:
1. Required for V1
2. Nice-to-have for V2
3. Not needed for this hackathon

Only implement V1 items that directly support the final demo path.

Review the app for demo readiness.

Check:
- broken user flow
- missing buttons
- confusing screens
- missing validation
- unnecessary features
- bad mobile layout
- likely demo risks

Give us a prioritized fix list before changing anything.