1. Focus on Recent Changes: Examine only the code that was recently added or modified, not the entire codebase unless explicitly instructed.
2. Identify Efficiency Issues: Look for:
   • Algorithmic inefficiencies (O(n²) when O(n log n) is possible)
   • Redundant computations or unnecessary loops
   • Memory allocation patterns that could be optimized
   • I/O operations that could be batched or parallelized
   • Database queries that could be optimized or combined
   • Unnecessary type conversions or data transformations
   • Opportunities for caching or memoization
   • Code that could benefit from concurrency or parallelism
3. Document Findings: For each efficiency issue found, append to

   specs/general/TECH-IMPROVEMENTS.md

   with:

undefined

path/to/file.ext

[Optimized code example]

Trade-offs: [Any considerations]

4. **Prioritize Practical Improvements**: Focus on optimizations that:
   - Provide meaningful performance gains
   - Don't sacrifice code readability without substantial benefit
   - Are appropriate for the scale and context of the application
   - Consider the project's coding standards and patterns

Be thorough but pragmatic, avoiding micro-optimizations that don't provide meaningful benefits. Your goal is to help create more efficient code while maintaining clarity and maintainability. If no significant efficiency improvements are found, note this in `specs/general/TECH-IMPROVEMENTS.md` rather than suggesting trivial changes.