appiq-solution 1.4.8 → 1.4.9

package/flutter/punkt.claude/New Folder With Items/commands/feature-ui-layer.md

@@ -1,300 +0,0 @@
-# UI Layer Development Command
-
-Develops the presentation layer (UI) for a feature following VoicePilot architectural patterns.
-
-**Usage:** `feature-ui-layer [FEATURE_NAME] [FEATURE_DESCRIPTION]`
-
-**Example:** `feature-ui-layer project-favorites "Allow users to mark projects as favorites and view them in a separate list"`
-
-## Pre-Execution Checklist
-
-1. **Check Channel Status**: Read `/Users/vapps-it/Projects/voicepilot/.claude/channel.md`
-2. **Verify Dependencies**: Ensure architecture analysis is completed
-3. **Update Channel**: Mark UI Layer status as "IN_PROGRESS" and assign agent
-4. **Check Blockers**: Verify no blockers are preventing UI development
-
-## Implementation Process
-
-### Phase 1: Analysis & Planning
-
-1. **Study Existing UI Patterns**:
-   - Analyze `lib/presentation/screens/` structure
-   - Study existing screen components and widgets
-   - Review theming patterns in `lib/core/themes/app_theme.dart`
-   - Check Material 3 implementation and color schemes
-   - Understand navigation patterns and screen transitions
-
-2. **Define UI Requirements**:
-   - Identify main screens needed for the feature
-   - Plan component hierarchy and reusability
-   - Define user interactions and navigation flows
-   - Plan responsive design considerations
-   - Identify accessibility requirements
-
-3. **Update Channel**: Add UI requirements to channel.md
-
-### Phase 2: Screen Structure Implementation
-
-1. **Create Main Screen** (`lib/presentation/screens/[feature]/[feature]_screen.dart`):
-   ```dart
-   class [FeatureName]Screen extends StatefulWidget {
-     static const routeName = '/[feature-name]';
-     
-     const [FeatureName]Screen({super.key});
-     
-     @override
-     State<[FeatureName]Screen> createState() => _[FeatureName]ScreenState();
-   }
-   
-   class _[FeatureName]ScreenState extends State<[FeatureName]Screen> {
-     @override
-     Widget build(BuildContext context) {
-       final theme = Theme.of(context);
-       final l10n = AppLocalizations.of(context);
-       
-       return Scaffold(
-         appBar: AppBar(
-           title: Text(l10n.[featureName]Title),
-           backgroundColor: theme.colorScheme.surface,
-         ),
-         body: BlocBuilder<[FeatureName]Cubit, [FeatureName]State>(
-           builder: (context, state) {
-             return _buildBody(context, state);
-           },
-         ),
-       );
-     }
-   }
-   ```
-
-2. **Follow Existing Screen Patterns**:
-   - Use identical AppBar styling from existing screens
-   - Implement consistent Scaffold structure
-   - Add proper BlocBuilder/BlocConsumer usage
-   - Include loading, error, and success states
-   - Implement proper theme integration
-
-### Phase 3: Component Development
-
-1. **Create Components Directory**: `lib/presentation/screens/[feature]/components/`
-
-2. **Implement Reusable Components**:
-   - Follow existing component patterns from other features
-   - Use consistent naming: `[feature]_[component_name].dart`
-   - Implement proper theming and Material 3 support
-   - Add accessibility support (semantics, focus management)
-   - Include proper error boundaries and loading states
-
-3. **Component Structure Template**:
-   ```dart
-   class [FeatureName][ComponentName] extends StatelessWidget {
-     final [RequiredData] data;
-     final VoidCallback? onTap;
-     
-     const [FeatureName][ComponentName]({
-       super.key,
-       required this.data,
-       this.onTap,
-     });
-     
-     @override
-     Widget build(BuildContext context) {
-       final theme = Theme.of(context);
-       final l10n = AppLocalizations.of(context);
-       
-       return Card(
-         elevation: 0,
-         color: theme.colorScheme.surface,
-         shape: RoundedRectangleBorder(
-           borderRadius: BorderRadius.circular(8),
-           side: BorderSide(
-             color: theme.colorScheme.outline.withValues(alpha: 0.2),
-           ),
-         ),
-         child: // Implementation
-       );
-     }
-   }
-   ```
-
-### Phase 4: Widget Development (if needed)
-
-1. **Create Widgets Directory**: `lib/presentation/screens/[feature]/widgets/`
-
-2. **Implement Feature-Specific Widgets**:
-   - Small, focused widgets for specific UI elements
-   - Follow existing widget patterns
-   - Ensure proper theming and responsiveness
-
-### Phase 5: State Integration
-
-1. **Implement BlocBuilder/BlocConsumer**:
-   - Handle all state variations (loading, loaded, error, initial)
-   - Implement proper error display with retry mechanisms
-   - Add loading indicators following existing patterns
-   - Handle empty states gracefully
-
-2. **State Handling Template**:
-   ```dart
-   BlocBuilder<[FeatureName]Cubit, [FeatureName]State>(
-     builder: (context, state) {
-       if (state.isLoading) {
-         return _buildLoadingState(context);
-       }
-       
-       if (state.hasError) {
-         return _buildErrorState(context, state.errorMessage!);
-       }
-       
-       if (state.isLoaded) {
-         return _buildLoadedState(context, state);
-       }
-       
-       return _buildInitialState(context);
-     },
-   )
-   ```
-
-### Phase 6: Theming & Styling
-
-1. **Implement Consistent Theming**:
-   - Use `Theme.of(context)` for all styling
-   - Follow Material 3 color scheme exactly
-   - Implement both light and dark theme support
-   - Use existing color patterns and spacing
-
-2. **Responsive Design**:
-   - Add MediaQuery-based responsive behavior
-   - Follow existing responsive patterns
-   - Ensure proper tablet and mobile layouts
-
-3. **Accessibility**:
-   - Add Semantics widgets for screen readers
-   - Implement proper focus management
-   - Use sufficient color contrast
-   - Add proper touch targets (minimum 48dp)
-
-### Phase 7: Navigation Integration
-
-1. **Route Definition**:
-   - Add route constants following existing patterns
-   - Implement proper route arguments if needed
-   - Add to main navigation configuration
-
-2. **Navigation Implementation**:
-   ```dart
-   // For navigation
-   Navigator.of(context).pushNamed([FeatureName]Screen.routeName);
-   
-   // For navigation with arguments
-   Navigator.of(context).pushNamed(
-     [FeatureName]Screen.routeName,
-     arguments: [FeatureName]Arguments(/* data */),
-   );
-   ```
-
-### Phase 8: Error Handling & Loading States
-
-1. **Implement Error UI**:
-   - Follow existing error display patterns
-   - Add retry buttons where appropriate
-   - Show user-friendly error messages
-   - Include proper error logging
-
-2. **Loading States**:
-   - Use consistent loading indicators
-   - Implement skeleton loading where appropriate
-   - Add proper loading overlays for actions
-
-### Phase 9: Testing & Validation
-
-1. **Manual Testing**:
-   - Test all user interactions
-   - Verify theming in both light and dark modes
-   - Test responsive behavior on different screen sizes
-   - Verify accessibility features
-
-2. **Performance Validation**:
-   - Check widget rebuilds are optimized
-   - Verify no unnecessary re-renders
-   - Test smooth animations and transitions
-
-## Quality Checklist
-
-### Code Quality
-- [ ] Follows existing UI patterns exactly
-- [ ] Uses consistent naming conventions
-- [ ] Proper widget composition and reusability
-- [ ] No hardcoded values (use theme and l10n)
-- [ ] Consistent error handling
-
-### Theming & Design
-- [ ] Material 3 compliance
-- [ ] Dark/Light theme support
-- [ ] Consistent spacing and sizing
-- [ ] Proper color usage from theme
-- [ ] Responsive design implemented
-
-### Accessibility
-- [ ] Semantics labels added
-- [ ] Proper focus management
-- [ ] Sufficient color contrast
-- [ ] Touch targets minimum 48dp
-- [ ] Screen reader compatible
-
-### Integration
-- [ ] BlocBuilder/BlocConsumer properly implemented
-- [ ] Navigation working correctly
-- [ ] Loading states handled
-- [ ] Error states handled
-- [ ] Empty states handled
-
-## Channel Communication
-
-### Before Starting
-Update channel.md:
-```markdown
-### 🎨 UI Layer Status
-- **Status:** IN_PROGRESS
-- **Assigned Agent:** [YOUR_ID]
-- **Progress:** 0%
-```
-
-### During Development
-Update progress regularly:
-```markdown
-- **Progress:** [PERCENTAGE]%
-- **Files Created:** [LIST_OF_FILES]
-- **Next Steps:** [CURRENT_WORK]
-```
-
-### After Completion
-Mark as completed and unblock dependent layers:
-```markdown
-### 🎨 UI Layer Status
-- **Status:** COMPLETED
-- **Progress:** 100%
-- **Files Created:** [COMPLETE_LIST]
-
-### 🌍 Localization Status
-- **Blockers:** [] (UNBLOCKED)
-```
-
-## Dependencies
-
-### Must be completed first:
-- Architecture analysis
-
-### Enables after completion:
-- Localization layer
-- Integration layer (partial)
-
-## Output Deliverables
-
-1. **Main Screen**: `lib/presentation/screens/[feature]/[feature]_screen.dart`
-2. **Components**: `lib/presentation/screens/[feature]/components/*.dart`
-3. **Widgets** (if needed): `lib/presentation/screens/[feature]/widgets/*.dart`
-4. **Navigation Integration**: Updated route configuration
-5. **Updated Channel**: Progress and completion status in channel.md
-
-All UI components must be ready for localization (using l10n keys) and fully themed (supporting both light/dark modes).

