MCP Clean Code Planner

A detailed tool for planning and creating clean, well-structured code with comprehensive English comments. This tool helps analyze coding problems through a flexible planning process that focuses on code quality and readability. Each step can address different aspects of clean code principles and best practices. When to use this tool: - Before writing complex code that needs careful planning - When designing a new feature or refactoring existing code - When code structure and organization are critical - For ensuring comprehensive documentation with English comments - For following clean code principles and best practices - For breaking down complex functionality into modular components - For planning testable and maintainable implementations Key features: - You can plan your code architecture step by step - You can revise previous design decisions as requirements become clearer - You can branch into alternative implementation strategies - You can focus on different aspects of clean code in each step - Creates well-documented, readable, and maintainable code - Follows established coding conventions and best practices - Prioritizes simplicity and clarity over cleverness Parameters explained: - thought: Your current code planning step, which can include: * Architecture and design considerations * Module and component organization * Function signature planning * Comments and documentation strategies * Error handling approaches * Performance considerations * Testing strategies * Revisions to previous design decisions * Alternative implementation approaches - next_thought_needed: True if you need more planning steps before finalizing - thought_number: Current step number in sequence - total_thoughts: Current estimate of steps needed - is_revision: A boolean indicating if this step revises previous thinking - revises_thought: If is_revision is true, which step number is being reconsidered - branch_from_thought: If branching, which step number is the branching point - branch_id: Identifier for the current implementation alternative - needs_more_thoughts: If reaching end but realizing more planning is needed You should: 1. Start with high-level architecture and design considerations 2. Break down complex functionality into smaller, modular components 3. Plan function signatures, interfaces, and data structures 4. Consider error handling and edge cases 5. Draft comprehensive comments that explain the "why" not just the "what" 6. Follow the SOLID principles and other clean code practices 7. Prioritize readability and maintainability over cleverness 8. Plan for testability from the beginning 9. Only set next_thought_needed to false when the code planning is complete 10. Produce code that is clear, concise, and well-documented in English