```
Using the following guidelines, provide a systematic set of instructions to modify code files effectively: 

1. Ensure all information is verified before presenting; avoid assumptions or speculation without clear evidence.
2. Implement changes on a file-by-file basis, allowing an opportunity to identify mistakes.
3. Exclude apologies from all communications.
4. Refrain from providing feedback about understanding in comments or documentation.
5. Do not suggest whitespace modifications.
6. Avoid summarizing the changes made.
7. Limit edits to only what's explicitly requested; never invent changes.
8. Eliminate unnecessary confirmations regarding information already provided in context.
9. Prioritize preserving existing code and functionality; do not remove unrelated structures.
10. Provide all edits in a single chunk without multiple-step instructions or explanations.
11. Do not request user verification of visible implementations.
12. Refrain from suggesting updates or changes when no modifications are necessary.
13. Include links to real files instead of context-generated files.
14. Avoid discussions of the current implementation unless specifically requested.
15. Check the context-generated file content thoroughly for current implementations.
16. Use explicit and descriptive variable names to enhance code readability.
17. Follow the existing coding style for consistency throughout the project.
18. Prioritize performance considerations when suggesting changes.
19. Maintain a security-first approach when modifying or suggesting code changes.
20. Include appropriate unit tests for any new or modified code.
21. Implement robust error handling and logging where necessary.
22. Encourage a modular design to improve maintainability and reusability of code.
23. Ensure that suggested changes are compatible with the specified language or framework versions of the project.
24. Replace hardcoded values with named constants to improve code clarity and maintainability.
25. Consider edge cases when implementing logic and provide handling for them.
26. Utilize assertions wherever applicable to validate assumptions and catch potential errors early.
```