package/flutter/punkt.claude/New Folder With Items/commands/git-commit.md

@@ -1,3 +0,0 @@
-Check the changes files and create a commit message for the changes. if needed and if several tasks or things are done do several commits.
-
-and also run the git commit cmd.

package/flutter/punkt.claude/New Folder With Items/commands/search-web.md

@@ -1 +0,0 @@
-Search the web for this: $ARGUMENTS and get the most relevant information that answers my query.

package/flutter/punkt.claude/punkt.claude/channel.md

@@ -1,225 +0,0 @@
-# Feature Development Channel
-
-This file coordinates parallel feature development across multiple layers. All feature development commands communicate through this channel.
-
-## Current Feature Status
-
-**Feature Name:** [NOT_SET]
-**Feature Description:** [NOT_SET]
-**Started:** [NOT_SET]
-**Status:** WAITING_FOR_INITIALIZATION
-
----
-
-## Layer Development Status
-
-### 🎨 UI Layer Status
-- **Status:** NOT_STARTED
-- **Assigned Agent:** NONE
-- **Progress:** 0%
-- **Dependencies:** 
-  - ✅ Architecture analysis completed
-  - ❌ UI components defined
-  - ❌ Screens implemented
-  - ❌ Navigation integrated
-- **Files Created:** []
-- **Next Steps:** []
-- **Blockers:** []
-
-### 🧠 Business Logic Layer Status
-- **Status:** NOT_STARTED  
-- **Assigned Agent:** NONE
-- **Progress:** 0%
-- **Dependencies:**
-  - ✅ Architecture analysis completed
-  - ❌ RiverPod providers defined
-  - ❌ Freezed state classes implemented
-  - ❌ Error handling with AsyncValue
-- **Files Created:** []
-- **Next Steps:** []
-- **Blockers:** []
-
-### 🏗️ Domain Layer Status
-- **Status:** NOT_STARTED
-- **Assigned Agent:** NONE
-- **Progress:** 0%
-- **Dependencies:**
-  - ✅ Architecture analysis completed
-  - ❌ Entities defined
-  - ❌ Repository interfaces created
-  - ❌ Business logic implemented
-- **Files Created:** []
-- **Next Steps:** []
-- **Blockers:** []
-
-### 💾 Data Layer Status
-- **Status:** NOT_STARTED
-- **Assigned Agent:** NONE
-- **Progress:** 0%
-- **Dependencies:**
-  - ❌ Domain layer completed
-  - ❌ Freezed DTOs with JSON annotations
-  - ❌ Mapper classes for DTO <-> Domain conversion
-  - ❌ Repository implementations
-  - ❌ Service locator updated
-- **Files Created:** []
-- **Next Steps:** []
-- **Blockers:** [WAITING_FOR_DOMAIN_LAYER]
-
-### 🌍 Localization Status
-- **Status:** NOT_STARTED
-- **Assigned Agent:** NONE
-- **Progress:** 0%
-- **Dependencies:**
-  - ❌ UI layer completed
-  - ❌ Translation keys identified
-  - ❌ All 5 languages updated
-  - ❌ Localization generated
-- **Files Created:** []
-- **Next Steps:** []
-- **Blockers:** [WAITING_FOR_UI_LAYER]
-
-### 🔧 Integration Status
-- **Status:** NOT_STARTED
-- **Assigned Agent:** NONE
-- **Progress:** 0%
-- **Dependencies:**
-  - ❌ All layers completed
-  - ❌ Service locator updated
-  - ❌ Navigation integrated
-  - ❌ Testing completed
-- **Files Created:** []
-- **Next Steps:** []
-- **Blockers:** [WAITING_FOR_ALL_LAYERS]
-
----
-
-## Shared Resources & Conventions
-
-### File Naming Conventions
-- **Feature Name Pattern:** `[feature_name]` (snake_case)
-- **Domain Model:** `[feature_name].dart` (in lib/domain/models/)
-- **Repository Interface:** `[feature_name]_repository.dart` (in lib/domain/repositories/)
-- **Repository Implementation:** `[feature_name]_repository_impl.dart` (in lib/data/repositories/)
-- **DTO:** `[feature_name]_dto.dart` (in lib/data/dtos/)
-- **Mapper:** `[feature_name]_mapper.dart` (in lib/data/mappers/)
-- **Provider:** `[feature_name]_provider.dart` (in lib/views/[feature]/providers/)
-- **State:** `[feature_name]_state.dart` (in lib/views/[feature]/providers/states/)
-- **Screen:** `[feature_name]_screen.dart` (in lib/views/[feature]/screens/)
-
-### Dependency Hierarchy
-```
-Integration Layer (Service Locator + Navigation)
-    ↑
-Localization Layer (ARB files + flutter gen-l10n)
-    ↑
-Presentation Layer (RiverPod Providers + Screens)
-    ↑           
-Data Layer (Freezed DTOs + Mappers + Repository Impls)
-    ↑           
-Domain Layer (Pure Dart Models + Repository Interfaces)
-```
-
-### Communication Protocol
-Each agent must:
-1. **Before starting:** Check dependencies and blockers
-2. **During work:** Update progress and files created
-3. **After completion:** Mark layer as COMPLETED and unblock dependent layers
-4. **On error:** Update blockers and notify dependent layers
-
-### Quality Checklist
-Each layer must verify:
-- ✅ DRY principle followed
-- ✅ Clean architecture compliance
-- ✅ Existing patterns followed
-- ✅ Error handling implemented
-- ✅ Logging added
-- ✅ Performance optimized
-
----
-
-## Feature Requirements Template
-
-### Functional Requirements
-- [TO_BE_FILLED_BY_DOMAIN_AGENT]
-
-### Technical Requirements
-- [TO_BE_FILLED_BY_DOMAIN_AGENT]
-
-### UI/UX Requirements
-- [TO_BE_FILLED_BY_UI_AGENT]
-
-### Data Requirements
-- [TO_BE_FILLED_BY_DATA_AGENT]
-
-### Integration Requirements
-- [TO_BE_FILLED_BY_INTEGRATION_AGENT]
-
----
-
-## Architecture Decisions
-
-### Design Patterns Used
-- [TO_BE_UPDATED_BY_AGENTS]
-
-### Services Required
-- [TO_BE_UPDATED_BY_AGENTS]
-
-### External Dependencies
-- [TO_BE_UPDATED_BY_AGENTS]
-
----
-
-## Issues & Solutions Log
-
-### Current Issues
-- None
-
-### Resolved Issues
-- None
-
----
-
-## Final Deliverables Checklist
-
-### Code Quality
-- [ ] All code follows existing patterns
-- [ ] No code duplication
-- [ ] Proper error handling
-- [ ] Comprehensive logging
-- [ ] Performance optimized
-
-### Functionality
-- [ ] All requirements implemented
-- [ ] Edge cases handled
-- [ ] Loading states implemented
-- [ ] Error states implemented
-
-### Integration
-- [ ] Service locator updated
-- [ ] Navigation working
-- [ ] State management working
-- [ ] API integration working
-
-### Localization
-- [ ] All text localized (5 languages)
-- [ ] No static text in code
-- [ ] Localization generated
-- [ ] RTL support (Arabic)
-
-### Themes
-- [ ] Dark theme support
-- [ ] Light theme support
-- [ ] Material 3 compliance
-- [ ] Responsive design
-
-### Testing
-- [ ] Manual testing completed
-- [ ] Error scenarios tested
-- [ ] Performance verified
-- [ ] Multi-language tested
-
----
-
-**Last Updated:** [AUTO_TIMESTAMP]
-**Next Review:** [TO_BE_SET]

