doc(project): project brief docs added

.kilocode/rules/memory-bank-instructions.md

@@ -0,0 +1,167 @@
+# Memory Bank
+
+I am an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task - this is not optional. The memory bank files are located in `.kilocode/rules/memory-bank` folder.
+
+When I start a task, I will include `[Memory Bank: Active]` at the beginning of my response if I successfully read the memory bank files, or `[Memory Bank: Missing]` if the folder doesn't exist or is empty. If memory bank is missing, I will warn the user about potential issues and suggest initialization.
+
+## Memory Bank Structure
+
+The Memory Bank consists of core files and optional context files, all in Markdown format.
+
+### Core Files (Required)
+1. `brief.md`
+   This file is created and maintained manually by the developer. Don't edit this file directly but suggest to user to update it if it can be improved.
+   - Foundation document that shapes all other files
+   - Created at project start if it doesn't exist
+   - Defines core requirements and goals
+   - Source of truth for project scope
+
+2. `product.md`
+   - Why this project exists
+   - Problems it solves
+   - How it should work
+   - User experience goals
+
+3. `context.md`
+   This file should be short and factual, not creative or speculative.
+   - Current work focus
+   - Recent changes
+   - Next steps
+
+4. `architecture.md`
+   - System architecture
+   - Source Code paths
+   - Key technical decisions
+   - Design patterns in use
+   - Component relationships
+   - Critical implementation paths
+
+5. `tech.md`
+   - Technologies used
+   - Development setup
+   - Technical constraints
+   - Dependencies
+   - Tool usage patterns
+
+### Additional Files
+Create additional files/folders within memory-bank/ when they help organize:
+- `tasks.md` - Documentation of repetitive tasks and their workflows
+- Complex feature documentation
+- Integration specifications
+- API documentation
+- Testing strategies
+- Deployment procedures
+
+## Core workflows
+
+### Memory Bank Initialization
+
+The initialization step is CRITICALLY IMPORTANT and must be done with extreme thoroughness as it defines all future effectiveness of the Memory Bank. This is the foundation upon which all future interactions will be built.
+
+When user requests initialization of the memory bank (command `initialize memory bank`), I'll perform an exhaustive analysis of the project, including:
+- All source code files and their relationships
+- Configuration files and build system setup
+- Project structure and organization patterns
+- Documentation and comments
+- Dependencies and external integrations
+- Testing frameworks and patterns
+
+I must be extremely thorough during initialization, spending extra time and effort to build a comprehensive understanding of the project. A high-quality initialization will dramatically improve all future interactions, while a rushed or incomplete initialization will permanently limit my effectiveness.
+
+After initialization, I will ask the user to read through the memory bank files and verify product description, used technologies and other information. I should provide a summary of what I've understood about the project to help the user verify the accuracy of the memory bank files. I should encourage the user to correct any misunderstandings or add missing information, as this will significantly improve future interactions.
+
+### Memory Bank Update
+
+Memory Bank updates occur when:
+1. Discovering new project patterns
+2. After implementing significant changes
+3. When user explicitly requests with the phrase **update memory bank** (MUST review ALL files)
+4. When context needs clarification
+
+If I notice significant changes that should be preserved but the user hasn't explicitly requested an update, I should suggest: "Would you like me to update the memory bank to reflect these changes?"
+
+To execute Memory Bank update, I will:
+
+1. Review ALL project files
+2. Document current state
+3. Document Insights & Patterns
+4. If requested with additional context (e.g., "update memory bank using information from @/Makefile"), focus special attention on that source
+
+Note: When triggered by **update memory bank**, I MUST review every memory bank file, even if some don't require updates. Focus particularly on context.md as it tracks current state.
+
+### Add Task
+
+When user completes a repetitive task (like adding support for a new model version) and wants to document it for future reference, they can request: **add task** or **store this as a task**.
+
+This workflow is designed for repetitive tasks that follow similar patterns and require editing the same files. Examples include:
+- Adding support for new AI model versions
+- Implementing new API endpoints following established patterns
+- Adding new features that follow existing architecture
+
+Tasks are stored in the file `tasks.md` in the memory bank folder. The file is optional and can be empty. The file can store many tasks. 
+
+To execute Add Task workflow:
+
+1. Create or update `tasks.md` in the memory bank folder
+2. Document the task with:
+   - Task name and description
+   - Files that need to be modified
+   - Step-by-step workflow followed
+   - Important considerations or gotchas
+   - Example of the completed implementation
+3. Include any context that was discovered during task execution but wasn't previously documented
+
+Example task entry:
+```markdown
+## Add New Model Support
+**Last performed:** [date]
+**Files to modify:**
+- `/providers/gemini.md` - Add model to documentation
+- `/src/providers/gemini-config.ts` - Add model configuration
+- `/src/constants/models.ts` - Add to model list
+- `/tests/providers/gemini.test.ts` - Add test cases
+
+**Steps:**
+1. Add model configuration with proper token limits
+2. Update documentation with model capabilities
+3. Add to constants file for UI display
+4. Write tests for new model configuration
+
+**Important notes:**
+- Check Google's documentation for exact token limits
+- Ensure backward compatibility with existing configurations
+- Test with actual API calls before committing
+```
+
+### Regular Task Execution
+
+In the beginning of EVERY task I MUST read ALL memory bank files - this is not optional. 
+
+The memory bank files are located in `.kilocode/rules/memory-bank` folder. If the folder doesn't exist or is empty, I will warn user about potential issues with the memory bank. I will include `[Memory Bank: Active]` at the beginning of my response if I successfully read the memory bank files, or `[Memory Bank: Missing]` if the folder doesn't exist or is empty. If memory bank is missing, I will warn the user about potential issues and suggest initialization. I should briefly summarize my understanding of the project to confirm alignment with the user's expectations, like:
+
+"[Memory Bank: Active] I understand we're building a React inventory system with barcode scanning. Currently implementing the scanner component that needs to work with the backend API."
+
+When starting a task that matches a documented task in `tasks.md`, I should mention this and follow the documented workflow to ensure no steps are missed.
+
+If the task was repetitive and might be needed again, I should suggest: "Would you like me to add this task to the memory bank for future reference?"
+
+In the end of the task, when it seems to be completed, I will update `context.md` accordingly. If the change seems significant, I will suggest to the user: "Would you like me to update memory bank to reflect these changes?" I will not suggest updates for minor changes.
+
+## Context Window Management
+
+When the context window fills up during an extended session:
+1. I should suggest updating the memory bank to preserve the current state
+2. Recommend starting a fresh conversation/task
+3. In the new conversation, I will automatically load the memory bank files to maintain continuity
+
+## Technical Implementation
+
+Memory Bank is built on Kilo Code's Custom Rules feature, with files stored as standard markdown documents that both the user and I can access.
+
+## Important Notes
+
+REMEMBER: After every memory reset, I begin completely fresh. The Memory Bank is my only link to previous work. It must be maintained with precision and clarity, as my effectiveness depends entirely on its accuracy.
+
+If I detect inconsistencies between memory bank files, I should prioritize brief.md and note any discrepancies to the user.
+
+IMPORTANT: I MUST read ALL memory bank files at the start of EVERY task - this is not optional. The memory bank files are located in `.kilocode/rules/memory-bank` folder.

