appiq-solution 1.6.4 → 1.7.0

package/docs/livestream_prd_smart.md

@@ -0,0 +1,278 @@
+# Livestream Feature PRD
+
+## Overview
+Implementierung einer Live-Streaming-Funktionalität in die bestehende Flutter-App mit intelligenter Integration in vorhandene Komponenten.
+
+## Implementation Paths
+> Spezifische Pfade für optimale Integration
+
+### Suggested File Structure
+```
+lib/
+├── features/
+│   └── livestream/                    # ← Neues Feature
+│       ├── data/
+│       │   ├── datasources/
+│       │   │   ├── livestream_remote_datasource.dart
+│       │   │   └── livestream_local_datasource.dart
+│       │   ├── models/
+│       │   │   ├── stream_model.dart
+│       │   │   └── stream_chat_model.dart
+│       │   └── repositories/
+│       │       └── livestream_repository_impl.dart
+│       ├── domain/
+│       │   ├── entities/
+│       │   │   ├── stream_entity.dart
+│       │   │   └── stream_message_entity.dart
+│       │   ├── repositories/
+│       │   │   └── livestream_repository.dart
+│       │   └── usecases/
+│       │       ├── start_stream_usecase.dart
+│       │       ├── join_stream_usecase.dart
+│       │       └── send_chat_message_usecase.dart
+│       └── presentation/
+│           ├── cubit/
+│           │   ├── livestream_cubit.dart
+│           │   ├── livestream_state.dart
+│           │   ├── stream_chat_cubit.dart
+│           │   └── stream_chat_state.dart
+│           ├── pages/
+│           │   ├── stream_list_page.dart
+│           │   ├── stream_viewer_page.dart
+│           │   └── stream_creator_page.dart
+│           └── widgets/
+│               ├── stream_player_widget.dart
+│               ├── stream_controls_widget.dart
+│               └── stream_chat_widget.dart
+```
+
+### Integration Points
+> Bestehende Dateien/Klassen für Integration:
+
+- **Main Navigation**: `lib/features/home/presentation/pages/home_page.dart`
+  - Füge "Go Live" Button in AppBar hinzu
+  - Integriere Stream-Liste in Home-Feed
+
+- **Existing API Service**: `lib/shared/services/api_service.dart`
+  - Erweitere für WebRTC-Endpoints
+  - Nutze bestehende Auth-Header
+
+- **Video Player Base**: `lib/features/media/presentation/widgets/video_player_widget.dart`
+  - Erweitere für Live-Stream-Funktionalität
+  - Nutze bestehende Player-Controls
+
+- **Chat System**: `lib/features/chat/presentation/widgets/chat_widget.dart`
+  - Adaptiere für Live-Stream-Chat
+  - Nutze bestehende Message-Patterns
+
+- **User Profile Integration**: `lib/features/user/presentation/pages/profile_page.dart`
+  - Füge "My Streams" Sektion hinzu
+  - Zeige Stream-History
+
+### Code Reuse Analysis
+> Bestehende Komponenten prüfen und wiederverwenden:
+
+#### Existing Similar Features (PRÜFEN ZUERST!)
+- [ ] **Video Feature**: `lib/features/video/` - Für Player-Logik
+- [ ] **Chat Feature**: `lib/features/chat/` - Für Chat-Implementation
+- [ ] **Camera Feature**: `lib/features/camera/` - Für Stream-Aufnahme
+- [ ] **Notification Feature**: `lib/features/notifications/` - Für Stream-Alerts
+
+#### Shared Components to Reuse (VERWENDEN STATT NEU ERSTELLEN!)
+- [ ] `lib/shared/widgets/loading_widget.dart` - Für Stream-Loading
+- [ ] `lib/shared/widgets/error_widget.dart` - Für Stream-Errors
+- [ ] `lib/shared/widgets/custom_button.dart` - Für Stream-Controls
+- [ ] `lib/shared/widgets/user_avatar.dart` - Für Streamer-Avatar
+- [ ] `lib/shared/widgets/bottom_sheet_widget.dart` - Für Stream-Settings
+- [ ] `lib/shared/services/navigation_service.dart` - Für Stream-Navigation
+- [ ] `lib/shared/services/websocket_service.dart` - Für Real-time Chat
+- [ ] `lib/shared/utils/validators.dart` - Für Stream-Input-Validation
+- [ ] `lib/shared/utils/permission_handler.dart` - Für Camera/Mic-Permissions
+
+#### Common Patterns to Follow (BESTEHENDE PATTERNS BEFOLGEN!)
+- [ ] **Cubit Naming**: `LivestreamCubit`, `LivestreamState` (wie `AuthCubit`)
+- [ ] **Error Handling**: `StreamFailure` extends `Failure` (wie `AuthFailure`)
+- [ ] **API Patterns**: `ApiResponse<StreamModel>` (wie bestehende APIs)
+- [ ] **Repository Pattern**: Folge `UserRepository` Struktur
+- [ ] **DI Pattern**: Registrierung wie in `injection_container.dart`
+
+## UI References
+> Mockups und Referenz-Bilder für Development
+
+### Design Assets Location
+```
+assets/
+├── images/
+│   └── livestream/
+│       ├── mockup_stream_list.png          # ← Haupt-Stream-Liste
+│       ├── mockup_stream_viewer.png        # ← Stream-Viewer mit Chat
+│       ├── mockup_stream_creator.png       # ← Stream-Erstellung
+│       ├── wireframe_stream_flow.png       # ← User-Flow Diagramm
+│       └── ui_components_reference.png     # ← UI-Komponenten Guide
+└── icons/
+    └── livestream/
+        ├── stream_icon.svg                 # ← Live-Stream Icon
+        ├── camera_icon.svg                 # ← Kamera Icon
+        ├── chat_icon.svg                   # ← Chat Icon
+        └── viewer_count_icon.svg           # ← Viewer-Anzahl Icon
+```
+
+### UI Reference Links
+- **Figma Design**: https://figma.com/livestream-feature-v2
+- **Design System**: `lib/shared/theme/app_theme.dart` - Folge bestehende Patterns
+- **Similar UI Reference**: 
+  - `lib/features/video/presentation/pages/video_player_page.dart` - Für Player-Layout
+  - `lib/features/chat/presentation/widgets/chat_list_widget.dart` - Für Chat-UI
+
+### Visual Guidelines (BESTEHENDE PATTERNS VERWENDEN!)
+- **Theme**: Erweitere `lib/shared/theme/app_theme.dart`
+  - Füge `livestreamColors` zu `AppColors` hinzu
+  - Nutze bestehende `primaryColor` für Live-Indicator
+- **Typography**: Verwende `AppTextStyles.headline1` für Stream-Titel
+- **Spacing**: Nutze `AppSpacing.medium` für konsistente Abstände
+- **Components**: Erweitere `lib/shared/widgets/` statt neue zu erstellen
+
+## Features
+- **Live Stream Starten**: Integration mit bestehender Camera-Feature
+- **Stream Discovery**: Erweitere Home-Feed um Stream-Liste  
+- **Real-time Chat**: Nutze bestehende Chat-Infrastruktur
+- **Stream Controls**: Erweitere bestehende Video-Controls
+- **Viewer Analytics**: Integration in bestehende Analytics
+
+## Acceptance Criteria
+
+### Live Stream Starten
+- [ ] **Reuse Camera Permission**: Nutze `lib/shared/utils/permission_handler.dart`
+- [ ] **Extend Navigation**: Füge zu `lib/core/routing/app_router.dart` hinzu
+- [ ] **Follow Button Pattern**: Nutze `lib/shared/widgets/custom_button.dart`
+
+### Stream Viewer  
+- [ ] **Extend Video Player**: Erweitere `lib/features/video/presentation/widgets/video_player_widget.dart`
+- [ ] **Reuse Loading States**: Nutze `lib/shared/widgets/loading_widget.dart`
+- [ ] **Follow Page Structure**: Wie `lib/features/video/presentation/pages/video_player_page.dart`
+
+### Chat Integration
+- [ ] **Extend Chat Widget**: Adaptiere `lib/features/chat/presentation/widgets/chat_widget.dart`
+- [ ] **Reuse WebSocket**: Nutze `lib/shared/services/websocket_service.dart`
+- [ ] **Follow Message Pattern**: Wie `lib/features/chat/domain/entities/message_entity.dart`
+
+## Technical Requirements
+
+### Architecture Compliance (BESTEHENDE PATTERNS BEFOLGEN!)
+- [ ] **Clean Architecture**: Folge `lib/features/user/` Struktur
+- [ ] **Cubit State Management**: Wie `lib/features/auth/presentation/cubit/auth_cubit.dart`
+- [ ] **Repository Pattern**: Wie `lib/features/user/data/repositories/user_repository_impl.dart`
+- [ ] **Dependency Injection**: Registrierung in `lib/core/di/injection_container.dart`
+
+### Code Integration Requirements (ZUERST PRÜFEN!)
+- [ ] **Before New API Client**: Erweitere `lib/shared/services/api_service.dart`
+- [ ] **Before New WebSocket**: Prüfe `lib/shared/services/websocket_service.dart`
+- [ ] **Before New Widgets**: Prüfe `lib/shared/widgets/` für ähnliche Komponenten
+- [ ] **Before New Utils**: Prüfe `lib/shared/utils/` für Helper-Functions
+- [ ] **Before New Services**: Prüfe `lib/shared/services/` für ähnliche Services
+
+### Performance Requirements (BESTEHENDE OPTIMIERUNGEN NUTZEN!)
+- [ ] **Image Caching**: Nutze bestehende `lib/shared/services/image_cache_service.dart`
+- [ ] **Network Optimization**: Folge bestehende API-Caching-Patterns
+- [ ] **Memory Management**: Wie in `lib/features/video/` implementiert
+
+## Auto-Analysis Instructions
+> Für das smart-auto-detect System
+
+### Code Analysis Tasks
+1. **Scan Similar Features**:
+   ```bash
+   # Prüfe Video-Feature für Player-Patterns
+   find lib/features/video/ -name "*.dart" | head -10
+   
+   # Prüfe Chat-Feature für Message-Patterns  
+   find lib/features/chat/ -name "*.dart" | head -10
+   
+   # Prüfe Camera-Feature für Aufnahme-Patterns
+   find lib/features/camera/ -name "*.dart" | head -10
+   ```
+
+2. **Shared Component Analysis**:
+   ```bash
+   # Prüfe verfügbare Widgets
+   ls -la lib/shared/widgets/ | grep -E "(video|chat|button|loading)"
+   
+   # Prüfe verfügbare Services
+   ls -la lib/shared/services/ | grep -E "(api|websocket|navigation)"
+   
+   # Prüfe verfügbare Utils
+   ls -la lib/shared/utils/ | grep -E "(validator|permission|formatter)"
+   ```
+
+### Architect Fallback Rules
+> Wenn Pfade nicht spezifiziert sind:
+
+1. **Feature Complexity**: HOCH → Eigenes Feature-Verzeichnis
+2. **Dependencies**: Video + Chat + Camera → Nutze bestehende Integration-Patterns
+3. **UI Complexity**: Multiple Screens → Folge `lib/features/video/` Struktur
+
+## User Stories
+
+### Epic: Live Streaming Infrastructure
+- Als Entwickler möchte ich bestehende Video-Player-Komponenten erweitern, damit ich keine redundante Player-Logik erstelle
+- Als Entwickler möchte ich bestehende Chat-Infrastruktur nutzen, damit Real-time-Messaging bereits funktioniert
+- Als Entwickler möchte ich bestehende Camera-Services verwenden, damit Permissions bereits verwaltet sind
+
+### Epic: Stream Creation & Management  
+- Als Content Creator möchte ich den vertrauten Camera-Button verwenden, damit die Stream-Erstellung intuitiv ist
+- Als Content Creator möchte ich bestehende Navigation-Patterns nutzen, damit die App konsistent bleibt
+- Als Content Creator möchte ich bekannte UI-Komponenten sehen, damit die Bedienung vertraut ist
+
+### Epic: Stream Consumption
+- Als Viewer möchte ich den gewohnten Video-Player sehen, damit die Bedienung vertraut ist
+- Als Viewer möchte ich das bekannte Chat-Interface nutzen, damit ich sofort weiß, wie ich interagiere
+- Als Viewer möchte ich konsistente Loading-States sehen, damit die App professionell wirkt
+
+## Dependencies
+
+### Existing Code Dependencies (WIEDERVERWENDEN!)
+- `lib/features/video/` - Video Player Base-Funktionalität
+- `lib/features/chat/` - Real-time Chat Infrastructure
+- `lib/features/camera/` - Camera Access & Permissions
+- `lib/shared/services/api_service.dart` - HTTP Client für Stream-APIs
+- `lib/shared/services/websocket_service.dart` - Real-time Communication
+- `lib/shared/widgets/` - UI Components (Button, Loading, Error)
+
+### New External Dependencies
+- `webrtc_interface: ^1.0.0` - Für Live-Streaming
+- `agora_rtc_engine: ^6.0.0` - Stream Infrastructure (falls nicht WebRTC)
+
+### Backend Dependencies
+- WebRTC Signaling Server
+- Stream Media Server (RTMP/HLS)
+- Chat WebSocket Endpoints (erweitere bestehende)
+
+## Migration/Integration Notes
+
+### Existing Feature Integration
+- [ ] **Video Feature**: Erweitere Player für Live-Streams
+- [ ] **Chat Feature**: Adaptiere für Stream-spezifische Messages
+- [ ] **Home Feature**: Integriere Stream-Liste in Feed
+- [ ] **Profile Feature**: Füge Stream-History hinzu
+
+### Navigation Integration
+- [ ] Erweitere `lib/core/routing/app_router.dart`:
+  ```dart
+  GoRoute(
+    path: '/livestream',
+    builder: (context, state) => const StreamListPage(),
+  ),
+  GoRoute(
+    path: '/livestream/:streamId',
+    builder: (context, state) => StreamViewerPage(
+      streamId: state.params['streamId']!,
+    ),
+  ),
+  ```
+
+### State Management Integration
+- [ ] Erweitere globale App-State falls nötig
+- [ ] Integration mit bestehenden User-State für Streamer-Info
+- [ ] Benachrichtigungs-State für Stream-Alerts
+
+Das ist ein intelligentes PRD, das maximale Code-Wiederverwendung sicherstellt! 🧠✨

