skills.rest
AreteDriver
AreteDriverCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

software-architect

Define system boundaries, component interfaces, and data flows for software architectures.

4|1|Updated Jan 27, 2026
Search Tags:#architecture#security#scalability#interfaces#system-design#data-flow
One-click install
npx skills add https://github.com/AreteDriver/ai_skills --skill software-architect-aretedriver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: software-architect
Source: https://github.com/AreteDriver/ai_skills/tree/main/skills/software-architect
Command: npx skills add https://github.com/AreteDriver/ai_skills --skill software-architect-aretedriver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams design scalable, secure software architectures by defining component boundaries, interfaces, and technology choices, reducing guesswork and rework.

Core Features & Use Cases

  • Structured design guidance: define system boundaries, interfaces, and data flows for complex applications.
  • Trade-off analysis: present multiple architectural options with clear pros and cons.
  • Non-functional considerations: address scalability, reliability, security, observability, and deployment concerns.
  • Use Case: design a new order service or refactor a monolith into modular services with clear integration points.

Quick Start

Request an initial architecture sketch for a microservices-based order management system, outlining system boundaries, major components, and data flows.

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 software architecture for a new service?▼

Software architecture design for monolith refactoring involves defining modular service boundaries, component interfaces, and data flows. This process establishes clear integration points and addresses non-functional considerations like scalability and reliability during major refactors.

What's the best way to evaluate architectural trade-offs when building microservices?▼

Evaluating architectural trade-offs requires presenting multiple design options with clear pros and cons. This structured analysis ensures non-functional considerations such as security, scalability, and deployment concerns are addressed before finalizing system boundaries.

Does this system design approach work for migrating from a monolith to modular services?▼

Yes, this system design approach works for monolith migrations by defining modular service boundaries and clear integration points. It provides structured baseline designs that satisfy requirements for component interfaces and data flows during major refactors.

How do I define system boundaries and data flows for complex applications?▼

Define system boundaries and data flows by creating a structured baseline design that maps major components and their interactions. This architectural sketch outlines integration points and addresses non-functional requirements like observability and security.

Related Skills

Explore More Software Engineering Skills→
saolalabsaolalab
37

requirements-analysis

Gather and validate stakeholder requirements into a traceability matrix and BRD.

Official
Advanced
matteocervellimatteocervelli
25

design

Design software architecture, API contracts, and data flows for Python projects.

Community
Intermediate
yonatangrossyonatangross
217

testing-integration

Validate API boundaries and cross-service contracts with Pact, Supertest, httpx, and Hypothesis.

Community
Advanced
camelranchentertainmentcamelranchentertainment
1

legacy-modernizer

Plan incremental migration strategies for aging codebases with dependency maps and roadmaps.

Community
Advanced