architectural-patterns

Identify and apply software architecture patterns to organize codebases.

3|Updated Feb 11, 2026

Search Tags:#architecture #patterns #hexagonal #clean-architecture #vertical-slice #modular-monolith

Ready to run

npx skills add https://github.com/deepnoodle-ai/creddit --skill architectural-patterns

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architectural-patterns
Source: https://github.com/deepnoodle-ai/creddit/tree/main/.claude/skills/architectural-patterns
Command: npx skills add https://github.com/deepnoodle-ai/creddit --skill architectural-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Reference provides a concise guide for identifying and applying proven software architecture patterns to structure and evolve large codebases, reduce coupling, and improve maintainability.

Core Features & Use Cases

Covers Clean Architecture, Hexagonal Architecture, Modular Monolith, and Vertical Slice Architecture, including typical layers, boundaries, and module layouts.
Helps teams decide which pattern fits project complexity, team size, and long-term maintenance goals.
Provides canonical structures and practical use-case scenarios to guide design decisions and implementation approaches.

Quick Start

Identify a suitable architecture pattern for your project and begin implementing it in your codebase.

Frequently Asked Questions about architectural-patterns

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

FAQPage Schema

When should I use Clean Architecture versus a Modular Monolith for my codebase?▼

Clean Architecture suits complex domains needing strict layer separation, while a Modular Monolith fits larger teams wanting isolated modules without distributed deployment overhead. Choose based on your domain complexity and team size to ensure long-term maintainability.

How does Hexagonal Architecture organize application boundaries?▼

Hexagonal Architecture organizes application logic around ports and adapters, isolating the core domain from external concerns like databases and UI. This reduces coupling and allows you to swap infrastructure components without modifying business rules.

What is Vertical Slice Architecture and when is it the best approach?▼

Vertical Slice Architecture organizes code by feature rather than technical layers, grouping all related components together. It is the best approach for smaller teams needing rapid iteration without the overhead of strict boundary enforcement found in complex patterns.

How do I decide which software architecture pattern fits my project?▼

Decide on a software architecture pattern by evaluating domain complexity, team size, and maintenance goals. Use canonical structures and decision criteria to match patterns like Clean Architecture or Vertical Slice to your specific scalability requirements.

Can I apply these architecture patterns to reduce coupling in existing applications?▼

Yes, you can apply these architecture patterns to reduce coupling in existing applications by defining canonical structures and strict boundaries. Refactoring toward a Modular Monolith or Hexagonal pattern helps isolate features and improve long-term maintainability.