architecture-patterns

Guide backend architecture implementation with playbooks and templates for Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/angga30/antigravity-skill-tech-lead --skill architecture-patterns-angga30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-patterns
Source: https://github.com/angga30/antigravity-skill-tech-lead/tree/main/architecture-patterns
Command: npx skills add https://github.com/angga30/antigravity-skill-tech-lead --skill architecture-patterns-angga30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backend system design often suffers from inconsistency, rigidity, and unclear boundaries. This Skill provides a structured approach to applying proven patterns like Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to create maintainable, scalable backends.

Core Features & Use Cases

  • Provides a clear framework for choosing and applying backend architecture patterns across languages (Go, Python, Rust).
  • Supplies playbooks, templates, and references to guide architects through boundary definition, dependency rules, and module structuring.
  • Enables cross-team alignment by standardizing architectural decisions, migration plans, and validation checks for refactors or new projects.

Quick Start

Identify domain boundaries, select an appropriate architecture pattern, and outline the system structure accordingly.

Frequently Asked Questions about architecture-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement Clean Architecture and Domain-Driven Design in my backend?

Structure modular backends using Clean Architecture by defining clear domain boundaries, enforcing dependency rules, and applying provided playbooks to outline scalable system structures.

What is the best way to structure a backend using Hexagonal Architecture?

Structure a backend using Hexagonal Architecture by organizing the system around ports and adapters, which isolates the core domain logic from external infrastructure and enables maintainable scaling.

Does this architecture patterns guidance work with Go, Python, and Rust?

Yes, this architecture patterns guidance explicitly supports Go, Python, and Rust, providing practical templates and references to standardize backend design decisions across these multiple languages.

How do I define domain boundaries for a DDD backend refactor?

Define domain boundaries for a DDD backend refactor by following structured validation steps and migration plans that enforce clear modular limits, ensuring alignment across cross-functional teams.

When should I not use Hexagonal Architecture for my backend?

Avoid using Hexagonal Architecture for backends where strict domain boundaries and ports add unnecessary rigidity, especially if the project scale does not justify the overhead of isolating adapters.