How does it handle architectural documentation?

It follows a structured process to generate Architecture Decision Records (ADRs) that document the context, decision, alternatives considered, and long-term consequences.

When should I use the Software Architecture skill?

Use this skill when designing new systems, making major technology stack decisions, evaluating architectural approaches, or planning for performance and scale.

Can it help with scaling existing applications?

Absolutely. It provides frameworks for analyzing resource bottlenecks (CPU, Memory, I/O) and suggests scaling strategies like horizontal scaling, caching layers, and database sharding.

Does this skill support Rust development?

Yes, it includes specialized guidance on when to choose Rust over TypeScript and recommends modern Rust stacks like Axum, Actix, and Tokio for performance-critical services.

Software Architecture & System Design

Name: Software Architecture & System Design
Author: outfitter-dev

byoutfitter-dev

•

API Development

Guides system design, technology selection, and architectural tradeoff analysis using industry-proven patterns and frameworks.

About

This skill empowers Claude to act as a senior architect, helping developers design scalable systems, evaluate technology stacks, and document decisions through Architecture Decision Records (ADRs). It follows a structured workflow from requirement discovery to implementation planning, focusing on observability, scalability, and complexity management. Whether you are deciding between Rust and TypeScript or planning a migration from a monolith to microservices, this skill provides the necessary frameworks and principles to build resilient, production-ready software.

Key Features

Scalability and performance modeling to identify and resolve system bottlenecks
16 GitHub stars
Structured technology selection frameworks for databases, frameworks, and infrastructure
Comparative analysis of tech stacks including Rust vs. TypeScript performance metrics
Automated Architecture Decision Record (ADR) generation to document tradeoffs
Guidance on modern patterns like CQRS, Event-Sourcing, and Service Decomposition

Use Cases

Designing a new greenfield project with a scalable and maintainable tech stack
Planning for system growth by identifying future bottlenecks and performance requirements
Evaluating the pros and cons of migrating a monolithic service into microservices

About

Key Features

Scalability and performance modeling to identify and resolve system bottlenecks
16 GitHub stars
Structured technology selection frameworks for databases, frameworks, and infrastructure
Comparative analysis of tech stacks including Rust vs. TypeScript performance metrics
Automated Architecture Decision Record (ADR) generation to document tradeoffs
Guidance on modern patterns like CQRS, Event-Sourcing, and Service Decomposition

Use Cases

Designing a new greenfield project with a scalable and maintainable tech stack
Planning for system growth by identifying future bottlenecks and performance requirements
Evaluating the pros and cons of migrating a monolithic service into microservices