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-bundle-architecture-design

Install

Run in your terminal

npx claudepluginhub sickn33/antigravity-awesome-skills --plugin antigravity-bundle-architecture-design

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

resources/implementation-playbook.md

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

cost-optimization

1 file

Optimizes cloud costs on AWS, Azure, GCP via rightsizing, tagging strategies, reserved instances, spot usage, and spending analysis. Use for expense reduction and governance.

cloud-infrastructure

33.0k

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.