sdlc-architecture-design

Define software architectures with patterns, ADRs, and dependency rules.

Updated Jun 5, 2026

Search Tags:#architecture #microservices #adr #ddd #clean-architecture #system-design

Ready to run

npx skills add https://github.com/dinoudon/sdlc-skills --skill sdlc-architecture-design

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdlc-architecture-design
Source: https://github.com/dinoudon/sdlc-skills/tree/main/full/sdlc-architecture-design
Command: npx skills add https://github.com/dinoudon/sdlc-skills --skill sdlc-architecture-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define robust software architectures.

Core Features & Use Cases

Design system architectures using established patterns (C4, DDD, clean/hexagonal), ADRs, and dependency rules.
Produce architecture decision records, container diagrams, and code structure guidance for monoliths and microservices.
Use ADRs to capture rationale and ensure governance across teams.

Quick Start

Provide a complete system design for a new microservice, including patterns, ADRs, data model, and deployment considerations.

Frequently Asked Questions about sdlc-architecture-design

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

FAQPage Schema

How do I design a microservice architecture using clean architecture and DDD patterns?▼

Design microservice architecture by applying clean architecture, DDD, and hexagonal patterns to define bounded contexts, enforce dependency rules, and generate container diagrams alongside architecture decision records for governance.

When do I need to write architecture decision records for my system design?▼

Write architecture decision records when you need to capture the rationale behind architectural choices, enforce governance across teams, and ensure system design consistency across monoliths and microservices.

What is the best way to structure a database schema for a hexagonal architecture codebase?▼

Structure database schemas for hexagonal architecture by enforcing dependency rules that isolate domain logic from infrastructure, ensuring API design and data models remain decoupled from core business rules.

Can I use this system design approach for both monoliths and microservices?▼

Yes, this system design approach applies to both monoliths and microservices, enforcing architectural patterns, dependency rules, and ADRs across the entire codebase regardless of deployment topology.

How do I conduct an architecture review for an existing codebase?▼

Conduct an architecture review by evaluating the codebase against established patterns like clean architecture and DDD, checking dependency rules, and generating ADRs to document compliance and structural improvements.

Why should I use C4 container diagrams in my architecture design process?▼

Use C4 container diagrams in architecture design to visualize system components, map dependencies, and communicate structural boundaries, ensuring teams understand the system design before implementing code structure guidance.