# dhananjay-97/resumeconverter architecture

> Architecture diagram of the GitHub repository dhananjay-97/resumeconverter, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-04-10). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/dhananjay-97/resumeconverter
- Repository: https://github.com/dhananjay-97/resumeconverter

## Overview

##### Main Components
- Frontend/User Interface: Represented by streamlit_app.py. This module likely handles the user interactions, capturing resume data either through file uploads or text input.
- Backend Logic:
- main.py acts as a central module that orchestrates the resume conversion.
- prompt_manager.py likely handles dynamic prompt generation, especially if the conversion involves AI/LLM based processing.
- Data Structures and Validation: schemas.py provides the data models or validation schemas to ensure that resume data is structured correctly.
- Configuration: .env holds environment variables (for example, API keys or configuration settings) used by the application.
- Dependencies: requirements.txt lists all external libraries; while not a runtime component, it’s important for understanding the technology stack (possibly including libraries for HTTP calls, data manipulation, etc.).

##### Relationships and Interactions
- User Interaction Flow: Users interact with the front-end (streamlit_app.py) where they input or upload their resume.
- UI to Backend: The Streamlit interface forwards the data to the backend logic (main.py), which likely performs pre-processing, calls the prompt_manager to generate or manipulate prompts, and then processes the output.
- Data Validation: As resumes are transferred between layers, schemas.py validates or transforms the data ensuring consistency.
- Configuration Use: Both main.py and prompt_manager.py read configuration data from the .env file.

##### Architectural Patterns and Design Principles
- Modular Design: The separation between streamlit_app.py (UI) and the backend modules (main.py and prompt_manager.py) promotes a clean separation of concerns.
- Data Validation: Use of schemas.py underscores a commitment to data integrity.
- Config-driven: The use of an environment file (.env) for configuration means the application is designed to be flexible across multiple deployment environments.

## Diagram (Mermaid)

```mermaid
flowchart TD
    U["User"]:::user
    U -->|"submits resume"| FE["Streamlit Frontend"]:::frontend

    subgraph "Backend Logic"
        MA["Main Orchestrator"]:::backend
        PM["Prompt Manager"]:::backend
    end

    FE -->|"passes data"| MA
    MA -->|"generates prompt"| PM
    MA -->|"validates data"| SC["Schema Validator"]:::schema
    PM -->|"validates data"| SC

    EC["Environment Config"]:::config
    EC --- MA
    EC --- PM

    DEP["Dependencies"]:::dependency

    %% Click Events
    click FE "https://github.com/dhananjay-97/resumeconverter/blob/main/streamlit_app.py"
    click MA "https://github.com/dhananjay-97/resumeconverter/blob/main/main.py"
    click PM "https://github.com/dhananjay-97/resumeconverter/blob/main/prompt_manager.py"
    click SC "https://github.com/dhananjay-97/resumeconverter/blob/main/schemas.py"
    click EC "https://github.com/dhananjay-97/resumeconverter/blob/main/.env"
    click DEP "https://github.com/dhananjay-97/resumeconverter/blob/main/requirements.txt"

    %% Styles
    classDef user fill:#B0E0E6,stroke:#333,stroke-width:2px
    classDef frontend fill:#ADD8E6,stroke:#333,stroke-width:2px
    classDef backend fill:#90EE90,stroke:#333,stroke-width:2px
    classDef schema fill:#FFD700,stroke:#333,stroke-width:2px
    classDef config fill:#FFA500,stroke:#333,stroke-width:2px
    classDef dependency fill:#D3D3D3,stroke:#333,stroke-width:2px
```
