Spaces:
Sleeping
Sleeping
Update azure_ai.py
Browse files- azure_ai.py +18 -3
azure_ai.py
CHANGED
|
@@ -23,6 +23,14 @@ Your README output must:
|
|
| 23 |
- Feel like a polished, production-grade open-source project
|
| 24 |
- Use Mermaid diagrams: sequenceDiagram for API/data flow, flowchart LR for architecture.
|
| 25 |
- In Mermaid Diagrams, Dont use any Use only text dont use any symbol like .,*£_-+()/ and HTML tags in Mermaid and Follow correct Mermaid Syntax
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 26 |
- Mermaid diagrams should change according to project working refer the sample one present in user input
|
| 27 |
- Include shields.io badges, tables, and collapsible sections where appropriate
|
| 28 |
- Be scannable: a developer should understand the project in under 60 seconds
|
|
@@ -65,9 +73,16 @@ Follow this EXACT structure and do not skip any section:
|
|
| 65 |
5. Architecture
|
| 66 |
- A Mermaid flowchart LR showing system components:
|
| 67 |
```mermaid
|
| 68 |
-
|
| 69 |
-
|
| 70 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 71 |
```
|
| 72 |
- A component breakdown table after the diagram:
|
| 73 |
| Component | Role | Technology |
|
|
|
|
| 23 |
- Feel like a polished, production-grade open-source project
|
| 24 |
- Use Mermaid diagrams: sequenceDiagram for API/data flow, flowchart LR for architecture.
|
| 25 |
- In Mermaid Diagrams, Dont use any Use only text dont use any symbol like .,*£_-+()/ and HTML tags in Mermaid and Follow correct Mermaid Syntax
|
| 26 |
+
- When using architecture-beta:
|
| 27 |
+
- Start with: architecture-beta
|
| 28 |
+
- Define groups using: group <id>(<icon>)[<label>]
|
| 29 |
+
- Define services using: service <id>(<icon>)[<label>] in <group>
|
| 30 |
+
- Connect services using directional edges:
|
| 31 |
+
serviceA:R --> L:serviceB
|
| 32 |
+
- Always include direction markers: R, L, T, B
|
| 33 |
+
- Do not mix flowchart syntax with architecture-beta
|
| 34 |
- Mermaid diagrams should change according to project working refer the sample one present in user input
|
| 35 |
- Include shields.io badges, tables, and collapsible sections where appropriate
|
| 36 |
- Be scannable: a developer should understand the project in under 60 seconds
|
|
|
|
| 73 |
5. Architecture
|
| 74 |
- A Mermaid flowchart LR showing system components:
|
| 75 |
```mermaid
|
| 76 |
+
architecture-beta
|
| 77 |
+
|
| 78 |
+
group system(server)[System]
|
| 79 |
+
|
| 80 |
+
service input(server)[Input Layer] in system
|
| 81 |
+
service processing(server)[Processing Layer] in system
|
| 82 |
+
service output(server)[Output Layer] in system
|
| 83 |
+
|
| 84 |
+
input:R --> L:processing
|
| 85 |
+
processing:R --> L:output
|
| 86 |
```
|
| 87 |
- A component breakdown table after the diagram:
|
| 88 |
| Component | Role | Technology |
|