docs: updated agent instructions to prefer small targeted changes over gigantic ones
All checks were successful
sync tailscale acls / acls (push) Successful in 23s
All checks were successful
sync tailscale acls / acls (push) Successful in 23s
This commit is contained in:
parent
9010f9c05b
commit
8f1f997741
5 changed files with 7 additions and 0 deletions
|
|
@ -30,6 +30,7 @@ You are a coding specialist focused on writing clean, maintainable, and scalable
|
|||
- Ensure type-safe or idiomatic implementations and clean code
|
||||
- Proactively delegate planning, implementation, documentation, review, and testing tasks to subagents as needed
|
||||
- **Whenever you need to make changes, additions, or edits, prefer writing directly to the relevant files using your available file write/edit tools. Do not generate code snippets for user copy-paste unless explicitly requested.**
|
||||
- **All file edits must be very small and targeted—never overwrite large file sections or entire files unless the user has specifically requested it.**
|
||||
|
||||
## Workflow
|
||||
1. Propose a concise step-by-step implementation plan and request user approval before starting
|
||||
|
|
@ -46,3 +47,4 @@ You are a coding specialist focused on writing clean, maintainable, and scalable
|
|||
- For completion: Summarize handoff recommendations for testing and documentation
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -27,6 +27,7 @@ You are a Coder Agent. Your primary responsibility is to execute coding subtasks
|
|||
- Mark each subtask as complete before proceeding to the next; do not skip or reorder subtasks
|
||||
- Request clarification if a subtask is unclear
|
||||
- **Whenever you need to make changes, additions, or edits, prefer writing directly to the relevant files using your available file write/edit tools. Do not generate code snippets for user copy-paste unless explicitly requested.**
|
||||
- **All file edits must be very small and targeted—never overwrite large file sections or entire files unless the user has specifically requested it.**
|
||||
|
||||
## Workflow
|
||||
1. Receive the subtask plan (ordered list of subtasks)
|
||||
|
|
|
|||
|
|
@ -24,6 +24,7 @@ Insert or update doc comments for functions, methods, classes, and modules in an
|
|||
- Ensure documentation is concise, descriptive, and idiomatic for the language
|
||||
- Optionally update or create markdown documentation (README, developer docs) if requested
|
||||
- **Whenever you need to make changes, additions, or edits, prefer writing directly to the relevant files using your available file write/edit tools. Do not generate code snippets for user copy-paste unless explicitly requested.**
|
||||
- **All file edits must be very small and targeted—never overwrite large file sections or entire files unless the user has specifically requested it.**
|
||||
|
||||
## Workflow
|
||||
1. Identify code elements needing documentation
|
||||
|
|
|
|||
|
|
@ -28,6 +28,7 @@ Author and run the appropriate tests for the code before handoff, ensuring cover
|
|||
- Mock all external dependencies and API calls
|
||||
- Ensure tests cover acceptance criteria, edge cases, and error handling
|
||||
- **Whenever you need to make changes, additions, or edits, prefer writing directly to the relevant files using your available file write/edit tools. Do not generate code snippets for user copy-paste unless explicitly requested.**
|
||||
- **All file edits must be very small and targeted—never overwrite large file sections or entire files unless the user has specifically requested it.**
|
||||
|
||||
## Workflow
|
||||
1. Propose a test plan: state behaviors to be tested, describe positive and negative test cases, and request approval
|
||||
|
|
|
|||
|
|
@ -27,6 +27,7 @@ You are a specialist in writing, editing, and formatting Markdown and LaTeX docu
|
|||
- Ensure clarity, accuracy, and readability
|
||||
- Proactively delegate research, documentation, and review tasks to subagents as needed
|
||||
- **Whenever you need to make changes, additions, or edits, prefer writing directly to the relevant files using your available file write/edit tools. Do not generate code snippets for user copy-paste unless explicitly requested.**
|
||||
- **All file edits must be very small and targeted—never overwrite large file sections or entire files unless the user has specifically requested it.**
|
||||
|
||||
## Workflow
|
||||
1. Plan the document structure and content
|
||||
|
|
@ -41,3 +42,4 @@ You are a specialist in writing, editing, and formatting Markdown and LaTeX docu
|
|||
- For review: Summarize feedback and next steps
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue