skills.rest
flexigpt
flexigptOFFICIAL
Explore all skills by this author →
GitHub

designing-system-architecture

Compare architecture options and produce ADR-ready recommendations with trade-offs.

4|1|Updated Jul 23, 2024
Search Tags:#design#architecture#adr#patterns#event-driven#decision-making#bounded-context
One-click install
npx skills add https://github.com/flexigpt/flexigpt-app --skill designing-system-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: designing-system-architecture
Source: https://github.com/flexigpt/flexigpt-app/tree/main/internal/builtin/skills/software-dev/designing-system-architecture
Command: npx skills add https://github.com/flexigpt/flexigpt-app --skill designing-system-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help teams choose and justify a system architecture by comparing simple to complex patterns, mapping boundaries, and defining ownership to produce ADR-ready decisions.

Core Features & Use Cases

  • Compare architecture options (e.g., monolith, modular monolith, microservices) and evaluate their trade-offs.
  • Clarify bounded contexts, ownership, and integration contracts, with guidance on when to apply CQRS, event sourcing, sagas, or async messaging.
  • Produce ADR-ready recommendations that document decisions, rationale, and next steps for stakeholders.

Quick Start

Provide an ADR-ready architecture recommendation for your current project scope.

Frequently Asked Questions about designing-system-architecture

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

FAQPage Schema
Can I get an ADR-ready recommendation for a simple project scope?▼

Yes, you can obtain an ADR-ready architecture recommendation for simple project scopes by evaluating minimal structural patterns and producing clear boundaries, trade-offs, and next steps.

How do I decide between a modular monolith and microservices for my system architecture?▼

System architecture decisions between modular monoliths and microservices are evaluated by comparing structural trade-offs, mapping bounded contexts, and defining ownership to produce clear, ADR-ready recommendations.

When do I need event sourcing or CQRS in my architecture?▼

Event sourcing or CQRS is needed when evaluating event-driven patterns across bounded contexts to determine if complex ownership boundaries and integration contracts warrant these specific architectural decisions.

How do I document system architecture decisions for stakeholders?▼

Document system architecture decisions by producing ADR-ready recommendations that capture the selected patterns, rationale, trade-offs, and next steps for stakeholders to review and implement.

What is the best way to define bounded contexts and ownership boundaries?▼

The best way to define bounded contexts and ownership boundaries is by applying event-driven pattern analysis to clarify integration contracts and determine structural ownership within your system architecture.

Should I use sagas and async messaging for my system architecture?▼

Sagas and async messaging are recommended when your architecture decisions require coordinating complex event-driven processes across multiple bounded contexts, providing ADR-ready options with documented trade-offs and next steps.

Related Skills

Explore More Software Engineering Skills→
shafibabarshafibabar
1

bounded-context-mapping

Identify and document Bounded Contexts using Linguistic Fracture Line analysis.

Community
Advanced
ondrej-svecondrej-svec
18

architect

Convert brainstorm outcomes into user stories, architecture docs, and ADRs.

Community
Advanced
vecearvecear

domain-model-boundaries-mapper

Map bounded contexts, relationships, and dependencies using Domain-Driven Design.

Community
Advanced
SatoryKonoSatoryKono
1

architecture-guardian

Identify architectural boundary violations in BioETL code and generate a compliance report.

Community
Advanced