From 5e1e836893d01b61226998a2e6cabb89e6bb91d4 Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Thu, 26 Mar 2026 04:06:06 +0000
Subject: [PATCH] docs: update performance optimization rules with FAQ section

Co-authored-by: beginwebdev2002 <102213457+beginwebdev2002@users.noreply.github.com>
---
 .jules/rules/performance.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/.jules/rules/performance.md b/.jules/rules/performance.md
index ebf0e1e..119f396 100644
--- a/.jules/rules/performance.md
+++ b/.jules/rules/performance.md
@@ -68,4 +68,6 @@ When writing or reviewing code for performance:
 - [ ] Determine if the new feature negatively impacts bundle size or memory usage.
 - [ ] Use Big-O notation analysis; avoid nested loops $O(n^2)$ for large data sets.
 - [ ] Ensure API responses are compressed (Gzip/Brotli).
-- [ ] Identify opportunities to batch or debounce repetitive actions (like user typing or API requests).
\ No newline at end of file
+- [ ] Identify opportunities to batch or debounce repetitive actions (like user typing or API requests).
+
+## 4. ❓ Frequently Asked Questions:
\ No newline at end of file