Does this skill help with documentation?

Yes, it includes specialized templates and a workflow for generating Architecture Decision Records (ADRs) to document the rationale behind design choices.

Does it support modern infrastructure patterns?

Absolutely. It promotes 'Modern by Default' patterns including containerization, Infrastructure as Code (IaC), and distributed tracing.

How does it handle scaling?

It provides guidance on identifying bottlenecks, capacity planning, and implementing horizontal or vertical scaling strategies for databases and services.

When should I use the Architecture skill?

Use it when designing new systems, evaluating major features, making technology stack decisions, or planning for scale and performance.

Can it help choose between Rust and TypeScript?

Yes, the skill contains specific comparison frameworks for Rust and TypeScript, evaluating them based on performance, memory safety, and developer velocity.

System Architecture & Design

Name: System Architecture & Design
Author: outfitter-dev

byoutfitter-dev

•

API 개발

Guides the design, evaluation, and documentation of scalable software systems using proven architectural patterns and technology selection frameworks.

소개

This skill empowers Claude to act as a senior software architect, facilitating high-level system design from initial discovery through to formal documentation. It provides structured frameworks for choosing technology stacks, planning for horizontal and vertical scale, and implementing critical patterns such as microservices, event-driven systems, and observability. By focusing on architectural tradeoffs and 'complexity budgets,' it helps developers avoid over-engineering while ensuring systems remain maintainable, observable, and ready for future growth through the generation of formal Architecture Decision Records (ADRs).

주요 기능

Architecture Decision Record (ADR) generation and documentation
Scalability planning and performance bottleneck identification
Implementation of modern patterns (Microservices, Event-driven, BFF)
Observability-first design for metrics, tracing, and logging
Technology stack selection frameworks and tradeoff analysis
18 GitHub stars

사용 사례

Evaluating whether to migrate from a monolith to microservices or serverless
Documenting major technical decisions via a formal ADR process
Designing a greenfield system architecture with a focus on scale and performance

소개

주요 기능

Architecture Decision Record (ADR) generation and documentation
Scalability planning and performance bottleneck identification
Implementation of modern patterns (Microservices, Event-driven, BFF)
Observability-first design for metrics, tracing, and logging
Technology stack selection frameworks and tradeoff analysis
18 GitHub stars

사용 사례

Evaluating whether to migrate from a monolith to microservices or serverless
Documenting major technical decisions via a formal ADR process
Designing a greenfield system architecture with a focus on scale and performance