appiq-solution 1.4.8 → 1.4.9

package/flutter/CLAUDE.md

@@ -1,58 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Development Commands
-
-IMPORTANT FOLLOW THIS RULES:
-
-## Standard Workflow
-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 all mcps that are needed for the tasks - check the github pages provided here how and when to use it: 
-fetcher - https://github.com/jae-jae/fetcher-mcp 
-sequential-thinking - https://github.com/modelcontextprotocol/servers/tree/main/src/sequentialthinking 
-memory - https://hub.docker.com/r/mcp/memory 
-context7 - https://github.com/upstash/context7
-puppeteer - https://github.com/merajmehrabi/puppeteer-mcp-server 
-
-## THIS RULES ARE IMPORTANT AND YOU NEED FOLLOW THEM ALWAYS!!!!!
-
-🧹 DRY-Prinzip befolgt - Keine Code-Duplikation mehr
-📖 Bessere Lesbarkeit - Kleinere, fokussierte Methoden
-🔧 Wartbarkeit - Logische Gruppierung ähnlicher Funktionen
-⚡ Performance - Weniger redundante Repository-Calls
-🧪 Testbarkeit - Kleinere, testbare Methoden-Einheiten
-
-1. **Architecture**: Follows Clean Architecture with proper layer separation
-2. **Localization**: All text supports multi-language
-3. **Quality**: Passes all 5 quality criteria (DRY, Readable, Maintainable, Performant, Testable)
-4. **Documentation**: Code is properly documented with examples
-8. **Consistency**: Code style matches existing patterns
-
-Follow the best clean code rules and the best practices. Implement Code the same style as the archtitecuter is build up - follow the folder and file strucutre.
-
-When implementing new features:
-
-1. **First**: Check existing code for similar patterns
-2. **Second**: Review these coding rules
-3. **Third**: Ensure all validation criteria are met
-4. **Finally**: Implement with confidence following established patterns
-
-> **Remember**: Consistency is key. When in doubt, follow existing patterns in the codebase.

package/flutter/punkt.claude/New Folder With Items/channel.md

@@ -1,221 +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
-  - ❌ State classes defined
-  - ❌ Cubit implementation
-  - ❌ Error handling implemented
-- **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
-  - ❌ Models implemented
-  - ❌ Repository implementations
-  - ❌ Data sources created
-- **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)
-- **Entity:** `[feature_name]_entity.dart`
-- **Repository Interface:** `[feature_name]_repository.dart`
-- **Repository Implementation:** `[feature_name]_repository_impl.dart`
-- **Model:** `[feature_name]_model.dart`
-- **Cubit:** `[feature_name]_cubit.dart`
-- **State:** `[feature_name]_state.dart`
-- **Screen:** `[feature_name]_screen.dart`
-
-### Dependency Hierarchy
-```
-Integration Layer
-    ↑
-Localization Layer
-    ↑
-UI Layer ← Business Logic Layer
-    ↑           ↑
-Data Layer ← Domain Layer
-```
-
-### 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/New Folder With Items/commands/add-translations.md

@@ -1,12 +0,0 @@
-If the project is a flutter project:
-1. Search where the localization is implemented in. Either its an l10n folder or you have the *.arb files
-2. Extend the arb files of all langauges en,de,ru,tr,ar by the missing translations 
-3. run the cmd to generate the new localization files: flutter gen-l10n
-4. Make sure that all the screens, variable initialization and so on has multilanguage support.
-5. Make sure we dont have static text in the code.
-
-If the project is a react project:
-1. Search where the localization is implemented in. Either its in a dictonary folder or you have the *.json files
-2. Extend the arb files of all langauges en,de,ru,tr,ar by the missing translations 
-3. Make sure that all the screens, variable initialization and so on has multilanguage support.
-4. Make sure we dont have static text in the code.

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

