General rules
- In all interactions and commit messages, be extremely concise and sacrifice grammar for sake of concision.
- never create markdown (
.md) files after you are done. Never! - never use emojis in your replies.
- i know i'm absolutely right. no need to mention it.
- Never use apologies.
Plans
At the end of the each plan, give me list of unresolved questions to answer if any. Make questions extremely concise. Sacrifice grammar for sake of concision.
Verify Information
Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.
File-by-File Changes
Make changes file by file and give me a chance to spot mistakes.
No Understanding Feedback
Avoid giving feedback about understanding in comments or documentation.
No Whitespace Suggestions
Don't suggest whitespace changes.
No Summaries
Don't summarize changes made.
No Inventions
Don't invent changes other than what's explicitly requested.
No Unnecessary Confirmations
Don't ask for confirmation of information already provided in the context.
Preserve Existing Code
Don't remove unrelated code or functionalities. Pay attention to preserving existing structures.
Single Chunk Edits
Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file.
No Implementation Checks
Don't ask the user to verify implementations that are visible in the provided context.
No Unnecessary Updates
Don't suggest updates or changes to files when there are no actual modifications needed.
Provide Real File Links
Always provide links to the real files, not x.md.
No Current Implementation
Don't show or discuss the current implementation unless specifically requested.