Add initial mobile app prototypes and staff payments feature

Introduces the first versions of client and staff mobile application prototypes, including platform-specific assets, screens, and configuration for Android, iOS, macOS, Linux, and Windows. Adds documentation, AI prompt guides, and a new staff payments feature module with repository, use cases, and presentation logic. Also includes generated localization files and supporting resources for both client and staff apps.

apps/mobile/ai_prompts/1-architecture-scaffolding.md

@@ -0,0 +1,54 @@
+TASK: Create the KROW Flutter monorepo skeleton using Melos.
+
+You must:
+1. Create the directory structure exactly as defined below (some of the parts are already developed)
+2. Initialize Melos  (some of the parts are already developed)
+3. Create minimal pubspec.yaml files where required  (some of the parts are already developed)
+4. Do NOT add application logic
+5. Do NOT generate Flutter apps yet (basic strcuture of the apps/ are developed)
+
+Target structure:
+
+root/
+├── apps/
+│   ├── client/
+│   ├── staff/
+│   └── design_system_viewer/
+│
+├── packages/
+│   ├── core/
+│   ├── design_system/
+│   ├── domain/
+│   ├── data_connect/
+│   └── features/
+│      ├─ domain/
+│      │  ├─ repositories/
+│      │  └─ usecases/
+│      │
+│      ├─ data/
+│      │  ├─ datasources/
+│      │  └─ repositories_impl/
+│      │
+│      ├─ presentation/
+│      │  ├─ state/
+│      │  ├─ pages/
+│      │  └─ widgets/
+│      │
+│      └─ feature_manifest.md
+├── docs/
+└── dataconnect/
+
+Rules:
+- Use Flutter 3.x compatible setup
+- All packages must be melos-aware
+- Keep pubspec files minimal
+- No dependencies unless required for structure
+- No example widgets or boilerplate UI
+
+Output:
+- melos.yaml
+- Folder tree
+- Minimal pubspec.yaml per package/app
+- Short explanation of dependency boundaries
+
+Do NOT proceed beyond skeleton creation.