What is the difference between architecture patterns and design patterns?

Architecture patterns describe system-wide organization and interactions, while design patterns solve problems inside individual components (creational, structural, behavioral).

How do Architecture Decision Records (ADRs) help?

ADRs document decisions, alternatives considered, rationale, and status, keeping stakeholders aligned and guiding future changes.

When should distributed architectures be considered?

When scalability, resilience, and independent deployment are required; evaluate service boundaries, data ownership, and patterns like service communication, data consistency, and event-driven design.

architecture

skill

npx machina-cli add skill Fujigo-Software/f5-framework-claude/architecture --openclaw

Files (1)

SKILL.md

2.2 KB

Architecture Skills

Overview

This module covers fundamental and advanced architecture concepts applicable across all technology stacks.

When to Use

Starting new projects
Refactoring legacy systems
Making architecture decisions
Code review and design discussions
Team knowledge sharing

Directory Structure

skills/architecture/
├── _index.md
├── principles/
│   ├── solid.md
│   ├── dry-kiss-yagni.md
│   ├── separation-of-concerns.md
│   └── dependency-inversion.md
├── patterns/
│   ├── clean-architecture.md
│   ├── hexagonal-architecture.md
│   ├── layered-architecture.md
│   ├── domain-driven-design.md
│   ├── cqrs-event-sourcing.md
│   └── microservices.md
├── design-patterns/
│   ├── creational/
│   ├── structural/
│   └── behavioral/
├── distributed-systems/
└── decision-making/

Integration with F5 Framework

These skills are referenced by:

Stack templates for implementation guidance
Agents for architecture decisions
Quality gates for design review

Source

git clone https://github.com/Fujigo-Software/f5-framework-claude/blob/main/plugins/f5-core/skills/architecture/SKILL.mdView on GitHub

Overview

This skill covers core and advanced software architecture concepts applicable across technology stacks. It organizes systems using patterns, principles, and decision-making practices to improve scalability, maintainability, and resilience.

How This Skill Works

Knowledge is organized into Principles, Patterns, Design Patterns, Distributed Systems, and Decision Making. Practitioners select appropriate patterns (e.g., Clean, Hexagonal, Layered, Domain-Driven Design, CQRS) and document choices using Architecture Decision Records (ADR) and trade-off analyses to guide implementation.

When to Use It

Starting new projects
Refactoring legacy systems
Making architecture decisions
Code review and design discussions
Team knowledge sharing

Quick Start

Step 1: Gather requirements, constraints, quality attributes, and domain boundaries
Step 2: Choose a suitable architecture pattern (e.g., Clean/Hexagonal) and relevant design patterns
Step 3: Create an Architecture Decision Record (ADR) and draft a high-level component map

Best Practices

Apply SOLID principles and DRY/KISS/YAGNI to guide design decisions
Enforce Separation of Concerns across architectural layers
Use Dependency Inversion to decouple components
Select architecture patterns (Clean, Hexagonal, Layered, DDD, CQRS) based on domain needs
Capture decisions with Architecture Decision Records (ADR) and explicit trade-off analysis

Example Use Cases

Starting a new project with a layered/clean architecture to isolate business rules from infrastructure
Refactoring a monolith into modular boundaries to improve testability and deployment
Applying CQRS and Event Sourcing for high-throughput domains with complex consistency requirements
Documenting major decisions with ADRs to communicate rationale and alternatives
Designing distributed services with proper service communication and event-driven patterns