docs: update agent guidelines to minimize documentation verbosity
This commit is contained in:
2 files changed
+2
-2
No files matched your search
@@ -10,7 +10,7 @@ This section outlines the universal rules and expectations for any LLM agent wor
|
||||
|
||||
**Maintain Context:** Before making any changes, an agent must read and understand the relevant files, including the project's main documentation and existing code structure.
|
||||
|
||||
**Be Sparse:** Only introduce new code if needed. Comment only what is worth commenting. When testing focus on the business use case.
|
||||
**Be Sparse:** Only introduce new code if needed. Comment only what is worth commenting. When testing focus on the business use case. When writing documentations keep the explanation to a minimum.
|
||||
|
||||
## Project structure
|
||||
|
||||
|
||||
+1
-1
@@ -14,7 +14,7 @@ This section outlines the universal rules and expectations for any LLM agent wor
|
||||
|
||||
**Maintain Context:** Before making any changes, an agent must read and understand the relevant files, including the project's main documentation and existing code structure.
|
||||
|
||||
**Be Sparse:** Only introduce new code if needed. Comment only what is worth commenting. When testing focus on the business use case.
|
||||
**Be Sparse:** Only introduce new code if needed. Comment only what is worth commenting. When testing focus on the business use case. When writing documentations keep the explanation to a minimum.
|
||||
|
||||
## Project structure
|
||||
|
||||
|
||||
Reference in new issue
Block a user