.kilocode/rules/memory-bank/architecture.md

@@ -0,0 +1,374 @@
+# System Architecture
+
+## Project Structure
+
+### Core Directory (`lib/core/`)
+Central infrastructure and shared components:
+- **Dependency Injection**: GetIt-based service locator in `locator_service.dart`
+- **Routing**: GoRouter implementation in `app_router.dart` with deep linking
+- **Theme**: Material theme with Mulish font family in `theme/theme_helper.dart`
+- **Networking**: Dio HTTP client with token interceptor
+- **WebSockets**: Pusher Channels for real-time communication
+- **State Management**: Flutter BLoC/Cubit pattern
+
+### Features Directory (`lib/features/`)
+Feature-based modular architecture with 35+ feature modules:
+
+**Core Features:**
+- `auth/` - Authentication (email/password, OAuth)
+- `feed/` - Content discovery feed
+- `diary/` - Food diary tracking
+- `chat/` - Real-time messaging
+- `consultations/` - Consultation management
+- `profile/` - User profiles and settings
+
+**Content Creation:**
+- `create_recipe/` - Recipe creation
+- `create_diet/` - Diet plan creation
+- `create_plan/` - Nutrition plan creation
+- `blog_post_create/` - Blog post creation
+
+**User Management:**
+- `settings/` - User preferences
+- `user_details/` - User information management
+- `menu/` - App navigation menu
+- `bottom_navigation_bar/` - Main navigation
+
+**Consultant Features:**
+- `consultant/` - Consultant verification
+- `consultant_rating/` - Rating system
+- `finances_and_consultations_archive/` - Financial tracking
+
+**Supporting Features:**
+- `notifications/` - Push notifications
+- `glossary/` - Nutrition glossary
+- `calendar/` - Calendar integration
+- `support/` - Customer support
+- `welcome/` - Onboarding
+- `update_screen/` - App update management
+
+## Architectural Patterns
+
+### Clean Architecture Layers
+
+Each feature follows a layered structure:
+
+```
+feature/
+├── models/          # Data models (freezed + json_serializable)
+├── services/        # API services (Retrofit)
+├── repositories/    # Data repositories
+├── presentation/    # UI layer
+│   ├── pages/       # Screen widgets
+│   ├── widgets/     # Feature-specific widgets
+│   └── bloc/        # State management (Cubit)
+└── entities/        # Domain entities
+```
+
+### Dependency Injection
+
+**Registration Structure** (`lib/core/di/`):
+- `app_config_registration.dart` - App configuration
+- `external_registrations.dart` - External dependencies (Dio, etc.)
+- `service_registrations.dart` - API services
+- `repository_registrations.dart` - Data repositories
+- `cubit_registrations.dart` - State management
+
+**Service Lifecycle:**
+- Singleton: Services, Repositories (most common)
+- Factory: Cubits that need fresh instances
+- Lazy Singleton: WebSocket manager, core services
+
+### State Management Pattern
+
+**BLoC/Cubit Implementation:**
+- Global state: Registered in `AppConfig.globalBlocProviders`
+- Feature state: Created per screen/feature
+- State classes: Freezed unions for type-safe states
+
+**Global Cubits:**
+- `NewMessagesCubit` - Message notifications
+- `NotificationsCubit` - Push notifications
+- `FeedCubit` - Feed content
+- `ProfileAvatarCubit` - User profile
+- `ChatsCubit` - Chat rooms
+- `ViewsCubit` - Content view tracking
+- `InternetConnectionCubit` - Network status
+
+## Data Flow
+
+### API Integration
+
+**Base Setup:**
+- Base URL: Configurable via environment (prod/dev)
+- HTTP Client: Dio with interceptors
+- API Services: Retrofit for type-safe endpoints
+- Authentication: Bearer token in headers
+
+**Interceptors:**
+1. `TokenInterceptor` - Adds auth token, handles 401 errors
+2. `PhoneVerifyErrorInterceptor` - Handles phone verification errors
+
+### Real-time Communication
+
+**WebSocket Architecture:**
+- Library: `dart_pusher_channels`
+- Manager: `WsManager` (singleton)
+- Connection: Authenticated via backend endpoint
+
+**Channels:**
+1. Private Notifications: `App\Events\BroadcastNotificationCreated`
+2. Private Messages: `App\Events\ChatMessageUpdated`
+3. Direct Chat: Room-specific message updates
+4. Client Typing: Real-time typing indicators
+
+**Socket ID Storage:**
+- Persisted via SharedPreferences
+- Used for authentication and channel subscription
+
+### Authentication Flow
+
+**Methods:**
+1. Email/Password - Traditional credentials
+2. OAuth Providers:
+   - VK ID (Russian social network)
+   - Yandex ID
+   - OK (Odnoklassniki)
+   - Mail.ru
+
+**Token Management:**
+- Storage: SharedPreferences via `TokenStorage`
+- Refresh: Automatic on 401 response
+- Logout: Token removal + WebSocket cleanup
+
+**Post-Authentication:**
+1. WebSocket initialization
+2. Profile loading
+3. Chat room loading
+4. Notification loading
+5. Firebase push token registration
+
+## Navigation Architecture
+
+### GoRouter Setup
+
+**Route Structure:**
+- Shell routes for persistent bottom navigation
+- Named routes for easy navigation
+- Deep linking support for content (recipe/blog_post/plan/diet)
+
+**Route Groups:**
+- `AuthRoutes` - Login, registration, password reset
+- `MainNavigationRoutes` - Shell route with bottom nav
+- `ContentRoutes` - Content viewing screens
+- `SettingsRoutes` - User settings
+- `OtherRoutes` - Miscellaneous screens
+
+**Deep Linking Pattern:**
+```
+/content/{type}/{identifier}
+- /content/recipe/{slug}
+- /content/blog_post/{id}
+- /content/plan/{slug}
+- /content/diet/{slug}
+```
+
+### Bottom Navigation
+
+**Main Sections:**
+1. My Profile - User profile and content
+2. Feed - Content discovery
+3. Diary - Food tracking
+4. Consultations - Consultation management
+5. Chat - Messaging
+6. Notifications - Notification center
+7. Menu - Settings and more
+
+**Implementation:**
+- `BottomNavigationBarWidget` wraps content
+- No transition animations for tab switches
+- WebSocket initialization on feed screen
+
+## Data Persistence
+
+### Storage Solutions
+
+**SharedPreferences:**
+- Authentication token
+- Socket ID
+- User preferences
+
+**Cached Network Images:**
+- Library: `cached_network_image`
+- Automatic caching of user avatars, content images
+
+**Firebase:**
+- Push notification tokens
+- Remote configuration
+- Analytics events
+
+## Critical Implementation Details
+
+### Content View Tracking
+
+**Pattern:**
+- `ViewsCubit` handles visibility detection
+- `VisibilityDetector` widget tracks on-screen time
+- Views sent to backend when 50%+ visible for 2+ seconds
+- Debounced to prevent excessive API calls
+
+**Tracked Content:**
+- Blog posts
+- Recipes
+- Diets
+- Nutrition plans
+
+### Image Handling
+
+**Upload Flow:**
+1. `ImagePicker` for selection
+2. `FlutterImageCompress` for compression
+3. MultiPart form data upload via Dio
+4. Preview via `CachedNetworkImage`
+
+**Supported Formats:**
+- User photos (profile, diary)
+- Content images (recipes, diets, plans)
+- Chat attachments
+
+### Search Implementation
+
+**Debounced Search:**
+- Library: `easy_debounce`
+- Delay: 500ms
+- Min query length: 3 characters
+- Applied to: Feed, Recipes, Diets, Plans, Consultants
+
+**Tag-based Filtering:**
+- Recipe tags for filtering
+- Modal bottom sheet UI
+- Persistent selection across sessions
+
+### Pagination Pattern
+
+**Implementation:**
+- Page-based pagination
+- Scroll detection for next page load
+- Loading state during fetch
+- Meta data tracking (current page, last page)
+
+**Example (FeedCubit):**
+```dart
+currentPage = 1
+lastPage = meta.lastPage
+loadNextPage() when currentPage < lastPage
+```
+
+## Error Handling
+
+### Network Errors
+
+**401 Unauthorized:**
+- Auto logout
+- Token removal
+- Navigate to auth screen
+
+**Connection Errors:**
+- `InternetConnectionCubit` monitors status
+- Retry mechanisms in repositories
+- User-friendly error messages
+
+### State Error Handling
+
+**Pattern:**
+```dart
+sealed class State {
+  const State.loading();
+  const State.loaded({required data});
+  const State.error({required String errorMessage});
+}
+```
+
+**UI Response:**
+- Loading: Show loaders/skeletons
+- Error: Show `DataErrorWidget` with retry
+- Empty: Show empty state messages
+
+## Performance Optimizations
+
+### Lazy Loading
+- Lazy singleton services
+- On-demand cubit creation
+- Deferred widget loading
+
+### Image Optimization
+- Compression before upload
+- Cached network images
+- Thumbnail generation
+
+### WebSocket Management
+- Connection reuse
+- Automatic reconnection
+- Proper cleanup on logout
+
+### List Rendering
+- Pagination for large lists
+- ListView.builder for efficiency
+- Visibility detection for tracking
+
+## Platform-Specific Features
+
+### Android
+- Huawei HMS support for Huawei devices
+- Google FCM for push notifications
+- ProGuard rules for release builds
+- QR code scanning via camera
+
+### iOS
+- APNs for push notifications
+- Deep linking configuration
+- App Store compliance
+
+### Firebase Integration
+- Separate configs for Android/iOS
+- Environment-based configuration
+- Push notification handling
+- Analytics tracking
+
+## Security Considerations
+
+### Authentication
+- Bearer token authentication
+- Secure token storage
+- Automatic session management
+- OAuth 2.0 for social login
+
+### Data Protection
+- HTTPS only communication
+- Token encryption in storage
+- Secure WebSocket connections
+- Privacy policy compliance
+
+## Key Files Reference
+
+**Entry Point:**
+- `lib/main.dart` - App initialization
+
+**Core Infrastructure:**
+- `lib/core/app_initializer.dart` - Startup sequence
+- `lib/core/locator_service.dart` - DI container
+- `lib/core/app_config.dart` - App configuration
+- `lib/core/app_router.dart` - Routing setup
+
+**WebSocket:**
+- `lib/core/websockets/ws_manager.dart` - Connection management
+- `lib/core/websockets/ws_service.dart` - API service
+
+**Authentication:**
+- `lib/features/auth/sdk/social_auth_facade.dart` - Social auth
+- `lib/core/token_storage.dart` - Token persistence
+- `lib/core/interceptors/token_interceptor.dart` - Auth interceptor
+
+**Environment:**
+- `lib/core/env_config.dart` - Environment variables
+- `.env` - Environment file (not in repo)