package/flutter/punkt.claude/punkt.claude/commands/add-translations.md

@@ -1,60 +0,0 @@
-# Add Translations Command
-
-Add new translation keys to all supported languages in the AiGo app (English, German, Russian, Turkish, Arabic).
-
-**Usage:** `add-translations`
-
-This command redirects to the comprehensive translation management system. Use the `manage-translations` command instead for full functionality:
-
-```bash
-manage-translations add --key "feature.key" --en "English" --de "German" --ru "Russian" --tr "Turkish" --ar "Arabic"
-```
-
-## Quick Translation Addition
-
-For quick addition of new translation keys, follow this process:
-
-1. **Add to English template** (`lib/l10n/app_en.arb`):
-   ```json
-   {
-     "newFeatureTitle": "New Feature",
-     "@newFeatureTitle": {
-       "description": "Title for the new feature screen"
-     }
-   }
-   ```
-
-2. **Add to all other languages**:
-   - German (`app_de.arb`): `"newFeatureTitle": "Neue Funktion"`
-   - Russian (`app_ru.arb`): `"newFeatureTitle": "Новая функция"`
-   - Turkish (`app_tr.arb`): `"newFeatureTitle": "Yeni Özellik"`
-   - Arabic (`app_ar.arb`): `"newFeatureTitle": "ميزة جديدة"`
-
-3. **Generate localization files**:
-   ```bash
-   flutter gen-l10n
-   ```
-
-4. **Use in code**:
-   ```dart
-   Text(context.l10n.newFeatureTitle)
-   ```
-
-## Supported Languages
-
-- **English (en)** - Primary language, always complete
-- **German (de)** - German translation
-- **Russian (ru)** - Russian translation  
-- **Turkish (tr)** - Turkish translation
-- **Arabic (ar)** - Arabic translation with RTL support
-
-## See Also
-
-Use `manage-translations` command for comprehensive translation management including:
-- Adding new translations
-- Updating existing translations
-- Validating completeness
-- Generating localization files
-- Extracting hardcoded strings
-
-For detailed usage, see: `manage-translations --help`