@@ -1,168 +0,0 @@
-# Create Complete Feature Command - Parallel Orchestrator
-
-Orchestrates parallel feature development across multiple specialized agents using the VoicePilot architecture.
-
-**Usage:** `create-feature [FEATURE_NAME] [FEATURE_DESCRIPTION]`
-
-**Example:** `create-feature project-favorites "Allow users to mark projects as favorites and view them in a separate list"`
-
-## ⚡ Parallel Development System
-
-This command orchestrates multiple specialized agents that work in parallel through a central communication channel. Each agent handles a specific layer while coordinating dependencies through `/Users/vapps-it/Projects/voicepilot/.claude/channel.md`.
-
-## 🚀 Parallel Execution Workflow
-
-### Step 1: Initialize Channel
-```bash
-# Initialize the communication channel
-1. Update channel.md with feature details
-2. Set all layers to "NOT_STARTED" 
-3. Define feature requirements and dependencies
-```
-
-### Step 2: Launch Parallel Agents
-Execute these commands **simultaneously** in separate Claude conversations:
-
-#### 🏗️ Domain Layer (Independent - Start First)
-```bash
-feature-domain-layer [FEATURE_NAME] "[FEATURE_DESCRIPTION]"
-```
-- Creates entities and repository interfaces
-- Defines business logic and failure types
-- **No dependencies** - can start immediately
-
-#### 🎨 UI Layer (Independent - Start First) 
-```bash
-feature-ui-layer [FEATURE_NAME] "[FEATURE_DESCRIPTION]"
-```
-- Creates screens, components, and widgets
-- Implements theming and responsive design
-- **No dependencies** - can start immediately
-
-#### 🧠 Business Logic (Coordinates with Domain)
-```bash
-feature-business-logic [FEATURE_NAME] "[FEATURE_DESCRIPTION]"
-```
-- Creates cubits and state management
-- **Coordinates with Domain layer** through channel
-- Starts immediately but adapts to domain interfaces
-
-#### 💾 Data Layer (Waits for Domain)
-```bash
-feature-data-layer [FEATURE_NAME] "[FEATURE_DESCRIPTION]"
-```
-- Creates models, data sources, repository implementations
-- **Waits for Domain layer completion** (checks channel status)
-- Auto-starts when Domain layer marks as "COMPLETED"
-
-#### 🌍 Localization (Waits for UI)
-```bash
-feature-localization [FEATURE_NAME] "[FEATURE_DESCRIPTION]"
-```
-- Adds translations for all 5 languages (en, de, ru, tr, ar)
-- **Waits for UI layer completion** (needs all text content)
-- Auto-starts when UI layer marks as "COMPLETED"
-
-#### 🔧 Integration (Waits for All)
-```bash
-feature-integration [FEATURE_NAME] "[FEATURE_DESCRIPTION]"
-```
-- Connects all layers and updates service locator
-- **Waits for ALL other layers** to complete
-- Final integration and testing phase
-
-### Step 3: Monitor Progress
-Each agent updates the channel with:
-- Current status and progress percentage
-- Files created and dependencies resolved
-- Blockers and completion notifications
-
-### Step 4: Automatic Coordination
-- **Domain completes** → Unblocks Data Layer
-- **UI completes** → Unblocks Localization  
-- **All complete** → Unblocks Integration
-- **Integration completes** → Feature ready for production
-
-## 📋 Agent Communication Protocol
-
-### Channel Status Updates
-Each agent must:
-1. **Check channel** before starting work
-2. **Update progress** regularly during development  
-3. **Mark completion** and unblock dependent layers
-4. **Report blockers** if dependencies are missing
-
-### Dependency Chain
-```
-Integration Layer (waits for all)
-    ↑
-Localization ← UI Layer (parallel start)
-    ↑           ↑
-Data Layer  ← Domain Layer (parallel start)
-    ↑           ↑
-Business Logic Layer (coordinates with both)
-```
-
-## 🎯 Execution Example
-
-For feature "project-favorites":
-
-1. **Launch simultaneously:**
-   - Agent A: `feature-domain-layer project-favorites "Favorite projects functionality"`
-   - Agent B: `feature-ui-layer project-favorites "Favorite projects functionality"`  
-   - Agent C: `feature-business-logic project-favorites "Favorite projects functionality"`
-
-2. **Auto-triggered when dependencies complete:**
-   - Agent D: `feature-data-layer` (starts when Domain completes)
-   - Agent E: `feature-localization` (starts when UI completes)
-
-3. **Final integration:**
-   - Agent F: `feature-integration` (starts when all layers complete)
-
-## ⚡ Performance Benefits
-
-- **5-6x faster development** through parallel execution
-- **Reduced waiting time** with automatic dependency resolution
-- **Consistent quality** through specialized agent expertise
-- **Real-time coordination** prevents conflicts and overwrites
-- **Automatic integration** ensures all pieces fit together perfectly
-
-## Implementation Guidelines
-
-### Code Style Requirements
-- Follow existing naming conventions exactly
-- Use identical code formatting and structure
-- Implement the same error handling patterns
-- Follow the exact file organization structure
-- Use the same design patterns throughout
-
-### Architecture Compliance
-- **Clean Architecture**: Maintain strict layer separation
-- **SOLID Principles**: Follow all SOLID principles
-- **DRY Principle**: Reuse existing code and patterns
-- **Performance**: Use existing optimization patterns
-- **Maintainability**: Follow existing maintainability practices
-
-### Quality Criteria
-Every feature must meet these 5 quality criteria:
-1. **🧹 DRY-Prinzip**: No code duplication
-2. **📖 Readability**: Clean, understandable code with proper documentation
-3. **🔧 Maintainability**: Logical grouping and easy to modify
-4. **⚡ Performance**: Optimized for performance following existing patterns
-5. **🧪 Testability**: Easily testable with proper separation of concerns
-
-### Multi-language & Theme Support
-- **Localization**: All text must be in L10n (de, en, ru, tr, ar)
-- **Dark/Light Mode**: Full support for both themes
-- **Material 3**: Consistent with existing Material 3 implementation
-- **Accessibility**: Follow existing accessibility patterns
-
-## Execution Process
-
-1. **Create TODO List**: Break down the feature into specific, trackable tasks
-2. **Follow Architecture**: Implement each layer following the exact existing patterns
-3. **Reuse Components**: Maximize reuse of existing core utilities and services
-4. **Test Thoroughly**: Verify all aspects work correctly
-5. **Document Changes**: Provide clear summary of what was implemented
-
-The end result should be a feature that looks and feels like it was built by the same developer who built the rest of the application, following identical patterns and maintaining perfect consistency with the existing codebase.

package/flutter/punkt.claude/New Folder With Items/commands/explain-codebase.md

@@ -1 +0,0 @@
-Scan out the whole codebase and explain it to me in an easy way that allows me to understand how it functions and how everthing is connected.