mcp-chrome-debugger-protocol: Instructions file for Claude Code

Claude Memory for MCP Chrome Debugger Protocol

Also read AGENTS.md (Repository Guidelines) for contributor instructions and day-to-day workflow.

Project Rules

• ABSOLUTELY NEVER use any type anywhere in TypeScript code - always use proper typing, create interfaces, use unknown with type guards, or use generic types
• Use official types from modules instead of custom types - import and use existing types from @modelcontextprotocol/sdk and other modules rather than creating custom interfaces
• NEVER use emoji in code, comments, or console output - keep all text plain and professional
• Always return JSON from MCP tools instead of user-friendly strings
• Use filePath parameter for breakpoints, not scriptId
• Maintain consistent error handling patterns
• Apply DRY (Don't Repeat Yourself) principle everywhere except in tests - extract common patterns, shared utilities, and reusable functions
• Use modern ES features - prefer const/let over var, arrow functions, async/await, destructuring, optional chaining, nullish coalescing
• Use Node.js built-in promise-based APIs - prefer node:timers/promises over setTimeout, node:fs/promises over callback fs methods
• ABSOLUTELY MANDATORY: Use modern Promise-based timers with async/await - always use import { setTimeout } from "node:timers/promises" and async/await patterns instead of callback-based setTimeout
• ABSOLUTELY MANDATORY: NEVER use JSON.stringify in src/* - use the safe version (safe-stable-stringify) - import safeStringify from "safe-stable-stringify" and call safeStringify(value) everywhere. The safe version handles circular references, gives deterministic key order, and matches the project's wire-format guarantees. This rule applies to cache keys, log messages, MCP wire format, and any other serialization. The only allowed exception is template strings that are injected into the debuggee runtime via CDP Runtime.evaluate (where safe-stable-stringify is not available); document such exceptions inline. JSON.parse remains allowed for incoming JSON.
• Follow ESLint rules strictly - write code that passes linting without warnings, use ?? instead of ||, avoid unused variables, prefer explicit types
• No community docs until there is a community - do NOT add CONTRIBUTING.md or CODE_OF_CONDUCT.md. While the project has no external contributor community, these files are unnecessary; contributor guidance lives in AGENTS.md and the README Development section.