skills.rest
swaylq
swaylqCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

software-architecture-master

Guide software architecture decisions with explicit trade-offs for scalability, coupling, consistency, and evolvability.

114|12|Updated May 18, 2026
Search Tags:#system design#data modeling#software architecture#distributed systems#ADR#trade-off analysis#service boundaries
One-click install
npx skills add https://github.com/swaylq/master-skill --skill software-architecture-master
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: software-architecture-master
Source: https://github.com/swaylq/master-skill/tree/main/prototypes/software-architecture-master/output
Command: npx skills add https://github.com/swaylq/master-skill --skill software-architecture-master

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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?”

Frequently Asked Questions about software-architecture-master

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

FAQPage Schema
How do I decide between a modular monolith and microservices for a distributed backend?▼

Evaluating architectural patterns requires explicit trade-off analysis across scalability, coupling, consistency, and evolvability. By translating your distributed backend's latency and growth goals into decision criteria, you can rationally choose between a modular monolith or microservices approach.

What is the best way to design service boundaries and API contracts for distributed systems?▼

Designing service boundaries and API contracts requires an architecture-first workflow with context discovery. Structured playbook-style recommendations help define data flow and integration design while ensuring your system maintains evolvability and proper consistency strategies.

How do I model data and manage consistency strategies in an event-driven architecture?▼

Data model design and consistency strategies in event-driven distributed systems require trade-off analysis across CAP theorem constraints. Applying patterns like Saga, outbox, and idempotency helps manage eventual consistency and data flow effectively across service boundaries.

When do I need formal architecture decision records for system design?▼

You need architecture decision records when evaluating complex trade-offs for scalability and coupling in distributed back-ends. Maintaining ADR hygiene and validating evolution paths with fitness functions ensures your architectural choices remain aligned with future change axes.

Does this approach work for mobile and web application architecture or only distributed back-ends?▼

This architecture-first workflow applies to application and system architecture across web, mobile, and distributed back-ends. It provides senior-level guidance for service design, API boundaries, and data modeling regardless of your specific platform or client type.

Related Skills

Explore More Software Engineering Skills→
jagreehaljagreehal
3

system-architecture

Document architecture decisions and trade-offs using ADR patterns.

Community
Basic
jikig-aijikig-ai
12

architecture-strategist

Analyze code changes for architectural consistency and design integrity.

Official
Advanced
yonatangrossyonatangross
217

testing-integration

Validate API boundaries and cross-service contracts with Pact, Supertest, httpx, and Hypothesis.

Community
Advanced
Eigo-Mt-FujiEigo-Mt-Fuji

system-architect

Design scalable, secure architectures with C4 diagrams, ADRs, and trade-off analysis.

Community
Advanced