💎 Bonus 1: Extended User Guide + Lovable Prompt
🧠 Bonus 2: Extended Professional Advice (for the best experience)

Below is your complete bonus package, prepared in one text so it can be sent directly to the user or saved as a .txt file.

==================================================
💎 BONUS 1: EXTENDED USER GUIDE + LOVABLE PROMPT
==================================================

Advanced Usage Guide

Lovable should be used primarily as a professional development environment, not as your final production infrastructure.

🧠 Pro Tips
- Each workspace includes approximately 25 credits
- You may receive multiple workspaces depending on your package
- Use credits carefully and focus on development, structure, and export
- Do not keep critical project logic dependent on Lovable-specific infrastructure
- Always think in terms of portability and long-term control

🔄 When Credits Run Out
- Wait for the next cycle
- Or purchase a new workspace/package
- Before credits run out, make sure everything important is already backed up
- Always export your work regularly so no progress is lost

💡 Smart Usage Strategy
Use Lovable strictly as a development tool.
Recommended workflow:
1. Build the project inside Lovable
2. Connect GitHub as early as possible
3. Export all important code externally
4. Keep the project portable
5. Deploy the final system on your own VPS/server

This gives you maximum flexibility, ownership, and safety.

🔗 Recommended GitHub Workflow
- Connect your GitHub account
- Push important milestones regularly
- Reconnect GitHub after each workspace transfer if needed
- If you want to reuse the same repository name, rename your old repository first
- Treat GitHub as the main external backup of your source code

⚠️ Development Best Practices
Avoid using Lovable-specific services if your goal is full portability:
- Supabase
- Edge Functions
- Lovable Cloud

👉 Recommended Approach
- Build inside Lovable
- Export everything externally
- Host backend and frontend on your own VPS/server
- Use your own database and deployment workflow
- Keep your stack standard and transferable

📦 Backup Strategy (Highly Recommended)
To avoid data loss during workspace transfers, keep external backups of everything important.

Recommended backup items:
- Full database export as SQL files
- Full chat history exported to JSON file
- deployment.md
- chat-history.md
- project-notes.md
- environment notes
- architecture notes
- API documentation
- setup instructions

Recommended backup structure:
/backup
  /database
    - database-backup.sql
  /chat
    - chat-history.json
    - chat-history.md
  /docs
    - deployment.md
    - project-notes.md
    - architecture.md
    - api-reference.md

This helps prevent data loss during workspace changes, credit exhaustion, or project migration.

🔁 Workspace Transfer Tips
- Reconnect GitHub
- Restore project files
- Restore documentation
- Restore SQL database backup
- Restore environment variables
- Continue development seamlessly

🧠 Lovable Master Prompt
Use this at the start of every workspace:

You are assisting me as a professional development environment.

Core rules:
- Do NOT use Lovable-specific services (no Supabase, Edge Functions, Lovable Cloud)
- Everything must be exportable and runnable outside Lovable
- Treat Lovable only as a development tool, not hosting

Goal:
Build a fully portable project for VPS/server deployment.

Requirements:
- Clean project structure
- Use standard technologies
- Separate frontend and backend where appropriate
- Keep the system maintainable and scalable
- Use environment variables for all important configuration
- Use portable database architecture
- Make all features production-ready
- Ensure all code can run outside Lovable without dependency on platform-specific infrastructure

Additional requirements:
- Back up all chat history into a JSON file
- Create complete atomic-level developer documentation
- Make full database backups in SQL format
- Convert the entire system for VPS deployment, including backend and frontend
- Provide clear project structure, deployment guide, and backup strategy
- Document all setup, migration, and restoration steps

==================================================
🧠 BONUS 2: EXTENDED PROFESSIONAL ADVICE
==================================================

Professional Advice for Better Experience

If you want the best long-term experience, treat Lovable as a high-speed development layer, not as your permanent infrastructure.

1. Think Like a Professional Team
Build the project as if it will later be handed to another developer, deployed on another server, and maintained without Lovable.

That means:
- clean code
- clean folder structure
- clean documentation
- predictable deployment
- no hidden platform dependency

2. Build Portable by Default
The project should be able to run:
- on your local machine
- on another server
- on a VPS
- after export from Lovable
- without requiring Lovable-specific runtime services

3. Keep Frontend and Backend Ready for VPS
Frontend should be:
- easy to build
- easy to deploy
- configurable with environment variables

Backend should be:
- independent
- documented
- restartable on a VPS
- connected to a standard database
- portable across environments

4. Always Maintain Atomic-Level Documentation
Your documentation should explain every important layer of the project.

Recommended documentation files:
- README.md
- deployment.md
- architecture.md
- backend.md
- frontend.md
- database.md
- api-reference.md
- chat-history.md
- project-notes.md
- migration-guide.md
- restoration-guide.md

Atomic-level documentation means:
- exact setup steps
- exact run commands
- exact environment variables
- exact deployment sequence
- exact backup process
- exact restore process
- exact project structure
- exact service responsibilities

5. Keep Chat History as External Knowledge
Chat history often contains key architectural decisions and implementation logic.
Do not leave it only inside the workspace.

Recommended format:
chat-history.json

Example structure:
[
  {
    "timestamp": "2026-04-03T10:00:00Z",
    "role": "user",
    "message": "Build a portable authentication system"
  },
  {
    "timestamp": "2026-04-03T10:05:00Z",
    "role": "assistant",
    "message": "Created a portable auth architecture using standard backend logic"
  }
]

