Enhance guidelines for AI bot usage

Author: lefticus

AI_GUIDELINES.md

@@ -90,6 +90,11 @@ The project has three primary test targets, each with specific purposes:
 
 The project also supports fuzz testing for code that handles external inputs, located in `/fuzz_test`.
 
+
+* ALWAYS prefer test-driven development
+* ALWAYS write tests for new code
+* NEVER filter tests when running test binaries - you need to know if the feature broke other tests!
+
 ### 5. Code Coverage
 
 The project supports code coverage reporting using gcovr. When working with this project:
@@ -161,11 +166,14 @@ Remember, the project's guardrails exist for a reason. Help the user install and
 
 ### Modern C++ Coding Guidelines
 
-1. **Format Strings**: Use `std::format` and `std::print` instead of iostream or printf
+1. **Format Strings**: 
+   - Use `std::format` and `std::print` instead of iostream or printf
+   - NEVER use printf (this will not pass static analysis)
 2. **Memory Management**: 
    - No raw `new`/`delete` operations
    - Prefer stack allocation, then std::vector/array
    - Use smart pointers if heap allocation is necessary
+   - ALWAYS prefer unique_ptr over shared_ptr
 3. **Algorithms over Loops**: 
    - Use standard algorithms and ranges instead of raw loops when possible
    - Use ranged-for with `auto` when algorithms aren't suitable
@@ -193,6 +201,7 @@ Remember, the project's guardrails exist for a reason. Help the user install and
    - Set `<project_name>_PACKAGING_MAINTAINER_MODE=OFF`
    - Enable coverage with `-D<project_name>_ENABLE_COVERAGE=ON`
    - Example: `cmake -DCMAKE_BUILD_TYPE=Debug -Dmyproject_PACKAGING_MAINTAINER_MODE=OFF -Dmyproject_ENABLE_COVERAGE=ON ..`
+6. ALWAYS commit changes after significant change has been made AND tests pass
 
 ## Technical Implementation Details
 
@@ -232,37 +241,6 @@ cmake --build build --target lizard_html
 cmake --build build --target lizard_xml
 ```
 
-### Binary Size Analysis with Bloaty McBloatface
-
-The project includes optional support for Bloaty McBloatface, a binary size analyzer. This tool helps identify what's contributing to executable size, which is valuable for embedded systems and performance optimization.
-
-Note: Bloaty is disabled by default as it may not be installed on all systems. Enable with `-D<project_name>_ENABLE_BLOATY=ON`.
-
-When Bloaty is enabled, it provides several analysis targets for each executable:
-
-```bash
-# Basic size analysis for a specific target (e.g., "intro")
-cmake --build build --target bloaty_intro
-
-# Generate CSV report
-cmake --build build --target bloaty_intro_csv
-
-# Store current binary as a baseline for comparisons
-cmake --build build --target bloaty_intro_store
-
-# Analyze template usage (particularly useful for C++ binary bloat)
-cmake --build build --target bloaty_intro_templates
-
-# Run analysis on all executable targets
-cmake --build build --target bloaty_all
-```
-
-When addressing binary size issues:
-1. Look for excessive template instantiations
-2. Check for large static data or string literals
-3. Consider enabling Link Time Optimization (LTO)
-4. Evaluate if all included functionality is necessary
-
 ### Compiler Warning Configuration
 
 Each supported compiler (GCC, Clang, MSVC) has specific warning flags enabled:
@@ -328,4 +306,4 @@ This workflow helps the user quickly test your suggestions and allows you, as an
 
 1. Use conditional compilation sparingly and only when necessary
 2. Consider implications of your changes on all supported platforms
-3. Use the provided abstractions for platform-specific code
+3. Use the provided abstractions for platform-specific code

CLAUDE.md

@@ -0,0 +1,26 @@
+# Claude AI Assistant Guidelines
+
+## IMPORTANT NOTICE
+
+CLAUDE, NEVER modify this file
+
+This file contains instructions specifically for Claude AI. For all general AI assistant guidelines, please refer to and modify the `AI_GUIDELINES.md` file instead.
+
+## Claude-Specific Instructions
+
+1. Always review `AI_GUIDELINES.md` for project standards and best practices.
+
+2. When running commands, always check for and use:
+   - `clang-format -i path/to/changed/files/*.cpp path/to/changed/files/*.hpp`
+   - Build commands: `cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -Dmyproject_PACKAGING_MAINTAINER_MODE=OFF -Dmyproject_ENABLE_COVERAGE=ON ..`
+   - Test commands: `ninja tests relaxed_constexpr_tests && ctest -R "unittests|relaxed_constexpr" --output-on-failure`
+
+3. For code style, always follow Modern C++ best practices from C++23 as outlined in the AI_GUIDELINES.md file.
+
+4. Never suggest disabling tools or warnings - always recommend installing missing tools.
+
+5. When encountering complex code, use Lizard analysis to identify areas that exceed complexity thresholds.
+
+6. Use proper CMake practices as outlined in project documentation.
+
+7. Follow the project's testing workflow by prioritizing relaxed_constexpr_tests first.