# meet-tecmantras/automating_project_development_and_planing architecture

> Architecture diagram of the GitHub repository meet-tecmantras/automating_project_development_and_planing, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-05-22). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/meet-tecmantras/automating_project_development_and_planing
- Repository: https://github.com/meet-tecmantras/automating_project_development_and_planing

## Overview

##### Project type and purpose
- It is not a full-stack web app or microservices ecosystem; it is a single-process Python automation script with two entrypoints (newgeminiapp.py and newllama.py).

##### File structure
- Top-level files:
- newgeminiapp.py – entrypoint for the Gemini-based workflow
- newllama.py – entrypoint for the Llama-based workflow
- requirements.txt – Python dependencies (e.g., google-api-client, llama-cpp-python, click, etc.)
- README.md – high-level project description
- There are no directories for “frontend,” “backend,” or “database,” which tells us that the system is a CLI tool that interacts with external AI services/libraries.

##### README for additional insights
- The README indicates the objective: “Automating Project Development & Planning.”

a. Main components
1. CLI Interface
– Represents how an end-user invokes the tool (e.g., via command line arguments).
2. Orchestration Layer
– The Python scripts (newgeminiapp.py / newllama.py) containing the core logic: parsing inputs, formatting prompts, handling responses.
3. AI/LLM Service Layer
– Gemini API (external HTTP service)
– Llama model (local or library call)
4. Optional: Logging / Persistence
b. Relationships and interactions
– The user issues a CLI command → CLI Interface parses it → calls the Orchestration Layer
– Orchestration Layer determines which model to use → sends prompt to Gemini via REST (newgeminiapp.py) or to Llama via library call (newllama.py)
– AI Service returns a response → Orchestration Layer processes and prints/output it back to the console or writes to log
c. Architectural patterns and design principles
– Single-process, single-responsibility scripts
– Clear separation between “input-parsing,” “prompt orchestration,” and “model invocation”
– Dependency isolation via requirements.txt
d. Technologies, frameworks, or libraries
– Python 3.x
– google-api-client or similar for Gemini
– llama-cpp-python or equivalent for Llama
– click or argparse for CLI
– logging or JSON for persistence (if used)

##### Detailed capture of essential elements
- Configuration (e.g., environment variables for API keys in newgeminiapp.py).

## Diagram (Mermaid)

```mermaid
flowchart TD
    User["User"]:::user

    subgraph "Core Workflows"
        GeminScript["Orchestration: newgeminiapp.py"]:::process
        LlamaScript["Orchestration: newllama.py"]:::process
    end

    User --> GeminScript
    User --> LlamaScript

    GeminScript -->|"prompt text"| GeminiAPI["Gemini API Service"]:::external
    GeminiAPI -->|"API response"| GeminScript
    LlamaScript -->|"prompt text"| LlamaModel["Llama Model (Local Invocation)"]:::external
    LlamaModel -->|"inference result"| LlamaScript

    GeminScript --> Console["Console Output"]:::output
    LlamaScript --> Console
    GeminScript --> Log["Log Store / Output File"]:::storage
    LlamaScript --> Log

    subgraph "Docs & Config"
        README["README.md"]:::storage
        REQS["requirements.txt"]:::storage
    end

    click GeminScript "https://github.com/meet-tecmantras/automating_project_development_and_planing/blob/main/newgeminiapp.py"
    click LlamaScript "https://github.com/meet-tecmantras/automating_project_development_and_planing/blob/main/newllama.py"
    click README "https://github.com/meet-tecmantras/automating_project_development_and_planing/blob/main/README.md"
    click REQS "https://github.com/meet-tecmantras/automating_project_development_and_planing/blob/main/requirements.txt"

    classDef user fill:#9f6,stroke:#333,color:#000
    classDef process fill:#6cf,stroke:#333,color:#000
    classDef external fill:#f96,stroke:#333,color:#000
    classDef storage fill:#ccf,stroke:#333,color:#000
    classDef output fill:#cfc,stroke:#333,color:#000
```
