Skill

architecture-patterns

Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing ...

npx claudepluginhub absjaded/antigravity-awesome-skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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

Supporting Assets

resources/implementation-playbook.md

SKILL.md

Similar Skills

finishing-a-development-branch

174.6k

Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.

superpowers

systematic-debugging

174.6k

Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.

10 files

superpowers

writing-plans

174.6k

Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.

1 file

superpowers

Stats

Stars0

Forks0

Last CommitMar 3, 2026

Used By3 plugins

Actions

View Source View Plugin View on GitHub View README

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

Clarify domain boundaries, constraints, and scalability targets.

Select an architecture pattern that fits the domain complexity.

Define module boundaries, interfaces, and dependency rules.

Provide migration steps and validation checks.

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.