How nikk-666/solutionchallenge works
Main Components
• Frontend: This includes the user interface built with HTML, CSS, and JavaScript. The structure under the “frontend” directory shows multiple pages (index, login, signup, door, questions) and a rich interactive simulation component, with “src” organizing the game-like or simulation elements (scenes, entities, UI components) and “assets” storing maps and JSON configurations.
• Backend: Located under “backend”, this consists of the Flask application (app.py), model scripts (model.py, model_train.py), and supporting data/model files (career_model.csv, career_model.pkl). This layer is responsible for processing the psychological assessment inputs and initiating AI-driven career recommendations.
• Database & Cloud Services: According to the README, the project integrates with Firebase/Firestore and Google Cloud Services for hosting and data processing, even if the explicit configuration files for these are not visible.
• External AI Service: The integration with Gemini AI forms an external service piece that processes the recommendations.
Inter-Relationships
• The Frontend communicates with the Backend via HTTP requests (API endpoints hosted on Flask), sending user responses from assessment/questionnaire forms.
• The Backend processes these inputs using AI models (the trained model stored in career_model.pkl) and may perform further computations or data retrieval via Firebase/Firestore.
• The Backend then sends processed recommendations back to the Frontend.
• The Frontend uses its interactive scenes and UI components to display career simulation and recommendations; it utilizes libraries (such as kaboom.js indicated by kaboom.mjs) to provide dynamic visualizations and immersive interactions.
• External services such as Gemini AI are invoked by the Backend to enhance the recommendation capabilities.
Architectural Patterns and Design Principles
• Full-stack separation: A clear division between frontend (client-side interactive simulation and UI) and backend (API server with Flask logic and AI processing).
• Modular Design: The frontend is organized into modular components (scenes, entities, states, UI components), which aligns with modern front-end practices.
• Integration Points: The system has external connectivity with Google Cloud & Firebase and integration with Gemini AI.
• Data Flow: User inputs flow from the frontend to backend; AI processing and database accesses occur on the backend; recommendations are then delivered back to the frontend.
• Do the same for the Backend: API Server (Flask), Model Processing, and Data Handling.
• Annotations or legends to explain architectural patterns (modular design, separation of concerns) and the key technologies (Flask, Firebase, Gemini AI, kaboom.js).
Happy Diagramming!