.kilocode/rules/memory-bank/brief.md

@@ -0,0 +1,35 @@
+# Project Brief
+
+## Project Name
+Eatvio - Nutrition & Diet Management Application
+
+## Project Description
+A comprehensive mobile application connecting users with nutrition consultants, providing diet planning tools, recipes, food diary tracking, and professional consultation services.
+
+## Core Features
+- **Blog Posts**: Educational nutrition content and articles
+- **Nutrition Consultation**: Professional consultation services with certified nutritionists
+- **Recipes**: User-generated and professional recipes with nutritional information
+- **Diets**: Structured diet plans with daily schedules
+- **Nutrition Plans**: Long-term nutrition planning and tracking
+
+## Target Audience
+- Primary: Russian-speaking users interested in nutrition and healthy eating
+- Secondary: Certified nutrition consultants offering professional services
+- Market: Russian Federation and Russian-speaking countries
+
+## Platform
+- Mobile: iOS and Android (including Huawei devices)
+- Language: Russian (ru)
+- Current Version: 1.3.0+79
+
+## Business Model
+- Paid consultations with nutritionists
+- Content marketplace for premium diets and plans
+- Subscription-based features for consultants
+
+## Key Success Metrics
+- User engagement with food diary
+- Consultation bookings and completion rates
+- Content creation by consultants
+- User retention and progress tracking

