Skill

architecture-patterns

Implements Clean Architecture, Hexagonal Architecture, and Domain-Driven Design for maintainable, testable backend systems. Use for new designs, refactoring monoliths, or microservices planning.

backend

From antigravity-awesome-skills

Install

Run in your terminal

npx claudepluginhub sickn33/antigravity-awesome-skills --plugin antigravity-awesome-skills

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

resources/implementation-playbook.md

Skill Content

Similar Skills

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

139.9k

agent-payment-x402

Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.

everything-claude-code

139.9k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

139.9k

Stats

Parent Repo Stars30787

Parent Repo Forks5140

Last CommitMar 29, 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.
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.