docs: update claude.md (#72)

Author: huozhi

CLAUDE.md

@@ -44,35 +44,36 @@ Test files are located in `test/e2e/` and use test fixtures from `test/fixtures/
 
 ## Architecture
 
-### MCP Server Structure (src/index.ts)
+### MCP Server Structure
 
-The main server (`src/index.ts`) uses stdio transport and registers:
-- **Tools** (`src/mcp-tools/`): Callable functions for automation
-- **Prompts** (`src/mcp-prompts/`): Pre-configured prompts for common tasks
-- **Resources** (`src/mcp-resources/`): Knowledge base articles and documentation
+The main server is generated by `xmcp` (configured in `xmcp.config.ts`) and uses stdio transport. The server automatically registers:
+- **Tools** (`src/tools/`): Callable functions for automation
+- **Prompts** (`src/prompts/`): Pre-configured prompts for common tasks
+- **Resources** (`src/resources/`): Knowledge base articles and documentation
 
 ### Key Components
 
-**MCP Tools Registry** (`src/mcp-tools/index.ts`):
+**MCP Tools** (`src/tools/`):
+- Tools are automatically discovered and registered by xmcp from `src/tools/`
 - `nextjs_docs`: Search Next.js documentation and knowledge base
 - `browser_eval`: Playwright browser automation (via `playwright-mcp` server)
 - `nextjs_runtime`: Connect to Next.js dev server MCP endpoint for runtime diagnostics
 - `upgrade_nextjs_16`: Automated Next.js 16 upgrade guidance
 - `enable_cache_components`: Complete Cache Components setup with error detection
 
-**MCP Client Library** (`src/lib/mcp-client.ts`):
+**MCP Client Library** (`src/_internal/mcp-client.ts`):
 - Connects to external MCP servers via stdio transport
 - Used by `browser_eval` to communicate with `playwright-mcp`
 - Used by `nextjs_runtime` to communicate with Next.js dev server MCP endpoint
 
-**Runtime Managers** (`src/lib/`):
+**Runtime Managers** (`src/_internal/`):
 - `browser-eval-manager.ts`: Manages Playwright MCP server lifecycle
 - `nextjs-runtime-manager.ts`: Discovers and connects to Next.js dev servers with MCP enabled
 
 **Resources Architecture**:
 - Knowledge base split into focused sections (12 sections for Next.js 16)
 - Resources are loaded on-demand to avoid overwhelming context
-- Markdown files in `src/mcp-resources/` are copied to `dist/` during build via `scripts/copy-resources.js`
+- Markdown files in `src/resources/` are copied to `dist/resources/` during build via `scripts/copy-resources.js`
 
 ### TypeScript Configuration
 
@@ -83,10 +84,10 @@ The main server (`src/index.ts`) uses stdio transport and registers:
 
 ## Build Process
 
-1. TypeScript compilation: `tsc` compiles `src/` to `dist/`
-2. Resource copying: `scripts/copy-resources.js` copies markdown files and knowledge base directories from `src/` to `dist/`
+1. Server generation: `xmcp build` generates the MCP server from `xmcp.config.ts` configuration
+2. Resource copying: `scripts/copy-resources.js` copies markdown files from `src/resources/` and `src/prompts/` to `dist/resources/`
 
-The `dist/index.js` file is the entry point for the MCP server and includes a shebang for CLI execution.
+The `dist/stdio.js` file is the entry point for the MCP server and includes a shebang for CLI execution.
 
 ## MCP Protocol Integration
 
@@ -103,8 +104,9 @@ This server can:
 ## External MCP Server Dependencies
 
 **Playwright MCP** (`browser_eval` tool):
-- Automatically installed via npx when needed
-- Command: `npx -y @modelcontextprotocol/server-playwright`
+- Automatically installed globally via npm when needed
+- Package: `@playwright/mcp`
+- Command: `npx @playwright/mcp@latest` (with optional `--browser` and `--headless` flags)
 - Used for browser automation and testing
 
 **Next.js Runtime MCP** (`nextjs_runtime` tool):
@@ -116,24 +118,24 @@ This server can:
 ## Common Development Patterns
 
 **Adding a new MCP tool**:
-1. Create tool file in `src/mcp-tools/` with Zod schema and `tool()` function
-2. Export from `src/mcp-tools/index.ts` and add to `MCP_TOOLS` registry
+1. Create tool file in `src/tools/` with Zod schema and `tool()` function
+2. xmcp automatically discovers and registers tools from `src/tools/`
 3. Build and test
 
 **Adding a new MCP resource**:
-1. Create markdown file(s) in `src/mcp-resources/`
-2. Update `scripts/copy-resources.js` to include new resource
-3. Create resource handler in `src/mcp-resources/` with URI scheme
-4. Register in `src/index.ts` ListResourcesRequestSchema and ReadResourceRequestSchema handlers
+1. Create markdown file(s) in `src/resources/`
+2. Create resource handler TypeScript file in `src/resources/` with URI scheme
+3. xmcp automatically discovers and registers resources from `src/resources/`
+4. The `scripts/copy-resources.js` script automatically copies `.md` files to `dist/resources/`
 
 **Working with external MCP servers**:
-- Use `src/lib/mcp-client.ts` for stdio-based communication
-- Create manager module in `src/lib/` for lifecycle management
+- Use `src/_internal/mcp-client.ts` for stdio-based communication
+- Create manager module in `src/_internal/` for lifecycle management
 - Handle server installation, connection, and cleanup
 
 ## Package Publishing
 
 - Package name: `next-devtools-mcp`
-- Binary: `next-devtools-mcp` points to `dist/index.js`
+- Binary: `next-devtools-mcp` points to `dist/stdio.js`
 - prepublishOnly hook: cleans and rebuilds before publishing
 - Use `pnpm@9.15.9` as package manager