Skip to content
Skillpedia
APIs & servers (backend)48k · #2196

architecture-patterns

Lets your agent use proven backend architecture patterns. This results in systems that are easy to maintain, test, and scale.

What it does

This tool helps plan the structure of computer systems (backend) to make them easy to maintain, test, and scale. It teaches about methods like Clean Architecture and Domain-Driven Design.

When to use it

  • ✓When creating a new system from scratch.
  • ✓When organizing a large, messy system.
  • ✓When defining rules for how code should be written by a team.

Example of what to ask your AI

“How can I structure a new e-commerce application using Clean Architecture?”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/architecture-patterns/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/architecture-patterns/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool analyzes the problem, suggests a suitable organization method, and defines how system parts should communicate and what rules they should follow.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill architecture-patterns

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/architecture-patterns/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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.
  3. Define module boundaries, interfaces, and dependency rules.
  4. Provide migration steps and validation checks.
  5. For workflows that must survive failures (payments, order fulfillment, multi-step processes), use durable execution at the infrastructure layer — frameworks like DBOS persist workflow state, providing crash recovery without adding architectural complexity.

Refer to resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Related Skills

Works well with: event-sourcing-architect, saga-orchestration, workflow-automation, dbos-*

Resources

  • resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
FAQ

What are 'architecture patterns'?

They are like recipes or blueprints that help build software systems in an organized and efficient way.

Why is a good architecture important?

A good architecture makes the system easier to understand, modify, fix, and scale (increase capacity) in the future.

When should I not use this tool?

If you only need to make small changes or if the focus is solely on the visual part (frontend) of the application, without altering the core structure.

Details

Original description by the author

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

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#2196
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills