architecture

Guide interactive architecture decisions and output a coherent design document.

1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/tubone24/claude-code-settings --skill architecture-tubone24
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/tubone24/claude-code-settings/tree/main/skills/architecture
Command: npx skills add https://github.com/tubone24/claude-code-settings --skill architecture-tubone24

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design teams need a structured approach to craft scalable, maintainable software architectures, guiding decisions across patterns and technologies.

Core Features & Use Cases

  • Interactive design flow for selecting architecture styles (DDD, Clean Architecture, microservices, event-driven) based on project context.
  • Technology guidance and reference templates to accelerate architecture documentation.
  • Comprehensive references in references/ to support detailed design decisions and governance.

Quick Start

Define your project goals and run the interactive design flow to choose an architecture style and technology stack.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I design scalable software architecture for microservices and event-driven systems?

To design scalable software architecture, use an interactive design flow that evaluates project context to recommend architecture styles like microservices or event-driven patterns, producing a coherent design document aligned with best practices.

What is domain-driven design and when should I use it for my project?

Domain-driven design (DDD) is an architecture style that models complex software around business domains. You should use DDD when your project requires structured alignment between technical and business layers, guided by interactive decision points and reference templates.

How do I document clean architecture decisions and technology choices?

Document clean architecture decisions by defining project goals and running an interactive design flow that specifies decision points and reference templates. This accelerates architecture documentation and ensures governance across the selected technology stack.

Can I use this architecture design flow for small projects or is it only for large systems?

You can use this architecture design flow for projects of varying sizes. It guides scalable software architecture decisions by evaluating project context, making it applicable for selecting tech stacks across both small applications and large microservices systems.

What is the best way to choose between microservices and clean architecture?

The best way to choose between microservices and clean architecture is through an interactive design flow that evaluates project context. This guided process specifies decision points and uses references to recommend the appropriate scalable architecture style.