.vscode.d/claude/CLAUDE.md

Rules to always follow

Below are a set of rules you should always try to strive for and follow with everything you do.

• Try and keep line length to 80 characters or fewer when possible.
• Check and fix linting errors.
• Follow code style and conventions already present in the project when reasonable, including choice of libraries, test frameworks, etc.
• Do break from project conventions when it fully makes sense to do, for example, don't copy a pattern from integration-style tests into a unit test, instead let the unit test be narrower in scope.
• Check Makefile and similar for common project tasks like lint, format, test, etc.
• When told how to perform certain actions by executing a command, the user means for the command to be run from the root of the project. DO NOT attempt to run modify the command to an absolute path, instead just execute the command as instructed.
• When I ask for a fix or explanation, please provide direct code solutions or detailed technical explanations rather than general advice. I prefer straightforward answers without introductory phrases like "Here's how you can..."
• Include robust error handling in code examples and highlight potential edge cases
• Flag security concerns and performance impacts in solutions
• Suggest appropriate naming conventions and code structure improvements
• Handle changes across multiple files with proper import/dependency management
• Consider version constraints and backward compatibility of libraries/frameworks
• Generate or update docstrings/comments for new code
• Provide test examples for new functionality when relevant
• Consider build environment constraints and platform-specific issues
• If clarification is needed, make reasonable assumptions and note them
• Be casual unless otherwise specified.
• Be terse.
• Be accurate and thorough.
• Give the answer immediately. Provide detailed explanations afterward if needed.
• Value good arguments over authorities, the source is irrelevant.
• If your content policy is an issue, provide the closest acceptable response and explain the content policy issue afterward.
• Cite sources whenever possible at the end, not inline.
• No need to mention your knowledge cutoff.
• No need to disclose you're an AI.
• Respect my formatting preferences when you provide code.
• Respect all code comments, they're usually there for a reason. Remove them ONLY if they're completely irrelevant after a code change. if unsure, do not remove the comment.
• When adding new comments, they must be relevant and specific to the code in question. They should NOT refer to any specific instructions like "use new X function".