Guiyom commited on
Commit
58b3e65
·
verified ·
1 Parent(s): 2bfdd6e

Update app.py

Browse files
Files changed (1) hide show
  1. app.py +4 -2
app.py CHANGED
@@ -110,7 +110,7 @@ G --> H[Performance Evaluation - 45% Speed Improvement, 35% Risk Profiling, 50%
110
  -- flowchart --
111
  Important:
112
  - If the flow is "broader" than deep, choose LR (Left Right)
113
- - If the flow is "deeper" than broad, choose TD (Top Down)
114
 
115
  Top Down:
116
 
@@ -281,6 +281,7 @@ Keep in mind the:
281
  - Use html with css to render it, keep it sober and focused on the content
282
  - The output has to be boxed in a border of 1px Black and grey background (#ede8e8)
283
  - Font size minimum 12px for readability in PDF
 
284
  - You have freedom on the structure, but it has to cover all potential aspects on the topic in between 500 and 1000 words
285
 
286
  // Important
@@ -540,13 +541,14 @@ The report should be very detailed and lengthy — approximately the equivalent
540
  // Requirements
541
  - It must include inline citations (e.g., [1], [2], etc.) from real sources in the context
542
  - It must follow this writing style {reportstyle}.
 
543
  - name projects, products, organisations and people with their titles - make it REAL
544
  - The report must include at least {round(pages/3,0)} tables from the sources used (add citations if necessary) and use facts and figures extensively to ground the analysis.
545
  - For the numbering of titles or numbered lists, use numbers (ex: 1.) and sub-units (1.1, 1.2... 1.1.1...,1.1.2...).
546
  - For the reference citations, add systematically the urls from the Learnings (no need to put them in numbered list format since we alredy have the [x] that serves as number list)
547
  - Put paragraphs, sentences that are part of the same section in a div tag, this will be used for formatting.
548
  - Text Alignment has to be to the left, including for the titles
549
- - Titles should use the h1 to h4 tags hierarchy
550
  - Use inline formatting for the tables with homogeneous border and colors
551
  - Do not use html numbered lists format, they don't get correctly implemented. Use plain text format for numbering of sections and sub-sections
552
  - End the report with <p>---end---</p>, right before </div></body></html>
 
110
  -- flowchart --
111
  Important:
112
  - If the flow is "broader" than deep, choose LR (Left Right)
113
+ - If the flow is "deeper" than broad (>3 levels), choose TD (Top Down)
114
 
115
  Top Down:
116
 
 
281
  - Use html with css to render it, keep it sober and focused on the content
282
  - The output has to be boxed in a border of 1px Black and grey background (#ede8e8)
283
  - Font size minimum 12px for readability in PDF
284
+ - Skip lines and add intermediate titles for key paragraphs
285
  - You have freedom on the structure, but it has to cover all potential aspects on the topic in between 500 and 1000 words
286
 
287
  // Important
 
541
  // Requirements
542
  - It must include inline citations (e.g., [1], [2], etc.) from real sources in the context
543
  - It must follow this writing style {reportstyle}.
544
+ - Don't make too large blocks, skip lines and add line breaks when changing topic.
545
  - name projects, products, organisations and people with their titles - make it REAL
546
  - The report must include at least {round(pages/3,0)} tables from the sources used (add citations if necessary) and use facts and figures extensively to ground the analysis.
547
  - For the numbering of titles or numbered lists, use numbers (ex: 1.) and sub-units (1.1, 1.2... 1.1.1...,1.1.2...).
548
  - For the reference citations, add systematically the urls from the Learnings (no need to put them in numbered list format since we alredy have the [x] that serves as number list)
549
  - Put paragraphs, sentences that are part of the same section in a div tag, this will be used for formatting.
550
  - Text Alignment has to be to the left, including for the titles
551
+ - Titles should use the h1 to h4 html tags depending on the hierarchy
552
  - Use inline formatting for the tables with homogeneous border and colors
553
  - Do not use html numbered lists format, they don't get correctly implemented. Use plain text format for numbering of sections and sub-sections
554
  - End the report with <p>---end---</p>, right before </div></body></html>