architecture-designer

Guide architectural decisions and document choices with ADRs.

2|Updated Mar 21, 2019

Search Tags:#architecture #scalability #system design #microservices #ADR #monolith

Ready to run

npx skills add https://github.com/jrollin/dotfiles --skill architecture-designer-jrollin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/jrollin/dotfiles/tree/main/claude/.claude/skills/architecture-designer
Command: npx skills add https://github.com/jrollin/dotfiles --skill architecture-designer-jrollin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design new system architectures, review existing ones, and make critical architectural decisions, ensuring robust, scalable, and maintainable systems.

Core Features & Use Cases

System Design: Guides you through the process of creating new system architectures.
Architecture Review: Assists in evaluating and improving existing system designs.
Decision Making: Helps in choosing between architectural patterns like monolith vs. microservices and documenting these decisions with ADRs.
Use Case: You are starting a new project and need to decide whether to build a monolith or microservices. This Skill will guide you through the decision tree and help you document your choice.

Quick Start

Use the architecture designer skill to help decide between a monolith and microservices for a new e-commerce platform.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema

How do I decide between a monolith and microservices for a new software system?▼

System architecture decisions between a monolith and microservices depend on your scalability requirements and project complexity. This Skill guides you through the decision tree and helps document your choice using ADRs.

What is the best way to document architectural decisions for distributed systems?▼

Documenting architectural decisions for distributed systems is best achieved by creating Architecture Decision Records (ADRs). This Skill helps you select architectural patterns and formally document these choices for maintainability.

How do I review an existing system architecture for scalability and maintainability?▼

To review an existing system architecture for scalability, you must evaluate current design patterns and distributed components. This Skill assists in evaluating and improving existing designs to ensure robust, maintainable systems.

Can I get guidance on designing event-driven architectures for complex software?▼

Yes, you can get expert guidance on designing event-driven architectures for complex software. This Skill supports complex system design scenarios including event-driven architectures and distributed systems to ensure robust implementation.

When should I not use microservices for system design?▼

You should avoid microservices for system design when your project lacks the operational complexity or scalability demands that justify distributed systems. This Skill helps evaluate constraints to choose appropriate architectural patterns like a monolith.