advanced-patterns

Guide architecture decisions with SOLID and 12-Factor patterns.

16|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/JCE-Joshhh77/JCE-Opencode-Tools --skill advanced-patterns-jce-joshhh77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: advanced-patterns
Source: https://github.com/JCE-Joshhh77/JCE-Opencode-Tools/tree/main/config/skills/advanced-patterns
Command: npx skills add https://github.com/JCE-Joshhh77/JCE-Opencode-Tools --skill advanced-patterns-jce-joshhh77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams struggle to apply core architectural patterns consistently across projects, leading to fragile systems and maintenance challenges.

Core Features & Use Cases

  • Enforces SOLID and 12-Factor principles to improve modularity, resilience, and scalability.
  • Provides decision trees and practical examples for architecture choices in large-scale applications.
  • Use Case: when starting a new service, apply the patterns to define boundaries, dependencies, and deployment readiness.

Quick Start

Propose a starter workflow to apply architecture patterns to a sample project.

Frequently Asked Questions about advanced-patterns

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

FAQPage Schema
How do I apply SOLID principles to improve software modularity?

Applying SOLID principles for modularity involves enforcing them during architecture decisions to define boundaries and dependencies, which directly improves maintainability and reduces system fragility across projects.

What is the best way to choose architecture patterns for scalable applications?

Choosing architecture patterns for scalable applications is best done using decision trees and practical examples to guide pattern selection, ensuring modularity, resilience, and scalable deployment readiness.

How do I enforce 12-Factor practices when starting a new service?

Enforcing 12-Factor practices when starting a new service involves applying the patterns to define boundaries, dependencies, and deployment readiness, ensuring the architecture supports scalable and maintainable deployment.

When do I need a circuit breaker pattern in system architecture?

You need a circuit breaker pattern in system architecture when building resilient systems, acting as an implementation pattern to prevent cascading failures and maintain stability across modular components.

Does this approach work for large-scale applications requiring high performance?

This approach works for large-scale applications requiring high performance by providing architecture choices and decision trees specifically designed to handle scalability, modularity, and resilient deployment.

Why does inconsistent architecture lead to fragile systems?

Inconsistent architecture leads to fragile systems because design teams struggle to apply core architectural patterns uniformly across projects, causing maintenance challenges and poor resilience.