| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657 |
- ---
- description:
- globs:
- alwaysApply: true
- ---
- # Your rule content
- - You can @ files here
- - You can use markdown but dont have to
- ---
- description: Code Quality Guidelines
- globs:
- ---
- # Code Quality Guidelines
- ## 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 Apologies
- Never use apologies.
- ## 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.
|
