Update azure_ai.py

azure_ai.py

@@ -18,19 +18,10 @@ def enhance_with_ai(repo_info):
 
     system_prompt = """You are a senior open-source developer and technical writer who has authored
 documentation for projects with 50,000+ GitHub stars (e.g., FastAPI, LangChain, Streamlit).
-
 Your README output must:
 - Feel like a polished, production-grade open-source project
 - Use Mermaid diagrams: sequenceDiagram for API/data flow, flowchart LR for architecture. 
 - In Mermaid Diagrams, Dont use any Use only text dont use any symbol like .,*£_-+()/ and HTML tags in Mermaid and Follow correct Mermaid Syntax
-- When using architecture-beta:
-  - Start with: architecture-beta
-  - Define groups using: group <id>(<icon>)[<label>]
-  - Define services using: service <id>(<icon>)[<label>] in <group>
-  - Connect services using directional edges:
-    serviceA:R --> L:serviceB
-  - Always include direction markers: R, L, T, B
-  - Do not mix flowchart syntax with architecture-beta
 - Mermaid diagrams should change according to project working refer the sample one present in user input
 - Include shields.io badges, tables, and collapsible sections where appropriate
 - Be scannable: a developer should understand the project in under 60 seconds
@@ -39,54 +30,38 @@ Your README output must:
 
     user_prompt = f"""
 Generate a world-class GitHub README.md for this project.
-
 PROJECT CONTEXT
 ---------------
 Name        : {repo_info['name']}
 Description : {repo_info['description']}
 Topics      : {', '.join(repo_info['topics'])}
 User        : {repo_info['owner']['login']}
-
 FILES (sampled for context):
 {file_summaries}
 ---------------
-
 Follow this EXACT structure and do not skip any section:
-
 1. Hero Section
    - H1 title with a one-line tagline below it
    - A short 2-line summary of what the project does
-
 2. Table of Contents
    - Linked TOC to every section
-
 3. Introduction
    - The problem this project solves (2-3 sentences)
    - Who benefits from it
    - A "Why {repo_info['name']}?" comparison table vs alternatives:
      | Feature | {repo_info['name']} | Alternative A | Alternative B |
-
 4. Features
    - 6-8 bullet points, each starting with a relevant emoji
    - Group under: Core Features, Developer Experience, Deployment
-
 5. Architecture
    - A Mermaid flowchart LR showing system components:
      ```mermaid
-    architecture-beta
-    
-    group system(server)[System]
-    
-    service input(server)[Input Layer] in system
-    service processing(server)[Processing Layer] in system
-    service output(server)[Output Layer] in system
-    
-    input:R --> L:processing
-    processing:R --> L:output
+     flowchart LR
+         A[Input Layer] --> B[Processing Layer]
+         B --> C[Output Layer]
      ```
    - A component breakdown table after the diagram:
      | Component | Role | Technology |
-
 6. Workflow
    - A Mermaid sequenceDiagram showing the request/response or data flow:
      ```mermaid
@@ -100,10 +75,8 @@ Follow this EXACT structure and do not skip any section:
          App-->>User: result
      ```
    - Numbered step-by-step explanation below the diagram
-
 7. Tech Stack
    | Layer | Technology | Purpose |
-
 8. Installation
    - Prerequisites block
    - Quick Start in 3 steps max:
@@ -127,7 +100,6 @@ Follow this EXACT structure and do not skip any section:
 10. Usage
    - Basic example with code block
    - Advanced example with code block
-
     
 Write the complete README now. Do not summarize, skip, or truncate any section.
 """