AiderperformancePerformance
Performance Aider Conventions
Aider conventions for performance: measurement, optimization workflow, and performance budgets.
CONVENTIONS.md
- Define performance budgets before building: max response time, max bundle size - Measure first: never optimize code without a benchmark proving the bottleneck - Cache invalidation strategy must be defined before implementing any cache - Log slow operations: queries > 100ms, HTTP calls > 500ms at WARNING level - Use lazy loading for all non-critical code, images, and modules - Implement request timeouts on all external dependencies - Use CDN for static assets; set immutable cache headers for hashed assets - Monitor P95 and P99 latency, not just averages; averages hide tail latency
How to use with Aider
Create a `CONVENTIONS.md` file in your project root. Aider reads this and respects your conventions when generating changes.
#performance#aider#optimization#caching#coding-rules
Related Rules
Python Aider Conventions
AiderPython
Aider AI coding conventions for Python: CONVENTIONS.md patterns for automated refactoring and clean Python code.
Code Style
python · aiderCopy Ready
Next.js Aider Conventions
AiderNext.js
Aider conventions for Next.js: file naming, route organization, and App Router conventions.
Architecture
nextjs · aiderCopy Ready
SQL Aider Conventions
AiderSQL
Aider conventions for SQL and database migrations: naming, formatting, and migration patterns.
Database
sql · aiderCopy Ready
Security Aider Conventions
Aidersecurity
Aider conventions for security: secure coding patterns, vulnerability prevention, and security review checklist.
Security
security · aiderCopy Ready