package/docs/onboarding_prd.md

@@ -0,0 +1,93 @@
+# Onboarding Product Requirements Document
+
+## 1. Overview
+This document outlines the requirements for the **User Onboarding** feature in our Flutter mobile application. The onboarding flow should guide new users through the app's key features and help them get started quickly.
+
+## 2. Feature Description
+A comprehensive onboarding experience consisting of:
+- Welcome screen with app introduction
+- Feature highlights (3-4 key screens)
+- Account setup/login integration
+- Permissions requests (notifications, location, etc.)
+- Tutorial completion confirmation
+
+The onboarding should be skippable and only shown to first-time users.
+
+## 3. Functional Requirements
+- FR1: Display welcome screen with app logo and tagline
+- FR2: Show 3-4 feature highlight screens with illustrations
+- FR3: Integrate with existing authentication system
+- FR4: Request necessary permissions (push notifications, location)
+- FR5: Allow users to skip onboarding at any point
+- FR6: Remember onboarding completion status
+- FR7: Provide "Get Started" button to proceed to main app
+- FR8: Support both light and dark themes
+
+## 4. Non-Functional Requirements
+- NFR1: Performance - Smooth page transitions with animations
+- NFR2: Accessibility - Support for screen readers and large text
+- NFR3: Localization - Support for all app languages
+- NFR4: Security - No sensitive data collection during onboarding
+- NFR5: Analytics - Track onboarding completion rates
+
+## 5. User Stories
+- As a new user, I want to understand what the app does so that I can decide to continue using it.
+- As a new user, I want to see key features highlighted so that I know what's available.
+- As a new user, I want to quickly set up my account so that I can start using the app.
+- As a returning user, I want to skip onboarding so that I can access the app immediately.
+- As a user with accessibility needs, I want the onboarding to be screen reader friendly.
+
+## 6. Implementation Details (Optional - for Brownfield Projects)
+**Implementation Path:** `lib/features/onboarding`
+*   **Rationale**: New standalone feature that doesn't interfere with existing authentication flow. Clean separation from other features.
+*   **Integration Points**:
+    - `lib/main.dart` (for routing - add onboarding route)
+    - `lib/core/di/injection_container.dart` (for dependency injection)
+    - `lib/features/auth/presentation/cubit/auth_cubit.dart` (check if user is first-time)
+    - `lib/shared/widgets/base_scaffold.dart` (for consistent styling)
+    - `lib/core/storage/local_storage_service.dart` (store onboarding completion)
+*   **Existing Components to Check for Reuse**:
+    - `lib/shared/widgets/custom_button.dart` (for CTA buttons)
+    - `lib/shared/widgets/loading_widget.dart` (for loading states)
+    - `lib/shared/utils/theme_helper.dart` (for theme-aware styling)
+    - `lib/shared/widgets/animated_page_view.dart` (if exists for page transitions)
+    - `lib/features/auth/data/models/user_model.dart` (for user state)
+    - `lib/core/error/failures.dart` (for error handling)
+
+## 7. UI Reference (Optional)
+*   **Mockups/Wireframes**:
+    - `docs/ui/mockups/onboarding_welcome_screen.png`
+    - `docs/ui/mockups/onboarding_feature_highlights.png`
+    - `docs/ui/mockups/onboarding_permissions.png`
+    - `docs/ui/mockups/onboarding_completion.png`
+*   **Design Notes**: 
+    - Use app's primary brand colors
+    - Consistent with Material 3 design system
+    - Smooth page transitions with fade/slide animations
+    - Minimum 44pt touch targets for accessibility
+
+## 8. Acceptance Criteria
+- AC1: New users see onboarding flow on first app launch
+- AC2: Returning users bypass onboarding and go directly to main app
+- AC3: Users can skip onboarding at any point using "Skip" button
+- AC4: All text is localized and supports app's languages
+- AC5: Onboarding works in both light and dark themes
+- AC6: Page transitions are smooth with appropriate animations
+- AC7: Permissions are requested at appropriate moments
+- AC8: Onboarding completion is persisted locally
+- AC9: Analytics events are fired for onboarding steps
+- AC10: Accessibility features work correctly (screen readers, large text)
+
+## 9. Dependencies
+- Existing authentication system integration
+- Local storage service for persistence
+- Analytics service for tracking
+- Permission handling service
+- Theme system integration
+
+## 10. Future Scope
+- A/B testing different onboarding flows
+- Personalized onboarding based on user type
+- Interactive tutorials for complex features
+- Video introductions for key features
+- Progressive onboarding (show features when relevant)