.kilocode/rules/memory-bank/context.md

@@ -0,0 +1,29 @@
+# Current Context
+
+## Project Status
+Memory Bank initialized on 2025-10-16. This is a mature Flutter application (v1.3.0+79) currently in production.
+
+## Recent Activity
+- Memory Bank initialization completed
+- All core files documented
+- Architecture and technology stack catalogued
+
+## Current Focus
+Ready for development tasks. No active work in progress.
+
+## Known Issues
+None documented at initialization.
+
+## Next Steps
+Awaiting user direction for:
+- Feature development
+- Bug fixes
+- Architecture improvements
+- Performance optimizations
+
+## Important Notes
+- Primary language: Russian (ru)
+- Target market: Russian users
+- Multi-platform: Android (including Huawei) and iOS
+- Environment: Uses `.env` file for configuration (not in repository)
+- Build system: Requires code generation for models/services

.kilocode/rules/memory-bank/product.md

@@ -0,0 +1,73 @@
+# Product Overview
+
+## Purpose
+Eatvio is a comprehensive nutrition and diet management mobile application that connects users with nutrition consultants, provides diet planning tools, recipes, and personal food diary tracking.
+
+## Core Problems It Solves
+
+### For Regular Users:
+1. **Diet Management**: Track daily food intake with detailed nutritional information
+2. **Meal Planning**: Access to recipes and structured diet plans
+3. **Professional Guidance**: Connect with certified nutrition consultants
+4. **Progress Tracking**: Monitor weight, body measurements, and dietary habits
+5. **Knowledge Access**: Learn about nutrition through blog posts and glossary
+
+### For Nutrition Consultants:
+1. **Client Management**: Communicate with clients via integrated chat
+2. **Content Creation**: Create and publish diets, meal plans, recipes, and blog posts
+3. **Consultation Services**: Offer paid nutrition consultation services
+4. **Income Tracking**: Monitor earnings and client purchases
+5. **Professional Presence**: Build profile and gain subscribers
+
+## How It Works
+
+### User Journey:
+1. **Authentication**: Sign up via email/password or social networks (VK, Yandex, OK, Mail.ru)
+2. **Feed Exploration**: Browse recipes, diets, nutrition plans, blog posts, and consultants
+3. **Content Interaction**: Like, bookmark, comment on content
+4. **Diary Tracking**: Log daily meals with photos and nutritional data
+5. **Consultations**: Book and pay for nutrition consultant services
+6. **Real-time Chat**: Communicate with consultants through integrated messaging
+7. **Progress Monitoring**: Track weight and body measurements over time
+
+### Consultant Journey:
+1. **Become Consultant**: Apply and get verified as nutrition consultant
+2. **Content Creation**: Publish professional diets, meal plans, recipes
+3. **Client Interaction**: Respond to consultations and provide guidance
+4. **Diary Review**: Review client food diaries and provide feedback
+5. **Earnings Management**: Track income from consultations and content
+
+## User Experience Goals
+
+### Seamless Navigation:
+- Bottom navigation bar for main sections (Profile, Feed, Diary, Consultations, Chat)
+- Tab-based feed filtering (Blog posts, Recipes, Diets, Plans, Consultants)
+- Deep linking support for direct content access
+
+### Real-time Engagement:
+- WebSocket-powered chat for instant messaging
+- Push notifications for messages and updates
+- Live content updates without app restart
+
+### Professional Interface:
+- Clean, modern UI with Mulish font family
+- Intuitive search and filtering across all content types
+- Visual progress tracking with charts and gauges
+
+### Content Discovery:
+- Tag-based recipe filtering
+- Search functionality across all content types
+- Personalized feed based on user interests
+
+### Offline Capability:
+- Token persistence for seamless re-authentication
+- Cached content for better performance
+- Queue system for offline actions
+
+## Key Differentiators
+
+1. **Integrated Platform**: Combines diet tracking, content, and professional consultations
+2. **Social Features**: Follow consultants, like/bookmark content, engage with community
+3. **Professional Tools**: Full toolkit for consultants to manage practice
+4. **Russian Market Focus**: Optimized for Russian users with local payment and auth integrations
+5. **Multi-platform Support**: Works on Android (including Huawei) and iOS

