What architecture patterns does this skill support?

The skill provides guidance for various industry-standard patterns including Layered Architecture and Hexagonal (Ports & Adapters) Architecture.

What is the difference between Architecture Design and Technical Planning?

Architecture Design is strategic, focusing on high-level structure, component boundaries, and long-term implications. Technical Planning is tactical, focusing on specific implementation tasks and execution details for a feature.

Can this skill help with system reliability?

Yes, it includes a dedicated process for failure planning, identifying potential points of failure, and proposing mitigation strategies like circuit breakers and graceful degradation.

How does this skill help with technology selection?

It provides a framework for considering alternatives (e.g., PostgreSQL vs. MongoDB), weighing pros and cons against project constraints, and documenting the final decision in an ADR.

What are the core principles used by this skill?

It follows principles such as Simplicity (YAGNI), Separation of Concerns, Loose Coupling, High Cohesion, and Design for Testability.

Architecture Design

Name: Architecture Design
Author: TheBushidoCollective

byTheBushidoCollective

•

API開発

Designs robust system architectures and guides high-level technical decision-making for long-term scalability and maintainability.

概要

The Architecture Design skill empowers Claude to act as a seasoned software architect, focusing on strategic system structure rather than tactical implementation. It facilitates the creation of high-level blueprints, helps evaluate technology trade-offs through formalized Architecture Decision Records (ADRs), defines component boundaries, and plans for system resilience. This skill is essential when starting new projects, performing major refactors, or making foundational technology choices that impact the long-term success and simplicity of a software system.

主な機能

Technical constraint identification and trade-off analysis
Automated generation of Architecture Decision Records (ADRs)
Structured requirement gathering for functional and non-functional goals
Resilience planning for failure scenarios and edge cases
Component-based system mapping and interface definition
39 GitHub stars

ユースケース

Evaluating and documenting the impact of technology migrations or pattern changes
Designing a new system or subsystem from scratch including tech stack selection
Planning major refactors that affect multiple components and system boundaries

概要

主な機能

Technical constraint identification and trade-off analysis
Automated generation of Architecture Decision Records (ADRs)
Structured requirement gathering for functional and non-functional goals
Resilience planning for failure scenarios and edge cases
Component-based system mapping and interface definition
39 GitHub stars

ユースケース

Evaluating and documenting the impact of technology migrations or pattern changes
Designing a new system or subsystem from scratch including tech stack selection
Planning major refactors that affect multiple components and system boundaries