package/expansion-packs/appiq-flutter-mobile-dev/agents/flutter-ui-agent.md

@@ -111,12 +111,38 @@ security_considerations:
   - Prevent UI-based attacks (like tapjacking)
 
 standard_workflow:
-  - Think through UI requirements and read existing codebase
-  - Write implementation plan to tasks/todo.md
-  - Get plan verified before beginning work
-  - Implement UI components marking todo items complete
-  - Provide high-level explanations of changes
-  - Keep changes simple and focused
-  - Add review section to todo.md
-  - Make git commit after completion
+  - MANDATORY: Think through UI requirements and read existing codebase FIRST
+  - MANDATORY: Write detailed implementation plan to tasks/todo.md with checkable items
+  - MANDATORY: Get plan verified before beginning ANY work
+  - MANDATORY: Check lib/shared/widgets/ for existing components BEFORE creating new ones
+  - MANDATORY: Follow existing UI patterns - NEVER create new patterns without approval
+  - MANDATORY: Use AppLocalizations for ALL text - NO static text allowed
+  - MANDATORY: Implement UI components marking todo items complete as you go
+  - MANDATORY: Provide high-level explanations of changes at every step
+  - MANDATORY: Keep changes simple and focused - minimal code impact
+  - MANDATORY: Ensure all 5 quality criteria pass (DRY, Readable, Maintainable, Performant, Testable)
+  - MANDATORY: Add review section to todo.md with quality validation
+  - MANDATORY: Make git commit after completion with proper message
+
+mandatory_quality_gates:
+  - DRY: No widget duplication - reuse existing shared widgets
+  - Readable: Clear widget composition and self-documenting code
+  - Maintainable: Modular widget architecture following existing patterns
+  - Performant: Optimized widget trees with const constructors
+  - Testable: All widgets must have widget tests
+
+mandatory_pre_coding_checklist:
+  - Check lib/shared/widgets/ for existing similar widgets
+  - Review existing page structures in lib/features/*/presentation/pages/
+  - Verify theme compliance with lib/shared/theme/app_theme.dart
+  - Plan localization keys - NO static text allowed
+  - Identify reusable components before creating new ones
+  - Follow existing naming conventions exactly
+
+mandatory_failure_conditions:
+  - Static text in widgets (instant failure)
+  - Widget duplication when shared widget exists (instant failure)
+  - Breaking existing UI patterns (instant failure)
+  - Missing widget tests (instant failure)
+  - Theme inconsistencies (instant failure)
 ```

package/expansion-packs/appiq-flutter-mobile-dev/config.yaml

@@ -1,5 +1,5 @@
 name: "BMad Flutter Mobile Development"
-version: "1.4.0"
+version: "1.5.0"
 description: "Flutter mobile app development with Clean Architecture, Cubit state management, and best practices"
 bmad_compatibility: "v4+"
 author: "BMad Team"

package/expansion-packs/appiq-flutter-mobile-dev/data/flutter-development-guidelines.md

@@ -548,4 +548,70 @@ flutter test integration_test/
 - Use secure token storage
 - Handle token refresh properly
 
+## 🚨 MANDATORY DEVELOPMENT RULES - ALWAYS FOLLOW!
+
+### CRITICAL: These rules MUST be followed by ALL agents, ALL workflows, ALL IDEs!
+
+#### Standard Workflow (NO EXCEPTIONS!)
+1. **THINK**: Analyze problem and read existing codebase
+2. **PLAN**: Write detailed plan to `tasks/todo.md` with checkable items  
+3. **VERIFY**: Get plan approved before starting ANY coding
+4. **WORK**: Execute todo items, marking complete as you go
+5. **EXPLAIN**: Provide high-level explanations at every step
+6. **SIMPLE**: Make minimal impact changes - avoid complexity
+7. **REVIEW**: Add review section to `todo.md` with summary
+8. **COMMIT**: Make git commit after each completed task
+
+#### MANDATORY Quality Gates (ALL 5 MUST PASS!)
+- 🧹 **DRY**: No code duplication - ALWAYS reuse existing code
+- 📖 **Readable**: Self-documenting code with clear naming
+- 🔧 **Maintainable**: Clean Architecture with proper separation
+- ⚡ **Performant**: Efficient algorithms and resource usage
+- 🧪 **Testable**: Comprehensive test coverage
+
+#### MANDATORY Pre-Coding Checklist
+- [ ] **Check existing code** for similar functionality FIRST
+- [ ] **Review shared components** in `lib/shared/`
+- [ ] **Follow existing patterns** - NEVER create new patterns
+- [ ] **Plan localization keys** - NO static text allowed
+- [ ] **Verify architecture compliance** with Clean Architecture
+- [ ] **Identify reusable components** before creating new ones
+
+#### MANDATORY Flutter Rules
+- ✅ **Clean Architecture**: Presentation → Domain ← Data
+- ✅ **Cubit State Management**: Follow existing Cubit patterns
+- ✅ **Repository Pattern**: Implement like existing repositories
+- ✅ **Dependency Injection**: Use GetIt like existing features
+- ✅ **Localization**: ALL text must use AppLocalizations
+- ✅ **Testing**: Unit tests for business logic, widget tests for UI
+
+#### MANDATORY Code Integration Rules
+- ✅ **BEFORE new files**: Check if similar functionality exists
+- ✅ **BEFORE new widgets**: Review `lib/shared/widgets/`
+- ✅ **BEFORE new services**: Check `lib/shared/services/`
+- ✅ **BEFORE new utilities**: Review `lib/shared/utils/`
+- ✅ **EXTEND existing code** instead of duplicating
+- ✅ **FOLLOW existing naming conventions** exactly
+
+#### MANDATORY Validation Criteria
+All code MUST pass these criteria:
+1. **Architecture**: Follows Clean Architecture with proper layer separation
+2. **Localization**: All text supports multi-language (NO static text!)
+3. **Quality**: Passes all 5 quality criteria (DRY, Readable, Maintainable, Performant, Testable)
+4. **Documentation**: Code is properly documented with examples
+5. **Consistency**: Code style matches existing patterns EXACTLY
+
+#### FAILURE CONDITIONS (NEVER ALLOWED!)
+- ❌ Static text in UI (instant failure)
+- ❌ Code duplication (instant failure)
+- ❌ Breaking existing patterns (instant failure)
+- ❌ Missing tests (instant failure)
+- ❌ Architecture violations (instant failure)
+
+### 🎯 REMEMBER: When in doubt, ALWAYS follow existing patterns!
+
+**These rules apply to ALL development work - NO EXCEPTIONS!**
+
+---
+
 This guide ensures consistent, high-quality Flutter development that meets professional standards and security requirements.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "appiq-solution",
-  "version": "1.6.4",
+  "version": "1.7.0",
   "description": "APPIQ SOLUTION: Flutter Mobile Development Extension for BMAD Method",
   "main": "tools/cli.js",
   "bin": {