Also keep:
- chat-history.md for readable notes
- decision logs for major technical choices

6. Database Safety Advice
Never rely only on live database state inside a temporary development environment.

Always keep:
- full SQL dumps
- schema exports
- migration files
- seed files if needed
- restoration instructions

Recommended database backup naming:
- database-schema.sql
- database-full-backup.sql
- migrations/
- seeds/
- restore-db.md

7. VPS-First Mentality
Even while building in Lovable, think as if the final destination is:
- your own VPS
- your own domain
- your own database
- your own deployment control
- your own backup system

That mindset prevents lock-in and makes future migration much easier.

8. Safe Project Structure
Recommended full portable structure:

/project
  /frontend
  /backend
  /database
    /migrations
    /seeds
    /backups
  /docs
    /architecture
    /deployment
    /restoration
    /notes
  /scripts
  /.github

9. What a Fully Prepared Project Should Include
A serious portable project should include:
- frontend source
- backend source
- SQL backups
- environment example files
- developer documentation
- deployment instructions
- restore instructions
- chat history backup
- project notes
- architecture overview
- GitHub repository sync

10. Golden Rule
Lovable is best used as a powerful development assistant.
Your real ownership and stability come from:
- GitHub
- SQL backups
- JSON chat backups
- documentation
- VPS deployment readiness

==================================================
💎 RUSSIAN VERSION FOR THE SAME BONUSES
==================================================

💎 Бонус 1: Расширенное руководство по использованию + подсказка Lovable
🧠 Бонус 2: Расширенные профессиональные советы для наилучшего опыта

Lovable лучше использовать как профессиональную среду разработки, а не как финальную production-инфраструктуру.

🧠 Профессиональные советы
- Каждый workspace обычно включает примерно 25 credits
- В зависимости от пакета вы можете получить несколько workspaces
- Используйте кредиты в первую очередь на разработку, структуру и экспорт
- Не делайте проект зависимым от Lovable-специфичных сервисов
- Всегда стройте проект так, чтобы его можно было перенести и развернуть вне Lovable

🔄 Когда кредиты заканчиваются
- Дождитесь следующего цикла
- Или приобретите новый workspace/package
- Перед окончанием кредитов обязательно экспортируйте и сохраните все важные данные

💡 Умная стратегия использования
Используйте Lovable строго как инструмент разработки.
Рекомендуемый процесс:
1. Разрабатывайте проект внутри Lovable
2. Как можно раньше подключайте GitHub
3. Экспортируйте код наружу
4. Храните проект в переносимом виде
5. Разворачивайте итоговую систему на своем VPS/сервере

🔗 Рекомендуемый GitHub workflow
- Подключите GitHub-аккаунт
- Регулярно сохраняйте важные этапы
- При необходимости переподключайте GitHub после переноса workspace
- Если хотите использовать то же имя репозитория, переименуйте старый репозиторий
- Используйте GitHub как главный внешний бэкап исходного кода

⚠️ Лучшие практики разработки
Избегайте использования Lovable-специфичных сервисов, если ваша цель — полная переносимость:
- Supabase
- Edge Functions
- Lovable Cloud

👉 Рекомендуемый подход
- Создавайте проект внутри Lovable
- Экспортируйте всё наружу
- Разворачивайте backend и frontend на своем VPS/сервере
- Используйте собственную базу данных и собственную схему деплоя
- Делайте стек стандартным и переносимым

📦 Стратегия резервного копирования
Чтобы избежать потери данных при переносе workspace, храните внешние копии всего важного.

Что рекомендуется сохранять:
- Полный экспорт базы данных в SQL
- Полную историю чата в JSON
- deployment.md
- chat-history.md
- project-notes.md
- заметки по окружению
- архитектурную документацию
- документацию по API
- инструкции по установке

Рекомендуемая структура:
/backup
  /database
    - database-backup.sql
  /chat
    - chat-history.json
    - chat-history.md
  /docs
    - deployment.md
    - project-notes.md
    - architecture.md
    - api-reference.md

🔁 Советы по переносу workspace
- Переподключите GitHub
- Восстановите файлы проекта
- Восстановите документацию
- Восстановите SQL-бэкап базы данных
- Восстановите переменные окружения
- Продолжайте разработку без потерь

🧠 Master Prompt для Lovable
Используйте этот prompt в начале каждого workspace:

You are assisting me as a professional development environment.

Core rules:
- Do NOT use Lovable-specific services (no Supabase, Edge Functions, Lovable Cloud)
- Everything must be exportable and runnable outside Lovable
- Treat Lovable only as a development tool, not hosting

Goal:
Build a fully portable project for VPS/server deployment.

Requirements:
- Clean project structure
- Use standard technologies
- Separate frontend and backend where appropriate
- Keep the system maintainable and scalable
- Use environment variables for all important configuration
- Use portable database architecture
- Make all features production-ready
- Ensure all code can run outside Lovable without dependency on platform-specific infrastructure

Additional requirements:
- Back up all chat history into a JSON file
- Create complete atomic-level developer documentation
- Make full database backups in SQL format
- Convert the entire system for VPS deployment, including backend and frontend
- Provide clear project structure, deployment guide, and backup strategy
- Document all setup, migration, and restoration steps