npm - appiq-solution - Versions diffs - 1.4.7 → 1.4.9 - Mend

appiq-solution 1.4.7 → 1.4.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (737) hide show

package/#Tools/APPIQ-METHOD/bmad-core/templates/flutter-mobile-prd-tmpl.yaml DELETED Viewed

@@ -1,330 +0,0 @@
-document:
-  type: Flutter Mobile Product Requirements Document
-  version: 1.0
-  output_file: flutter-prd.md
-metadata:
-  product_name: "[Product Name]"
-  version: "[Version]"
-  created_date: "[Date]"
-  author: "[PM Name]"
-  stakeholders: "[Key Stakeholders]"
-  target_platforms:
-    - iOS (minimum version 12.0)
-    - Android (minimum SDK 21)
-  flutter_version: "[Flutter Version]"
-  architecture: "Clean Architecture with Feature-based Structure"
-sections:
-  - name: executive_summary
-    title: "📱 Executive Summary"
-    prompt: |
-      Provide a concise overview of the Flutter mobile application including:
-      - Core value proposition for mobile users
-      - Primary target audience and mobile usage patterns
-      - Key mobile-specific features and capabilities
-      - Business objectives and success metrics
-      - Market opportunity in mobile space
-  - name: mobile_context
-    title: "📲 Mobile Context & Market Analysis"
-    prompt: |
-      Define the mobile-specific context:
-      - Mobile market analysis and competitive landscape
-      - Target user mobile behavior patterns
-      - Device usage scenarios (phone, tablet, offline/online)
-      - Platform-specific considerations (iOS vs Android)
-      - App store positioning and discovery strategy
-  - name: user_personas
-    title: "👤 Mobile User Personas"
-    prompt: |
-      Define mobile-specific user personas including:
-      - Primary mobile user types and demographics
-      - Mobile usage patterns and device preferences
-      - User journey on mobile devices
-      - Pain points in current mobile solutions
-      - Mobile-specific needs and expectations
-  - name: feature_requirements
-    title: "🎯 Feature Requirements (Flutter Clean Architecture)"
-    prompt: |
-      Organize features using Flutter's feature-based architecture:
-      ## Core Features
-      For each major feature, define:
-      ### [Feature Name] Feature
-      **Business Logic (Domain Layer):**
-      - Entities: [Define business entities]
-      - Use Cases: [Define business use cases]
-      - Repository Interfaces: [Define data contracts]
-      - Business Rules: [Define validation rules]
-      **Data Management (Data Layer):**
-      - Data Sources: [Remote APIs, Local storage]
-      - Models: [JSON serialization models with Freezed]
-      - Repository Implementations: [Data access implementations]
-      - Caching Strategy: [Offline/online data handling]
-      **User Interface (Presentation Layer):**
-      - Pages/Screens: [List all screens for this feature]
-      - Widgets: [Reusable UI components]
-      - State Management: [Cubit states and events]
-      - Navigation: [Route definitions and deep linking]
-      **Localization:**
-      - Translation Keys: [All text content keys]
-      - Supported Languages: [List of supported locales]
-      **Testing Requirements:**
-      - Unit Tests: [Business logic testing]
-      - Widget Tests: [UI component testing]
-      - Integration Tests: [End-to-end user flows]
-  - name: ui_ux_requirements
-    title: "🎨 UI/UX Requirements (Material Design 3)"
-    prompt: |
-      Define Material Design 3 mobile UI requirements:
-      **Design System:**
-      - Material Design 3 theme and color scheme
-      - Typography scale and text styles
-      - Component library and design tokens
-      - Dark/Light theme support
-      **Responsive Design:**
-      - Phone layouts (small screens)
-      - Tablet layouts (large screens)
-      - Orientation handling (portrait/landscape)
-      - Accessibility requirements (WCAG compliance)
-      **Navigation Patterns:**
-      - Bottom navigation or navigation rail
-      - App bar configurations
-      - Drawer navigation (if applicable)
-      - Deep linking and routing structure
-      **Mobile-Specific Interactions:**
-      - Touch gestures and swipe patterns
-      - Pull-to-refresh implementations
-      - Loading states and error handling UI
-      - Offline state indicators
-  - name: technical_requirements
-    title: "⚙️ Technical Requirements"
-    prompt: |
-      Define Flutter-specific technical requirements:
-      **Flutter Architecture:**
-      - Clean Architecture implementation
-      - Feature-based folder structure
-      - Dependency injection with GetIt/Injectable
-      - State management with Cubit/BLoC
-      **Core Dependencies:**
-      - flutter_bloc for state management
-      - get_it + injectable for dependency injection
-      - freezed + json_serializable for models
-      - dio for networking
-      - hive for local storage
-      - go_router for navigation
-      - equatable for value equality
-      **Performance Requirements:**
-      - App startup time targets
-      - Screen transition performance
-      - Memory usage constraints
-      - Battery optimization considerations
-      **Platform Integration:**
-      - Device capabilities (camera, location, etc.)
-      - Push notifications
-      - In-app purchases (if applicable)
-      - Native platform features
-  - name: backend_integration
-    title: "🔌 Backend Integration"
-    prompt: |
-      Define backend integration requirements:
-      **API Requirements:**
-      - RESTful API endpoints specification
-      - Authentication and authorization flows
-      - Data synchronization patterns
-      - Real-time data updates (WebSocket/Server-Sent Events)
-      **Data Models:**
-      - JSON structure definitions
-      - Data validation requirements
-      - Error response formats
-      - Pagination and filtering patterns
-      **Offline Capabilities:**
-      - Local data caching strategy
-      - Offline-first functionality
-      - Data synchronization on reconnection
-      - Conflict resolution patterns
-  - name: security_requirements
-    title: "🔒 Security Requirements"
-    prompt: |
-      Define mobile security requirements:
-      **Data Protection:**
-      - Sensitive data encryption (flutter_secure_storage)
-      - Biometric authentication integration
-      - Session management and token refresh
-      - Certificate pinning for API calls
-      **Input Validation:**
-      - Form validation patterns
-      - Sanitization of user inputs
-      - Protection against injection attacks
-      - File upload security
-      **Privacy Compliance:**
-      - GDPR/CCPA compliance requirements
-      - User consent management
-      - Data retention policies
-      - Analytics and tracking permissions
-  - name: localization_requirements
-    title: "🌍 Localization & Accessibility"
-    prompt: |
-      Define internationalization requirements:
-      **Multi-Language Support:**
-      - Supported languages and locales
-      - Text direction support (LTR/RTL)
-      - Date, time, and number formatting
-      - Currency and unit localization
-      **Accessibility:**
-      - Screen reader support
-      - Voice navigation
-      - High contrast mode
-      - Font size scaling
-      - Keyboard navigation support
-  - name: performance_metrics
-    title: "📊 Performance & Success Metrics"
-    prompt: |
-      Define measurable success criteria:
-      **Technical Performance:**
-      - App launch time: [Target in milliseconds]
-      - Screen transition time: [Target]
-      - API response time: [Acceptable ranges]
-      - Memory usage: [Maximum limits]
-      - Battery consumption: [Optimization targets]
-      **Business Metrics:**
-      - User engagement metrics
-      - Conversion rates
-      - User retention rates
-      - App store ratings targets
-      - Feature adoption rates
-  - name: development_phases
-    title: "🚀 Development Phases"
-    prompt: |
-      Define development phases using Flutter feature-based approach:
-      **Phase 1: Core Foundation**
-      - Project setup and architecture
-      - Authentication and user management
-      - Core navigation structure
-      - Basic UI components and theme
-      **Phase 2: Essential Features**
-      - [List core features with priorities]
-      - Each feature includes all layers (data/domain/presentation)
-      - Basic testing implementation
-      **Phase 3: Advanced Features**
-      - [List advanced features]
-      - Performance optimizations
-      - Advanced animations and interactions
-      **Phase 4: Polish & Launch**
-      - Comprehensive testing
-      - App store preparation
-      - Performance optimization
-      - Launch strategy
-  - name: constraints_assumptions
-    title: "⚠️ Constraints & Assumptions"
-    prompt: |
-      Document constraints and assumptions:
-      **Technical Constraints:**
-      - Flutter version compatibility
-      - Minimum device requirements
-      - Third-party SDK limitations
-      - App store guidelines compliance
-      **Business Constraints:**
-      - Budget limitations
-      - Timeline constraints
-      - Resource availability
-      - Regulatory requirements
-      **Assumptions:**
-      - User device capabilities
-      - Network connectivity assumptions
-      - Backend service availability
-      - Third-party service reliability
-  - name: acceptance_criteria
-    title: "✅ Acceptance Criteria"
-    prompt: |
-      Define clear acceptance criteria for each feature:
-      **Feature Completion Criteria:**
-      - All layers implemented (data/domain/presentation)
-      - Unit tests coverage > 80%
-      - Widget tests for all UI components
-      - Integration tests for user flows
-      - Localization keys implemented
-      - Accessibility compliance verified
-      - Performance benchmarks met
-      **Quality Gates:**
-      - DRY: No code duplication
-      - Readable: Clear code structure
-      - Maintainable: Modular architecture
-      - Performant: Meets performance targets
-      - Testable: Comprehensive test coverage
-      - Secure: Security validation passed
-      - Localized: Multi-language support
-instructions:
-  pre_fill: |
-    Before starting this PRD:
-    1. Review any existing project documentation
-    2. Understand the target audience and mobile usage patterns
-    3. Research competitor mobile apps and market positioning
-    4. Consider Flutter's capabilities and limitations
-    5. Plan for feature-based architecture from the beginning
-  post_completion: |
-    After completing this PRD:
-    1. Validate with stakeholders and mobile UX experts
-    2. Review technical feasibility with Flutter developers
-    3. Ensure alignment with business objectives
-    4. Plan for architecture document creation
-    5. Prepare for feature-based story creation by Scrum Master
-    6. Save as docs/flutter-prd.md for development team reference
-  quality_checklist:
-    - "All features mapped to Flutter's clean architecture layers"
-    - "Material Design 3 principles incorporated"
-    - "Responsive design considerations included"
-    - "Localization requirements defined"
-    - "Performance metrics are measurable"
-    - "Security requirements are comprehensive"
-    - "Accessibility compliance addressed"
-    - "Backend integration patterns defined"
-    - "Testing strategy covers all layers"
-    - "Development phases are realistic and feature-based"

