home / Coding / Architecture Patterns Skill by @sickn33

Architecture Patterns Skill by @sickn33

FREE

github stars★ 48,690updatedOct 2026repo@sickn33

activity (commits, last 6 months)

6mo ago0

this month1

$git clone https://github.com/sickn33/agentic-awesome-skills

The skill is the skills/architecture-patterns folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.

about Architecture Patterns Skill by @sickn33

Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable.

our take

Explains backend architecture styles, including Clean Architecture, Hexagonal Architecture and Domain-Driven Design, so an agent can structure a codebase to be maintainable and testable.

when to use it

You are designing the layers of a new backend
A codebase has business logic tangled with framework code
You want to talk through trade-offs between architecture styles

before you install

These patterns add structure that small projects may not need
Apply them to the parts of the system that benefit, not everywhere

what's inside

The original SKILL.md is organised into these sections:

Use this skill when
Do not use this skill when
Instructions
Related Skills
Resources
Limitations

source and license

Written and maintained by @sickn33. It is published under the MIT license, which allows reuse with attribution. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.

View the full SKILL.md on GitHub ↗

Read the opening of the original SKILL.md

# Architecture Patterns

Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.

## Use this skill when

- Designing new backend systems from scratch
- Refactoring monolithic applications for better maintainability
- Establishing architecture standards for your team
- Migrating from tightly coupled to loosely coupled architectures
- Implementing domain-driven design principles
- Creating testable and mockable codebases
- Planning microservices decomposition

## Do not use this skill when

- You only need small, localized refactors
- The system is primarily frontend with no backend architecture changes
- You need implementation details without architectural design

## Instructions

1. Clarify domain boundaries, constraints, and scalability targets.
2. Select an architecture pattern that fits the domain complexity.
…

Excerpt only, quoted from the author's repository. Open the repository for the complete file.

↓ download .zip