senior-architect

Design scalable distributed system architectures and create ADRs.

467|103|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/borghei/Claude-Skills --skill senior-architect-borghei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-architect
Source: https://github.com/borghei/Claude-Skills/tree/main/engineering/senior-architect
Command: npx skills add https://github.com/borghei/Claude-Skills --skill senior-architect-borghei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Senior Software Architect skill provides a structured framework for designing scalable, reliable software systems. It helps engineering teams make informed architectural decisions, evaluate patterns, and document decisions to align with business goals.

Core Features & Use Cases

  • System design guidance for distributed architectures (monoliths, microservices, and event-driven designs).
  • Architecture decision records (ADRs) creation, pattern evaluation, and architecture governance.
  • Comparative analysis of Layered, Hexagonal, and Event-Driven architectures with diagrams and trade-offs.
  • Documentation templates for architecture diagrams, decisions, and performance considerations.
  • Use Case: when starting a new platform, define module boundaries, communication protocols, data ownership, and scalability requirements.

Quick Start

Provide a scenario or constraints and request an ADR, architecture outline, and evaluation criteria to begin the design process.

Frequently Asked Questions about senior-architect

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

FAQPage Schema
How do I design scalable microservices and define module boundaries for a new platform?

Architecture decision records (ADRs) document architectural choices, evaluate patterns, and align engineering teams with business goals. This skill generates ADRs alongside architecture diagrams and performance considerations to provide structured design governance.

What is the best way to compare Layered, Hexagonal, and Event-Driven architectures?

Comparing Layered, Hexagonal, and Event-Driven architectures requires evaluating structured trade-offs. This skill provides comparative analysis with architecture diagrams and evaluation criteria to help you choose the right distributed system pattern.

How do I create architecture documentation for distributed systems?

You start by providing a project scenario or technical constraints. The skill then processes these inputs to output a complete architecture outline, ADRs, and evaluation criteria for your tech choices, requiring no external dependencies to begin.

When should I not use microservices for my distributed system design?

You should evaluate microservices trade-offs against monoliths and event-driven designs. The skill enforces structured comparative analysis with evaluation criteria to determine if a monolithic or event-driven approach better fits your scalability requirements.