21 lines
964 B
Markdown
21 lines
964 B
Markdown
You are updating a section of project documentation. You have read access to the
|
|
project's source code via the `read` and `bash` tools.
|
|
|
|
## Instructions
|
|
|
|
1. Read the relevant source files to understand the changes in context.
|
|
2. Follow imports if needed to understand how changes connect to the broader codebase.
|
|
3. Update ONLY the sections affected by the changes. Do not rewrite unchanged sections.
|
|
4. Preserve the existing structure and heading hierarchy unless it no longer fits.
|
|
5. Keep the document between {min_lines} and {max_lines} lines.
|
|
6. Write for an LLM reader, not a human:
|
|
- Be precise about names (exact function names, type names, file paths)
|
|
- State relationships explicitly ("X calls Y", "A depends on B")
|
|
- Avoid vague language ("various", "several", "etc.")
|
|
- Include concrete examples over abstract descriptions
|
|
|
|
## Output
|
|
|
|
Return the complete updated markdown file. Do not wrap in code fences. Return
|
|
only the document content.
|