software-architect

Provides software architecture and system design guidance including domain-driven design and Architectural Decision Records.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Likas07/t3code-skills --skill software-architect-likas07
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-architect
Source: https://github.com/Likas07/t3code-skills/tree/main/skills/software-architect
Command: npx skills add https://github.com/Likas07/t3code-skills --skill software-architect-likas07

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design robust, scalable, and maintainable software architectures by providing expertise in system design, domain-driven design, and architectural patterns.

Core Features & Use Cases

  • System Design: Guides the creation of new software architectures or the evolution of existing ones.
  • Domain Modeling: Assists in identifying bounded contexts and defining domain events.
  • Architectural Patterns: Recommends appropriate patterns (microservices, modular monolith, event-driven) based on project needs.
  • Decision Making: Facilitates technical decision-making through structured trade-off analysis and ADRs.
  • Use Case: You need to design a new e-commerce platform. This Skill can help you define the core domains, choose between microservices or a modular monolith, and document your architectural decisions.

Quick Start

Use the software-architect skill to design a scalable microservices architecture for an e-commerce platform.

Frequently Asked Questions about software-architect

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

FAQPage Schema
How do I design a scalable microservices architecture for an e-commerce platform?

To design a scalable microservices architecture, you must define core domains, identify bounded contexts, and select appropriate architectural patterns to ensure system maintainability and scalability.

What is the best way to choose between a modular monolith and microservices?

Choosing between a modular monolith and microservices requires a structured trade-off analysis based on your specific project needs, domain-driven design principles, and desired scalability.

How do I identify bounded contexts when modeling a new software system?

Identifying bounded contexts involves analyzing your domain to define core domains and domain events, ensuring clear boundaries for maintainable system design and domain-driven modeling.

How do I document technical decisions for a new software architecture?

You document technical decisions by creating Architectural Decision Records (ADRs), which facilitate structured trade-off analysis and capture the rationale behind your architectural patterns.

When do I need domain-driven design for my software system?

You need domain-driven design when creating new software architectures or evolving existing ones, specifically to assist in identifying bounded contexts, defining domain events, and ensuring maintainability.

What architectural patterns work best for event-driven systems?

Event-driven systems benefit from architectural patterns recommended through structured trade-off analysis, ensuring the chosen pattern aligns with your domain events and scalability requirements.