rule-performance

Enforce performance budgets during code review by checking changes against guardrails for JS bundle size, API latency targets, and rendering paths. This prevents regressions by validating that new code respects defined thresholds before deployment.

Prevent N+1 queries and unbounded result sets by enforcing database query discipline through explicit loading, indexing, and pagination. Applying these rules ensures efficient data access patterns and maintains backend API stability.

Set API latency targets and caching strategies by applying performance guardrails to frontend rendering paths. This includes configuring ISR where relevant and defining caching rules to maintain fast user experiences across client code.

Apply performance guardrails across both backend and frontend codebases to maintain full-stack performance. The rules target server-side database access patterns and client-side JS bundle size simultaneously.

JS bundle size grows when code changes lack performance budgets. Apply guardrails by specifying strict size thresholds during code review, ensuring new dependencies and rendering logic respect established limits.

Performance guardrails are predefined rules for code changes that enforce query discipline, latency targets, and caching. You need them for API endpoints to prevent inefficient implementations and performance regressions.