pokemon-go-mcp: Skill for Claude Code

Universal Best Practices

This skill provides comprehensive guidance on software engineering best practices that apply across all programming languages and project types. Follow these principles to ensure clean, maintainable, production-ready code.

Core Workflow

When writing or reviewing code:

1. Start with KISS and YAGNI - implement the simplest thing that solves the current need
2. Apply SOLID principles to structure your classes and modules
3. Ensure DRY by eliminating duplication
4. Use SoC to separate concerns into distinct responsibilities
5. Follow LoD to minimize coupling between components
6. Apply remaining principles as relevant to your specific context

Fundamental Principles

SOLID

Five core object-oriented design principles that make code maintainable and flexible:

S - Single Responsibility Principle (SRP)

• Each class/module should have only ONE reason to change
• One class = one job or responsibility
• Example: Separate UserRepository (data access) from UserValidator (validation logic)
• Benefit: Changes to one responsibility don't affect unrelated code

O - Open/Closed Principle (OCP)

• Open for extension, closed for modification
• Add new functionality without changing existing code
• Use interfaces, abstract classes, or inheritance to extend behavior
• Example: Plugin systems, strategy patterns
• Benefit: Add features without risking existing functionality

L - Liskov Substitution Principle (LSP)

• Subtypes must be substitutable for their base types
• Child classes shouldn't break parent class contracts
• Example: If Bird has fly(), don't create Penguin extends Bird - penguins can't fly
• Benefit: Polymorphism works correctly, no surprises

I - Interface Segregation Principle (ISP)

• No class should implement methods it doesn't use
• Many specific interfaces > one general interface
• Example: Split IWorker into IWorkable and IEatable instead of forcing robots to implement eat()
• Benefit: Lean interfaces, no unnecessary dependencies