software-architecture-master

What problem does it solve?

This Skill helps you make high-quality software architecture decisions for application and system design in web, mobile, and distributed back-ends—especially when you need explicit trade-offs across scalability, coupling, consistency, and evolvability.

Core Features & Use Cases

• Architecture decision guidance (trade-offs first): Translates your problem into explicit architectural questions and decision criteria rather than tool-first suggestions.
• Service boundaries, data models, and integration design: Helps you design service boundaries, API contracts, data flow, and consistency strategies with evolution in mind.
• Playbook + protocol-driven workflow: Uses an “Agentic Protocol” research workflow and a structured playbook to produce an actionable architecture answer aligned to context and constraints.

Use case examples

• You’re choosing between architectural patterns (monolith vs modular monolith vs microservices, event-driven vs sync) and need a rationale tied to future change axes.
• You need to design data models and consistency strategies (CAP, eventual consistency, Saga/outbox/idempotency) for distributed systems.
• You’re validating an approach to observability, ADR/decision hygiene, and an evolution path with fitness functions.

Quick Start

Activate the skill and ask: “I’m designing a distributed backend for a multi-client web/mobile product; should we start with modular monolith or microservices, and what consistency and evolution strategy should we use given our latency and growth goals?”