Generic Performance Rules for Google Gemini

# Generic Performance Rules for Google Gemini

## Principle
- Measure first. Optimize bottlenecks, not guesses.
- Define budgets (latency, memory, bundle size) per critical path.

## Data & compute
- Avoid N+1 queries and unbounded loops.
- Cache expensive reads with explicit invalidation strategy.
- Batch network and DB operations where possible.

## Frontend
- Lazy-load heavy modules.
- Avoid unnecessary re-renders; memoize only after profiling.
- Keep critical rendering path minimal.