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