software-architecture

Guide software teams in designing scalable, maintainable architectures.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/simplerick0/com.ackhax.configs --skill software-architecture-simplerick0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-architecture
Source: https://github.com/simplerick0/com.ackhax.configs/tree/main/skills/software-architecture
Command: npx skills add https://github.com/simplerick0/com.ackhax.configs --skill software-architecture-simplerick0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design scalable, maintainable software architectures and make informed architectural decisions early in a project.

Core Features & Use Cases

  • Architectural patterns and decisions: choose between Monolith, Microservices, Event-Driven, Layered architectures with trade-offs.
  • System and API design guidance: define APIs, data flows, and contracts.
  • Documentation and governance: record ADRs, architecture diagrams, and decisions for future reference.
  • Use Case: When starting a new product, use this Skill to outline a high-level architecture, select an appropriate pattern, and draft an API contract.

Quick Start

Provide a high-level system design outline for a new service, including major components, data flows, and external interfaces.

Frequently Asked Questions about software-architecture

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

FAQPage Schema
How do I design a scalable software architecture for a new service?

System design for scalable architectures involves outlining major components, data flows, and external interfaces. You can select appropriate architectural patterns like Microservices or Event-Driven, and define API contracts alongside data modeling best practices.

What's the best way to choose between Monolith and Microservices architectures?

Choosing between Monolith and Microservices architectures requires evaluating trade-offs in scalability and maintainability. You can compare Monolith, Microservices, Event-Driven, and Layered patterns against project requirements to make informed architectural decisions.

How do I document architecture decisions and API contracts for future reference?

To document architecture decisions, generate Architecture Decision Records (ADRs) and architecture diagrams. This ensures API guidelines and data modeling choices are recorded for governance and future reference by software teams.

Can I use this for early-stage system design and data modeling?

Yes, you can use this for early-stage system design and data modeling. It is applicable across new products and ongoing architecture decisions, guiding teams to define data flows, API contracts, and execute scalability planning.

Does this help with defining API guidelines and data flows?

Yes, this helps with defining API guidelines and data flows by providing system and API design guidance. It assists in defining APIs, data flows, and contracts to ensure maintainable software architectures.