docs(claudemd): add prompt handlers and server dependency to documentation

I am updating the documentation to reflect the addition of prompt handlers and the inclusion of the MCP server implementation as a dependency. This clarifies the project structure and guides users on how to add new prompts, ensuring better maintainability and understanding of the codebase.

Author: chew-z

CLAUDE.md

@@ -10,10 +10,12 @@ This project is a Go-based MCP (Model Control Protocol) server that acts as a br
 - **Core Logic**:
     - `gemini_server.go`: Gemini service implementation.
     - `direct_handlers.go`: Handlers for the MCP tools.
+    - `prompt_handlers.go`: Handlers for MCP prompts.
     - `tools.go`: Definitions of the MCP tools.
 - **Transport**: Supports `stdio` and `http` (with JWT authentication).
 - **Dependencies**:
     - `github.com/mark3labs/mcp-go/mcp`: MCP protocol implementation.
+    - `github.com/mark3labs/mcp-go/server`: MCP server implementation.
     - `google.golang.org/genai`: Google Gemini API client.
     - `github.com/joho/godotenv`: for loading `.env` files.
 
@@ -47,7 +49,8 @@ The server is configured via environment variables, which can be overridden by C
 
 ## AI Assistant Guidelines
 - When adding a new tool, define it in `tools.go`, implement the handler in `direct_handlers.go`, and register it in `setupGeminiServer()` in `main.go`.
+- When adding a new prompt, define it in `prompts.go`, implement the handler in `prompt_handlers.go` using the `server.PromptHandlerFunc` type, and register it in `setupGeminiServer()`.
 - When modifying configuration, update `config.go` for defaults, `NewConfig()` for parsing, `structs.go` for the `Config` struct, and `main.go` for CLI flags.
 - Always use `ResolveModelID()` before making API calls to convert model family IDs to specific version IDs.
 - Use the existing logging infrastructure for any new logging.
-- Follow the existing code style and patterns.
+- Follow the existing code style and patterns.