# TRUSTHIRE — CONTINUE DEVELOPMENT MASTER INSTRUCTION ## From Initial Android UI to a Real Working MVP You have already created the initial TrustHire Android application. The existing implementation includes: - Welcome screen - Home screen - Job detail screen - Initial navigation architecture - Jetpack Compose UI components - Theme and color configuration - Models and ViewModel foundation - Adaptive application icon The previous build reported successful compilation. **Now your task is to continue this existing project and transform it into a real, functional TrustHire MVP.** Do not restart the project from zero. Do not unnecessarily redesign working components. Do not simply generate additional screens. Build actual functionality. --- ## 1. READ THE COMPLETE PRODUCT SPECIFICATION Use the provided document: TRUSTHIRE — ULTIMATE MASTER PROMPT Read and understand its complete requirements. It contains 111 sections covering the product vision, user roles, features, AI systems, security, database, architecture, MVP and future roadmap. Treat it as the primary product specification. Do not randomly invent new features. Do not remove important requirements. Clearly distinguish: - MVP - Post-MVP Phase 1 - Post-MVP Phase 2 - Post-MVP Phase 3 Your immediate objective is the MVP, not all 111 sections simultaneously. ## 2. INSPECT THE EXISTING CODEBASE Before changing anything, inspect every existing project file. Especially: - app/build.gradle.kts - settings.gradle.kts - MainActivity.kt - MainViewModel.kt - Models.kt - AppNavigation.kt - Components.kt - WelcomeScreen.kt - HomeScreen.kt - JobDetailScreen.kt - Theme.kt - Color.kt - Type.kt Determine: - What already works - What is only visual - What uses temporary data - What is connected to real services - What is incomplete - What is broken Preserve working functionality. Do not duplicate existing screens or navigation. ## 3. TECHNICAL ARCHITECTURE Current workspace: Android application. Continue with the existing Kotlin + Jetpack Compose architecture. Keep the code modular: app/ ├── data/ │ ├── models/ │ ├── repositories/ │ ├── remote/ │ └── local/ ├── domain/ │ ├── models/ │ └── usecases/ ├── ui/ │ ├── components/ │ ├── navigation/ │ ├── screens/ │ └── theme/ ├── viewmodel/ ├── core/ │ ├── network/ │ ├── auth/ │ └── security/ └── MainActivity.kt Backend architecture must follow the master specification: - Node.js - NestJS or modular Express - PostgreSQL - Secure API architecture - Python/FastAPI AI service where appropriate IMPORTANT: Do not silently replace the specified backend architecture with Firebase or a different database. The current Android workspace must not be assumed to support running a complete production backend. Inspect its actual capabilities. If backend implementation is possible, build and test it. Otherwise create proper API contracts and integration boundaries and report what still requires a separate backend environment.
# TRUSTHIRE — CONTINUE DEVELOPMENT MASTER INSTRUCTION ## From Initial Android UI to a Real Working MVP You have already created the initial TrustHire Android application. The existing implementation includes: - Welcome screen - Home screen - Job detail screen - Initial navigation architecture - Jetpack Compose UI components - Theme and color configuration - Models and ViewModel foundation - Adaptive application icon The previous build reported successful compilation. **Now your task is to continue this existing project and transform it into a real, functional TrustHire MVP.** Do not restart the project from zero. Do not unnecessarily redesign working components. Do not simply generate additional screens. Build actual functionality. --- ## 1. READ THE COMPLETE PRODUCT SPECIFICATION Use the provided document: TRUSTHIRE — ULTIMATE MASTER PROMPT Read and understand its complete requirements. It contains 111 sections covering the product vision, user roles, features, AI systems, security, database, architecture, MVP and future roadmap. Treat it as the primary product specification. Do not randomly invent new features. Do not remove important requirements. Clearly distinguish: - MVP - Post-MVP Phase 1 - Post-MVP Phase 2 - Post-MVP Phase 3 Your immediate objective is the MVP, not all 111 sections simultaneously. ## 2. INSPECT THE EXISTING CODEBASE Before changing anything, inspect every existing project file. Especially: - app/build.gradle.kts - settings.gradle.kts - MainActivity.kt - MainViewModel.kt - Models.kt - AppNavigation.kt - Components.kt - WelcomeScreen.kt - HomeScreen.kt - JobDetailScreen.kt - Theme.kt - Color.kt - Type.kt Determine: - What already works - What is only visual - What uses temporary data - What is connected to real services - What is incomplete - What is broken Preserve working functionality. Do not duplicate existing screens or navigation. ## 3. TECHNICAL ARCHITECTURE Current workspace: Android application. Continue with the existing Kotlin + Jetpack Compose architecture. Keep the code modular: app/ ├── data/ │ ├── models/ │ ├── repositories/ │ ├── remote/ │ └── local/ ├── domain/ │ ├── models/ │ └── usecases/ ├── ui/ │ ├── components/ │ ├── navigation/ │ ├── screens/ │ └── theme/ ├── viewmodel/ ├── core/ │ ├── network/ │ ├── auth/ │ └── security/ └── MainActivity.kt Backend architecture must follow the master specification: - Node.js - NestJS or modular Express - PostgreSQL - Secure API architecture - Python/FastAPI AI service where appropriate IMPORTANT: Do not silently replace the specified backend architecture with Firebase or a different database. The current Android workspace must not be assumed to support running a complete production backend. Inspect its actual capabilities. If backend implementation is possible, build and test it. Otherwise create proper API contracts and integration boundaries and report what still requires a separate backend environment.
Created using ChatSlide
This project focuses on enhancing the existing MVP foundation by auditing its code and mapping requirements to current capabilities. It aims to build a robust TrustHire core by integrating Compose flows with secure authentication and defining technical boundaries. Finally, it emphasizes validating user journeys, prioritizing features, and extending the MVP based on measurable readiness criteria.