.kilocode/rules/memory-bank/tech.md

@@ -0,0 +1,152 @@
+# Technology Stack
+
+## Core Framework
+- **Flutter**: SDK 3.8.0+
+- **Dart**: Language version >=3.8.0 <4.0.0
+- **Version**: 1.3.0+79 (build 79)
+
+## State Management
+- **flutter_bloc**: ^9.1.1 - BLoC pattern implementation
+- **equatable**: ^2.0.7 - Value equality for state objects
+
+## Data Management
+- **freezed**: ^3.2.0 - Immutable data classes
+- **freezed_annotation**: ^3.1.0 - Code generation annotations
+- **json_annotation**: ^4.9.0 - JSON serialization
+- **json_serializable**: ^6.10.0 - JSON code generation
+
+## Networking
+- **dio**: ^5.9.0 - HTTP client
+- **retrofit**: ^4.7.1 - Type-safe REST client
+- **retrofit_generator**: ^10.0.2 - Retrofit code generation
+- **http**: ^1.5.0 - Additional HTTP support
+- **http_parser**: ^4.1.2 - HTTP parsing utilities
+
+## Real-time Communication
+- **dart_pusher_channels**: ^1.2.3 - WebSocket support via Pusher
+- **connectivity_plus**: ^6.1.5 - Network connectivity monitoring
+
+## Navigation & Routing
+- **go_router**: ^16.1.0 - Declarative routing
+- Deep linking support for content
+
+## UI Components
+- **cached_network_image**: ^3.4.1 - Image caching
+- **flutter_svg**: ^2.2.0 - SVG rendering
+- **google_fonts**: ^6.3.0 - Mulish font family
+- **carousel_slider_plus**: ^7.1.1 - Carousel widgets
+- **photo_view**: ^0.15.0 - Image viewer
+- **dismissible_page**: ^1.0.2 - Swipe to dismiss
+- **badges**: ^3.1.2 - Notification badges
+- **lottie**: ^3.3.1 - Animation support
+- **flutter_portal**: ^1.1.4 - Overlay widgets
+- **dotted_border**: ^3.1.0 - Dotted borders
+- **flutter_rating_bar**: ^4.0.1 - Rating widgets
+
+## Forms & Input
+- **flutter_form_builder**: ^10.2.0 - Form management
+- **validators**: ^3.0.0 - Input validation
+- **flutter_typeahead**: ^5.2.0 - Autocomplete
+- **keyboard_dismisser**: ^3.0.0 - Keyboard management
+- **flutter_keyboard_visibility**: ^6.0.0 - Keyboard state
+- **mask_text_input_formatter**: ^2.9.0 - Input masking
+
+## Media & Files
+- **image_picker**: ^1.2.0 - Image selection
+- **flutter_image_compress**: ^2.4.0 - Image compression
+- **image**: ^4.5.4 - Image manipulation
+- **file_picker**: ^10.3.1 - File selection
+- **audioplayers**: ^6.5.0 - Audio playback
+- **qr_code_scanner_plus**: ^2.0.10+1 - QR code scanning
+
+## Data Visualization
+- **syncfusion_flutter_charts**: ^30.2.5 - Chart widgets
+- **syncfusion_flutter_gauges**: ^30.2.5 - Gauge widgets
+- **table_calendar**: ^3.2.0 - Calendar widget
+
+## Storage & Persistence
+- **shared_preferences**: ^2.5.3 - Local key-value storage
+- **path_provider**: ^2.1.5 - File system paths
+- **path**: ^1.9.1 - Path manipulation
+
+## Firebase
+- **firebase_core**: ^4.0.0 - Firebase initialization
+- **firebase_messaging**: ^16.0.0 - Push notifications
+
+## Analytics & Monitoring
+- **sentry_flutter**: ^9.6.0 - Error tracking
+- **appmetrica_plugin**: ^3.3.0 - Analytics (Russian market)
+
+## Authentication
+- **vk_id**: ^1.0.3 - VK social login
+- **flutter_login_yandex**: ^0.0.5 - Yandex ID login
+- OAuth support for OK and Mail.ru
+
+## Utilities
+- **url_launcher**: ^6.3.2 - URL handling
+- **easy_debounce**: ^2.0.3 - Debouncing
+- **share_plus**: ^11.1.0 - Content sharing
+- **flutter_html**: ^3.0.0 - HTML rendering
+- **webview_flutter**: ^4.13.0 - WebView
+- **intl**: ^0.20.2 - Internationalization
+- **collection**: ^1.19.1 - Collection utilities
+- **uuid**: ^4.5.1 - UUID generation
+- **visibility_detector**: ^0.4.0+2 - Visibility tracking
+- **fluttertoast**: ^8.2.12 - Toast messages
+- **version**: ^3.0.2 - Version management
+- **package_info_plus**: ^8.3.1 - Package info
+- **device_info_plus**: ^11.5.0 - Device information
+- **permission_handler**: ^12.0.1 - Permissions
+
+## Platform-Specific
+
+### Android
+- Huawei HMS Push (6.12.0.300)
+- Huawei Analytics (6.12.0.300)
+- Google Play Services
+- ProGuard for code obfuscation
+- NDK version 27.0.12077973
+- Compile SDK: Flutter default
+- Min SDK: Flutter default
+- Target SDK: Flutter default
+
+### iOS
+- APNs for push notifications
+- Deep linking support
+
+## Development Tools
+- **build_runner**: ^2.7.0 - Code generation
+- **flutter_native_splash**: ^2.4.6 - Splash screen
+- **flutter_lints**: ^6.0.0 - Linting
+- **mockito**: ^5.5.0 - Mocking for tests
+- **flutter_test**: SDK - Testing framework
+- **integration_test**: SDK - Integration testing
+- **flutter_dotenv**: ^5.2.1 - Environment variables
+
+## Localization
+- **flutter_localizations**: SDK - Localization
+- **flutter_intl**: Enabled - Internationalization
+- Primary language: Russian (ru)
+
+## Build Configuration
+- **Environment**: Production/Development/Test modes
+- **Build types**: Debug, Release, Profile
+- **Code generation**: Freezed, JSON, Retrofit
+- **Obfuscation**: ProGuard (Android release)
+- **Resource optimization**: Shrink resources enabled
+
+## API Integration Patterns
+- RESTful API via Retrofit
+- Bearer token authentication
+- Interceptor-based auth injection
+- Automatic 401 handling
+- Environment-based base URLs
+- Type-safe API clients
+
+## Development Workflow
+1. Code generation: `flutter pub run build_runner build`
+2. Clean generation: `flutter pub run build_runner build --delete-conflicting-outputs`
+3. Watch mode: `flutter pub run build_runner watch`
+4. Environment setup: `.env` file configuration
+5. Firebase setup: Separate configs per platform
+6. Testing: Unit tests + Integration tests