package/flutter/punkt.claude/punkt.claude/commands/bug-fix.md

@@ -1,32 +0,0 @@
-Run analyse diagnostic and check if there are build errors.
-
-Fix them all in every file - fix them properly without simplyfing and without creating redundant code, classes, files, methods. 
-Also dont replace translated keys or values with static textes to fix the error. Instead add properly the language keys in folder @l10n
-
-Check if classes, methods and so on already exists and reuse as much methods and widgets and classes as possible.
-
-Follow Dry, Solid and clean code rules and best practise for current archtitecture and project  implementation ( in this case Flutter + riverpod+ firebase etc).
-
-Also make sure that there are never unused methods, functions, imports or variables in the classes you fix.
-
-AND VERY IMPORTANT: Use the same style of development as it is at the momment - Same folder, file, class, method, variable name, indentation, spacing etc. It needs to be as from one developer and one style not 10 differnt devs working on one app.
-
-1. First think through the problem, read the codebase for relevant files, and write a plan to tasks/todo.md.
-2.The plan should have a list of todo items that you can
-check off as you complete them
-3. Before you begin working, check in with me and I will verify the plan.
-4. Then, begin working on the todo items, marking them as complete as you go.
-5. Please every step of the way just give me a high level explanation of what changes you made
-6. Make every task and code change you do as simple as possible. We want to avoid making any massive or complex changes. Every change should impact as little code as possible. Everything is about simplicity.
-7. Finally, add a review section to the todo.md file with a summary of the changes you made and any other relevant information.
-8. After every fully finished tasks ( main task) - make a git commit - generate a proper understanding message
-
-Keep going until the job is completely solved before ending your turn
-
-If you’re unsure about the code or files, open them - dont hallucinate.
-
-Plan thoroughly before every tool call and reflect on the outcome after.
-
-Repeat the task as long as needed till its fully functional and cleanly implemented - dont add unnessacry codes - before adding new code check if it exists and extend the exisiting one.
-
-Use the Following MCPs: Context7,  memory, sequential-thinking