solid-patterns

Assess design pattern application for code review and refactoring decisions.

Updated May 7, 2026
One-click install
npx skills add https://github.com/cornellsh/arch-dotfiles --skill solid-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solid-patterns
Source: https://github.com/cornellsh/arch-dotfiles/tree/main/agents/skills/solid-patterns
Command: npx skills add https://github.com/cornellsh/arch-dotfiles --skill solid-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) and assets (resource) components.

What problem does it solve?

It helps software engineers and architects decide when to apply design principles like SOLID, and specific patterns such as Strategy, State, Adapter, Factory Method, Decorator, and Singleton, to produce flexible, maintainable systems.

Core Features & Use Cases

  • Provides a rigorous decision-making framework for applying design patterns based on real symptoms and context.
  • Offers detailed references for each principle and pattern to deepen understanding.
  • Guides users through best practices in code review, refactoring, and design decisions involving object-oriented structures and architectural patterns.
  • Suitable for designing new systems, evaluating existing designs, or reviewing code with an emphasis on loose coupling and scalable architecture.

Quick Start

Ask the AI to analyze a code structure and determine if applying the singleton pattern is appropriate, based on current dependencies and flexibility needs.

Frequently Asked Questions about solid-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I apply SOLID principles and design patterns during code refactoring?

Use SOLID principles and design patterns during refactoring when you observe tight coupling or rigid structures. This framework assesses real symptoms to guide context-aware pattern application, ensuring maintainable object-oriented architecture with minimal complexity.

How do I know if using the Singleton pattern is appropriate for my code structure?

Assess if the Singleton pattern is appropriate by analyzing current dependencies and flexibility needs. This framework evaluates your code structure to determine if a Singleton provides scalable architectural benefits or introduces unnecessary complexity to your object-oriented design.

How do I choose between Strategy and State patterns for my architecture decisions?

Choosing between Strategy and State patterns depends on your specific architectural context and symptoms. This framework provides a rigorous decision-making process to help you select the exact pattern that resolves your structural problem while maintaining loose coupling and scalable architecture.

Can I use this framework to review existing object-oriented code for design pattern misuse?

Yes, you can use this framework to review existing object-oriented code for design pattern misuse. It evaluates current designs against principles like SOLID, highlighting where patterns like Adapter or Decorator are incorrectly applied or add unnecessary complexity.

What are the limitations of applying design patterns to create scalable systems?

The primary limitation of applying design patterns is the risk of introducing unnecessary complexity. This framework emphasizes context-aware, minimal complexity solutions, ensuring patterns like Factory Method or Decorator are only used when they provide genuine architectural value.