software-architect

Name: software-architect
Availability: InStock
Author: Mike Buyco

Guide software architecture decisions with trade-off analysis and execution plans.

Updated May 30, 2025

Search Tags:#security #system design #data modeling #software architecture #reliability #trade-offs

Ready to run

npx skills add https://github.com/mbuyco/dotfiles --skill software-architect-mbuyco

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: software-architect
Source: https://github.com/mbuyco/dotfiles/tree/main/opencode/skills/software-architect
Command: npx skills add https://github.com/mbuyco/dotfiles --skill software-architect-mbuyco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides pragmatic guidance on software architecture, focusing on making informed decisions about system design, trade-offs, and operational considerations.

Core Features & Use Cases

System Design: Assists in making decisions for system or service architecture.
Pattern Evaluation: Helps evaluate architectural patterns like monolith vs. microservices.
Data Modeling: Aids in designing data models, APIs, events, and schemas.
Reliability & Security: Plans for reliability, scalability, and security posture.
Documentation: Assists in writing lightweight architecture documentation.

Quick Start

Use the software-architect skill to design a scalable and reliable architecture for a new e-commerce platform, considering microservices and event-driven patterns.

Frequently Asked Questions about software-architect

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

FAQPage Schema

How do I evaluate architectural trade-offs for system design?▼

Data modeling for event-driven systems requires designing schemas, APIs, and events while balancing reliability and scalability constraints. The process clarifies operational goals and compares trade-offs to produce secure, simple data structures aligned with your architecture.

What is the best way to choose between monolith and microservices architecture?▼

Choosing between monolith and microservices architecture requires evaluating pattern trade-offs, identifying hard parts of your system, and comparing reliability and security impacts. The decision workflow clarifies your goals to recommend a solution with a concrete execution plan.

How do I write lightweight architecture documentation for a new platform?▼

Writing lightweight architecture documentation involves capturing system constraints, trade-offs, and operational considerations. It focuses on clarifying architectural goals, evaluating patterns, and recording recommended solutions with execution plans based on KISS and YAGNI principles.

Can I plan for scalability and security posture without complex system design?▼

Planning for scalability and security posture is achievable without complex system design by applying pragmatic principles like KISS, YAGNI, and EDUF. The workflow clarifies goals, identifies hard parts, and compares options to produce simple, reliable designs.

When should I not use microservices for software architecture?▼

You should not use microservices when evaluating architectural trade-offs reveals that reliability, security, or operational constraints favor a simpler design. Applying YAGNI principles helps identify if a monolithic approach better suits your current system goals and execution plan.