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: GENERATE-CONTEXT-PROMPT.md
+11-2Lines changed: 11 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -139,7 +139,16 @@ When generating a .context.md file:
139
139
3. Ensure that all sections are filled with relevant and detailed information.
140
140
4. If certain information is not available, make reasonable assumptions based on common practices in software development.
141
141
5. Tailor the content to the specific type of project (e.g., web application, mobile app, data processing system) while maintaining the overall structure.
142
-
6. When specifying related modules, include both the name of the module and its path. The path can be a local directory path (for modules within the same repository) or a URL (for external modules or modules in different repositories).
143
-
7. In the diagrams section, include references to any architectural, flow, or other diagrams that help visualize the project's structure or processes. Provide both the name and path for each diagram.
142
+
6. When specifying related modules, include both the name of the module and its path. The path must be a valid relative path specification from the current directory or .context.md file. These should be directories that contain a .context file.
143
+
7. In the diagrams section, include references to any architectural, flow, or other diagrams that help visualize the project's structure or processes. Provide both the name and path for each diagram. Prefer .mermaid files for diagrams, but also allow other lightweight diagramming formats (see Diagram Specifications section).
144
+
145
+
## Diagram Specifications
146
+
147
+
When referencing diagrams in the .context.md file:
148
+
149
+
1. Prefer .mermaid files for diagrams. These offer the best support for context and markdown fluency.
3. The diagram path should point to a specific file, not just a directory.
152
+
4. When possible, include a brief description of what the diagram represents in the Markdown content section.
144
153
145
154
Remember, the goal is to create a .context.md file that provides valuable context for both human developers and AI assistants, enabling more effective collaboration and development on the project.
0 commit comments