Skill

architecture-patterns

Implements Clean Architecture, Hexagonal Architecture, and Domain-Driven Design for backend systems. Use for architecting complex backends or refactoring monoliths for maintainability.

backend

Install

npx claudepluginhub joshuarweaver/cascade-code-general-misc-2 --plugin rmyndharis-antigravity-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

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

168.3k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

168.3k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

168.3k

Stats

Stars682

Forks124

Last CommitJan 18, 2026

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.

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

Resources

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