diff --git a/README.md b/README.md
index 6400c51..b402610 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,10 @@
+# > **Openfire Exploit Suite** — A full-stack security testing toolkit (recon, PoC, Burp plugin, Metasploit modules) for identifying and exploiting Openfire admin console and setup weaknesses.
+#
+# > **Repository description (sidebar):**
+# >> Openfire Exploit Suite — recon, PoC, Burp plugin, and Metasploit modules for Openfire vulnerabilities. Open‑source and responsibly shared.
+#
+# > **Suggested GitHub Topics (tags):** Openfire • Exploit • Metasploit • Burp Extension • PoC • Security Tool • Responsible Disclosure • CVE-2023-32315 • Recon Tool
+
 # Openfire Exploit Suite
 
 [![Burp Suite](https://img.shields.io/badge/Burp%20Suite-Pro%20Edition-orange)]()
@@ -145,4 +152,18 @@ For defenders and system administrators:
 - Disable or harden `/setup/` path in production deployments.
 - Use WAF to block double-encoded traversal attempts.
 - Monitor logs for unusual access to `admin-login.jsp` and lingering setup JSPs.
-- Use Burp Collaborator or Canary Tokens to trace callback attempts.
\ No newline at end of file
+- Use Burp Collaborator or Canary Tokens to trace callback attempts.
+
+---
+
+##  README Best Practices
+This README is designed to:
+- Provide an immediate project overview and quick setup instructions for new users.
+- Link out to detailed documentation files (in `docs/`), avoiding walls of text.
+- Meet open-source standards—clear, concise, and inviting for contribution.
+
+Based on best practices from sources like FreeCodeCamp and Microsoft docs:  
+— Keep your README up to date and focused.  
+— Provide installation, usage, and contribution paths succinctly.  
+— Use badges, clear headers, and external links where needed.  
+([freecodecamp.org](https://www.freecodecamp.org/news/how-to-write-a-good-readme-file/)) ([appsmith.com](https://www.appsmith.com/blog/write-a-great-readme))
\ No newline at end of file