package/#Tools/APPIQ-METHOD/bmad-core/templates/flutter-story-tmpl.yaml DELETED Viewed

@@ -1,376 +0,0 @@
-document:
-  type: Flutter Feature Story
-  version: 1.0
-  output_file: flutter-story.md
-metadata:
-  story_id: "[STORY-ID]"
-  feature_name: "[Feature Name]"
-  story_title: "[Story Title]"
-  created_date: "[Date]"
-  author: "[Scrum Master Name]"
-  priority: "[High/Medium/Low]"
-  estimate: "[Story Points]"
-  flutter_layers:
-    - presentation
-    - domain
-    - data
-  architecture: "Clean Architecture"
-sections:
-  - name: story_header
-    title: "📱 Flutter Feature Story"
-    prompt: |
-      ## Story: [Story Title]
-      **Story ID:** [STORY-ID]
-      **Feature:** [Feature Name]
-      **Priority:** [High/Medium/Low]
-      **Estimate:** [Story Points]
-      **Status:** Draft
-      **Flutter Architecture Layers:**
-      - ✅ Presentation Layer (UI/Cubit)
-      - ✅ Domain Layer (Entities/UseCases)
-      - ✅ Data Layer (Models/Repositories)
-  - name: user_story
-    title: "👤 User Story"
-    prompt: |
-      Write the user story in standard format:
-      **As a** [type of user]
-      **I want** [goal/functionality]
-      **So that** [benefit/value]
-      **Mobile Context:**
-      - Device usage scenario (phone/tablet, portrait/landscape)
-      - User interaction patterns (touch, swipe, navigation)
-      - Offline/online behavior expectations
-      - Performance and responsiveness requirements
-  - name: acceptance_criteria
-    title: "✅ Acceptance Criteria"
-    prompt: |
-      Define clear, testable acceptance criteria:
-      **Functional Criteria:**
-      1. [Specific functionality requirement]
-      2. [User interaction behavior]
-      3. [Data handling requirement]
-      4. [Navigation and routing behavior]
-      **UI/UX Criteria:**
-      1. Material Design 3 compliance verified
-      2. Responsive layout works on phone and tablet
-      3. Dark/light theme support implemented
-      4. Accessibility requirements met (WCAG AA)
-      5. Smooth animations and transitions
-      **Technical Criteria:**
-      1. Clean Architecture layers properly separated
-      2. Cubit state management implemented correctly
-      3. Error handling covers all scenarios
-      4. Loading states provide appropriate feedback
-      5. Localization keys used (no static text)
-      **Performance Criteria:**
-      1. Screen loads within [X] milliseconds
-      2. Smooth 60fps animations
-      3. Memory usage stays within acceptable limits
-      4. Battery impact minimized
-  - name: flutter_tasks
-    title: "🎯 Flutter Implementation Tasks"
-    prompt: |
-      Break down implementation by Flutter architecture layers:
-      ## Presentation Layer Tasks
-      **UI Implementation:**
-      - [ ] Create feature pages/screens with Material 3 design
-      - [ ] Implement custom widgets and components
-      - [ ] Set up responsive layouts for phone/tablet
-      - [ ] Add animations and micro-interactions
-      - [ ] Implement accessibility features (Semantics, etc.)
-      **State Management (Cubit):**
-      - [ ] Create Cubit class with business logic coordination
-      - [ ] Define State classes with Equatable
-      - [ ] Implement state transitions and error handling
-      - [ ] Add loading, success, and error states
-      - [ ] Connect UI to Cubit with BlocBuilder/BlocListener
-      **Navigation & Routing:**
-      - [ ] Define routes and navigation paths
-      - [ ] Implement deep linking (if required)
-      - [ ] Add navigation transitions
-      - [ ] Handle back navigation and gestures
-      ## Domain Layer Tasks
-      **Business Entities:**
-      - [ ] Create entity classes with Equatable
-      - [ ] Define entity relationships and properties
-      - [ ] Implement copyWith methods for immutability
-      - [ ] Add entity validation rules
-      **Use Cases:**
-      - [ ] Implement use case classes with @injectable
-      - [ ] Add business logic and validation
-      - [ ] Define Either<Failure, Success> return types
-      - [ ] Create use case unit tests
-      **Repository Interfaces:**
-      - [ ] Define repository abstract classes
-      - [ ] Specify method signatures and return types
-      - [ ] Document expected behavior and contracts
-      ## Data Layer Tasks
-      **Data Models:**
-      - [ ] Create model classes with @freezed annotation
-      - [ ] Add JSON serialization with json_serializable
-      - [ ] Implement model to entity conversion methods
-      - [ ] Handle API field mapping with @JsonKey
-      **Repository Implementations:**
-      - [ ] Implement concrete repository classes
-      - [ ] Add dependency injection with @LazySingleton
-      - [ ] Implement data source coordination
-      - [ ] Add error handling and data transformation
-      **Data Sources:**
-      - [ ] Create remote data source for API calls
-      - [ ] Implement local data source for caching
-      - [ ] Add network connectivity handling
-      - [ ] Implement offline-first functionality (if required)
-      ## Localization & Theming
-      - [ ] Add all text content to ARB files
-      - [ ] Implement right-to-left (RTL) support
-      - [ ] Verify dark/light theme compatibility
-      - [ ] Test with different locale settings
-      ## Testing Tasks
-      - [ ] Write unit tests for domain layer (entities, use cases)
-      - [ ] Create unit tests for data layer (repositories, models)
-      - [ ] Implement widget tests for UI components
-      - [ ] Add Cubit/state management tests
-      - [ ] Create integration tests for user flows
-      - [ ] Verify accessibility with testing tools
-  - name: technical_details
-    title: "⚙️ Technical Implementation Details"
-    prompt: |
-      Provide technical guidance for developers:
-      **Flutter Dependencies Required:**
-      ```yaml
-      dependencies:
-        flutter_bloc: ^8.1.6
-        get_it: ^8.0.2
-        injectable: ^2.5.0
-        freezed_annotation: ^2.4.4
-        json_annotation: ^4.9.0
-        equatable: ^2.0.7
-        dartz: ^0.10.1
-        dio: ^5.7.0
-        hive: ^2.2.3
-        go_router: ^14.0.0
-      dev_dependencies:
-        build_runner: ^2.4.13
-        injectable_generator: ^2.6.2
-        freezed: ^2.5.7
-        json_serializable: ^6.8.0
-        bloc_test: ^9.1.7
-        mocktail: ^1.0.4
-      ```
-      **File Structure:**
-      ```
-      lib/features/[feature_name]/
-      ├── data/
-      │   ├── datasources/
-      │   │   ├── [feature]_local_datasource.dart
-      │   │   └── [feature]_remote_datasource.dart
-      │   ├── models/
-      │   │   ├── [model_name]_model.dart
-      │   │   ├── [model_name]_model.freezed.dart
-      │   │   └── [model_name]_model.g.dart
-      │   └── repositories/
-      │       └── [feature]_repository_impl.dart
-      ├── domain/
-      │   ├── entities/
-      │   │   └── [entity_name]_entity.dart
-      │   ├── repositories/
-      │   │   └── [feature]_repository.dart
-      │   └── usecases/
-      │       ├── get_[items]_usecase.dart
-      │       ├── create_[item]_usecase.dart
-      │       └── update_[item]_usecase.dart
-      └── presentation/
-          ├── cubit/
-          │   ├── [feature]_cubit.dart
-          │   └── [feature]_state.dart
-          ├── pages/
-          │   ├── [feature]_list_page.dart
-          │   └── [feature]_detail_page.dart
-          └── widgets/
-              ├── [custom_widget]_widget.dart
-              └── [feature]_item_widget.dart
-      ```
-      **Key Implementation Patterns:**
-      - Use `const` constructors for performance
-      - Implement proper widget keys for testing
-      - Follow Material Design 3 guidelines
-      - Use BlocBuilder for state-dependent UI
-      - Use BlocListener for side effects (navigation, snackbars)
-      - Implement proper error boundaries
-      - Add loading indicators for async operations
-  - name: testing_requirements
-    title: "🧪 Testing Requirements"
-    prompt: |
-      Define comprehensive testing approach:
-      **Unit Tests (Domain Layer):**
-      - Test all entity copyWith methods and equality
-      - Test use case business logic and validation
-      - Test repository interface contracts
-      - Mock dependencies for isolated testing
-      - Target: 100% coverage for business logic
-      **Unit Tests (Data Layer):**
-      - Test model JSON serialization/deserialization
-      - Test repository implementations
-      - Test data source implementations
-      - Mock HTTP clients and local storage
-      - Test error handling and edge cases
-      **Widget Tests (Presentation Layer):**
-      - Test all custom widgets in isolation
-      - Test page widgets with different states
-      - Test user interactions (tap, swipe, input)
-      - Test accessibility semantics
-      - Mock Cubit dependencies
-      **Cubit Tests:**
-      - Test all state transitions
-      - Test error handling and recovery
-      - Test loading states and timing
-      - Use bloc_test for comprehensive coverage
-      - Mock use case dependencies
-      **Integration Tests:**
-      - Test complete user flows end-to-end
-      - Test navigation between screens
-      - Test data persistence and retrieval
-      - Test offline/online scenarios
-      - Test performance under load
-  - name: dev_notes
-    title: "📝 Development Notes"
-    prompt: |
-      Additional guidance and considerations:
-      **Performance Considerations:**
-      - Use ListView.builder for large lists
-      - Implement image caching for network images
-      - Optimize widget build methods
-      - Use keys for widget identity and performance
-      - Profile memory usage during development
-      **Accessibility Implementation:**
-      - Add Semantics widgets for screen readers
-      - Ensure minimum touch target sizes (44x44)
-      - Provide meaningful content descriptions
-      - Test with TalkBack/VoiceOver
-      - Support high contrast and large fonts
-      **Localization Guidelines:**
-      - Never use hardcoded strings in UI
-      - Use context-aware translation keys
-      - Handle text expansion/contraction
-      - Test with RTL languages
-      - Format dates, numbers, and currencies correctly
-      **Code Quality Standards:**
-      - DRY: Reuse widgets and business logic
-      - Readable: Clear naming and code structure
-      - Maintainable: Modular and loosely coupled
-      - Performant: Optimized for mobile devices
-      - Testable: Easy to test in isolation
-  - name: definition_of_done
-    title: "✅ Definition of Done"
-    prompt: |
-      Story completion checklist:
-      **Implementation Complete:**
-      - [ ] All tasks marked as complete
-      - [ ] All architecture layers implemented
-      - [ ] UI matches design specifications
-      - [ ] Material Design 3 compliance verified
-      - [ ] Responsive design works on all screen sizes
-      **Code Quality:**
-      - [ ] Code follows Flutter best practices
-      - [ ] No hardcoded strings (all localized)
-      - [ ] Error handling implemented
-      - [ ] Loading states provide feedback
-      - [ ] Accessibility requirements met
-      **Testing Complete:**
-      - [ ] Unit tests written and passing (>80% coverage)
-      - [ ] Widget tests written and passing
-      - [ ] Cubit tests written and passing
-      - [ ] Integration tests written and passing
-      - [ ] Manual testing on different devices
-      **Performance Verified:**
-      - [ ] No memory leaks detected
-      - [ ] Smooth animations (60fps)
-      - [ ] Acceptable loading times
-      - [ ] Battery usage optimized
-      **Documentation:**
-      - [ ] Code commented where necessary
-      - [ ] API documentation updated
-      - [ ] File list maintained
-      - [ ] Change log updated
-      **Review Process:**
-      - [ ] Code review completed
-      - [ ] Design review approved
-      - [ ] QA testing passed
-      - [ ] Accessibility testing completed
-      - [ ] Performance benchmarks met
-instructions:
-  pre_fill: |
-    Before creating this Flutter story:
-    1. Review Flutter PRD and architecture documents
-    2. Understand the specific feature requirements
-    3. Consider the target users and usage patterns
-    4. Plan the implementation across all three layers
-    5. Identify dependencies and integration points
-  post_completion: |
-    After completing this Flutter story:
-    1. Review with product owner and tech lead
-    2. Validate technical approach and estimates
-    3. Ensure all acceptance criteria are testable
-    4. Confirm resource availability and timeline
-    5. Prepare for developer handoff with clear documentation
-  quality_checklist:
-    - "Story follows standard user story format"
-    - "Acceptance criteria are specific and testable"
-    - "Tasks are broken down by Flutter architecture layers"
-    - "Technical details provide clear implementation guidance"
-    - "Testing requirements are comprehensive"
-    - "Definition of done is complete and measurable"
-    - "Performance and accessibility requirements included"
-    - "Localization requirements specified"
-    - "Code quality standards defined"
-    - "Integration points identified and documented"