java-design-principles
A comprehensive guide providing essential design principles and best practices for Java development
What this skill does
# Java Design Principles A comprehensive guide providing essential design principles and best practices for Java development. Structured for step-by-step learning from beginners to advanced developers. ## When to Use This Skill Use this skill in the following situations: - 🏗️ **When designing new Java projects** - Apply correct principles when making architectural decisions - 🔧 **When refactoring existing code** - Check guidelines for code quality improvement - 👀 **When performing code reviews** - Systematically review for design principle violations - 🎯 **When making class design decisions** - Inheritance vs composition, interface segregation, etc. - 🧩 **When managing dependencies between modules** - Methods to reduce coupling and increase cohesion - 📚 **When training junior developers** - Systematically convey core design principles - 🐛 **When resolving technical debt** - Identify which principles have been violated and improve ## 📚 Learning Path ### 🌱 Beginner - Starting with Simplicity An introductory course for those learning design principles for the first time. 1. **[Simplicity Principles](./core-concepts/simplicity-principles.md)** - KISS (Keep It Simple, Stupid) - YAGNI (You Aren't Gonna Need It) - Do The Simplest Thing That Could Possibly Work 💡 *Why learn this first?* Before learning complex principles, developing the habit of writing simple code is most important. ### 🚀 Intermediate - Core Design Principles Learn the core principles of object-oriented design. 2. **[SOLID Principles](./core-concepts/solid-principles.md)** - Single Responsibility Principle - Open/Closed Principle - Liskov Substitution Principle - Interface Segregation Principle - Dependency Inversion Principle 💡 *Why is this important?* SOLID is an essential principle for writing maintainable and extensible code. 3. **[Coupling and Cohesion](./core-concepts/coupling-cohesion.md)** - DRY (Don't Repeat Yourself) - Separation of Concerns - Minimize Coupling / Maximize Cohesion - Law of Demeter - Composition Over Inheritance 💡 *Practical Application:* Learn how to properly design relationships between modules. ### 🎯 Advanced - In-depth Principles and Patterns Learn more in-depth design principles and practical patterns. 4. **[Encapsulation](./core-concepts/encapsulation.md)** - Encapsulation & Information Hiding - Encapsulate What Changes 5. **[Advanced Principles](./core-concepts/advanced-principles.md)** - Code For The Maintainer - Boy-Scout Rule - Avoid Premature Optimization - Inversion of Control - Command Query Separation - Robustness Principle (Postel's Law) 6. **[Practical Patterns](./patterns/common-patterns.md)** - Good vs Bad examples of 5 core patterns - Single Responsibility - Open/Closed - Law of Demeter - Composition Over Inheritance - DRY ## 📖 Additional Resources - **[Best Practices & Common Pitfalls](./best-practices.md)** - Checklists for design/coding/maintenance - 8 common mistakes to avoid - **[Resources](./resources.md)** - Essential books - Online resources - Practice materials ## 🎓 Learning Tips ### Recommended Order for Beginners 1. **Week 1**: Read and practice simplicity principles 2. **Week 2-3**: Learn SOLID principles one by one (one per day) 3. **Week 4**: Understand coupling/cohesion concepts 4. **Week 5**: Practice with practical patterns 5. **Week 6+**: Code review with Best Practices checklist ### For Those with Experience - Learn selectively starting with principles of interest - Read Common Pitfalls first and apply to your current code - Use this guide as reference documentation during team code reviews ## 📂 Project Structure ``` java-design-principles/ ├── SKILL.md (this file) ├── core-concepts/ │ ├── simplicity-principles.md │ ├── solid-principles.md │ ├── coupling-cohesion.md │ ├── encapsulation.md │ └── advanced-principles.md ├── patterns/ │ └── common-patterns.md ├── best-practices.md └── resources.md ``` ## 🤝 Contributing If you want to contribute to this guide: - Open an issue if you find typos or improvements - Send a Pull Request if you have better examples - Share practical use cases --- **License**: MIT **Last Updated**: November 2025 Happy Coding! 🚀
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.