You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: scripts/readme-generator/readme-generator.ts
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,7 @@ You are a REAME.md generator. Your goal is to generate a README.md file for a pr
44
44
- Use markdown syntax to format the README.md file content
45
45
- Use Mermaid syntax to generate diagrams
46
46
- Use jsonc for all json code snippets. This allows you to add comments to the json code.
47
+
- Leave a blank line between sections and code blocks, and after headings in the markdown file.
47
48
48
49
## Sections
49
50
The following sections must be included in the README.md file:
@@ -66,6 +67,7 @@ The following sections must be included in the README.md file:
66
67
## Architecture Instructions
67
68
- Only if the project is an 'app', create a system diagram using the Mermaid syntax. The diagram should show the main components of the system and how they interact.
68
69
- Only if the project uses LLMs or AI in some way, highlight any of the patterns described below in the Agentic Patterns Cheatsheet. Each distinct pattern should be described in a separate section with a title and a brief description of how it is used in the project, and a Mermaid diagram too.
70
+
- All mermaid diagrams should relate to specific code patterns, not just generic explanations of the pattern itself. Always relate it to the code or specific functionality.
69
71
70
72
### Mermaid Diagrams
71
73
- mermaid diagrams MUST NOT contain parentheses in the descriptions. The reason for this is that the Mermaid renderer that we use does not allow it.
@@ -87,7 +89,7 @@ graph TD;
87
89
88
90
### Markdown formatting
89
91
90
-
There is often a problem when using lists where the next line is indented with the list. This often happens with code blocks, e.g.:
92
+
There is often a problem when using lists where the next line is indented with the list. You should also leave a line between the list line and the start of the code block, e.g.:
91
93
92
94
- **dev**: Starts the development server.
93
95
\`\`\`
@@ -97,6 +99,7 @@ npx nx dev agent-task-manager
97
99
Notice how the first set of backticks is indented with the list item. This causes the list item to be treated as a code block, and really can mess things up. To fix this, you should ensure that the next line is not indented, e.g.:
0 commit comments