docs(event-bus): enhance event bus documentation with naming conventions and best practices

Author: Lasim

docs/development/frontend/architecture.mdx

@@ -268,27 +268,9 @@ User Interaction → View → Service → API
 
 ### Event-Driven Updates
 
-The application uses an **event bus** for cross-component communication without direct coupling.
+The application uses an **event bus** for cross-component communication without direct coupling. This enables real-time updates across unrelated components, cache invalidation signals, global notifications, and feature-to-feature communication.
 
-Read more about the global event bus in the [Event Bus Documentation](/development/frontend/event-bus).
-
-#### Event Bus Usage
-
-- Real-time updates across unrelated components
-- Cache invalidation signals
-- Global notifications
-- Feature-to-feature communication
-
-#### Event Naming Convention
-
-```
-{feature}-{action}
-```
-
-Examples:
-- `teams-updated`
-- `credential-deleted`
-- `mcp-server-deployed`
+For complete details on the event bus system, including usage patterns, naming conventions, and implementation examples, see the [Event Bus Documentation](/development/frontend/event-bus).
 
 ## Component Implementation Standards
 

docs/development/frontend/event-bus.mdx

@@ -321,28 +321,57 @@ onUnmounted(() => {
 </script>
 ```
 
-## Best Practices
+## Event Naming Convention
+
+The event bus follows a consistent naming pattern to ensure clarity and maintainability across the application.
 
-### 1. Event Naming Convention
+### Standard Pattern
 
-Use descriptive, action-based names with consistent patterns:
+```
+{feature}-{action}
+```
+
+This pattern makes events self-documenting and easy to understand at a glance.
+
+### Examples
 
 ```typescript
-// Good
+// Team-related events
 'teams-updated'
-'user-profile-changed'
+'team-created'
+'team-deleted'
+'team-selected'
+
+// Credential events
+'credentials-updated'
+'credential-created'
+'credential-deleted'
+
+// MCP server events
 'mcp-server-deployed'
-'notification-show'
+'mcp-server-installed'
+'mcp-installation-removed'
 
-// Avoid
-'update'
-'change'
-'event1'
+// System events
+'notification-show'
+'storage-changed'
+'cache-cleared'
 ```
 
-### 2. Type Safety
+### Naming Guidelines
+
+- **Use kebab-case**: All event names should use lowercase with hyphens
+- **Feature first**: Start with the feature or domain name
+- **Action second**: End with the specific action or state change
+- **Be specific**: Avoid generic names like 'update' or 'change' without context
+- **Past tense for completed actions**: Use 'created', 'updated', 'deleted' for completed operations
+- **Present tense for commands**: Use 'show', 'hide', 'clear' for immediate actions
+
+## Best Practices
+
+### 1. Event Type Definition
 
-Always define event types in the `EventBusEvents` interface:
+Always define event types in the `EventBusEvents` interface for type safety:
 
 ```typescript
 export type EventBusEvents = {
@@ -357,7 +386,7 @@ export type EventBusEvents = {
 }
 ```
 
-### 3. Memory Management
+### 2. Memory Management
 
 Always clean up event listeners to prevent memory leaks:
 
@@ -385,7 +414,7 @@ onUnmounted(() => {
 </script>
 ```
 
-### 4. Error Handling
+### 3. Error Handling
 
 Wrap event handlers in try-catch blocks:
 
@@ -405,7 +434,7 @@ const handleDataUpdate = (data: any) => {
 }
 ```
 
-### 5. Debugging Events
+### 4. Debugging Events
 
 Add logging for development: