skills.rest
kamelmh
kamelmhCOMMUNITY
Explore all skills by this author →
GitHub

architecture-designer

Design high-level software architecture and document decisions in ADRs.

Updated Aug 23, 2026
Search Tags:#architecture#scalability#system design#microservices#adr#trade-offs
One-click install
npx skills add https://github.com/kamelmh/opencode-config --skill architecture-designer-kamelmh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/kamelmh/opencode-config/tree/main/skills/architecture-designer
Command: npx skills add https://github.com/kamelmh/opencode-config --skill architecture-designer-kamelmh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you make clear, defensible architecture decisions when a system needs to grow, change, or be reviewed. It turns vague product and engineering needs into structured designs with explicit trade-offs, risks, and implementation guidance.

Core Features & Use Cases

  • High-level system design: Shape scalable architectures for new products or major redesigns.
  • Architecture review and trade-off analysis: Compare monolith, modular monolith, microservices, serverless, and event-driven approaches.
  • Decision documentation: Produce Architecture Decision Records and rationale for technology choices, data stores, and component boundaries.
  • Use case: A team planning a new API platform can use this Skill to map requirements, select the right architecture pattern, document key decisions, and identify operational risks before implementation.

Quick Start

Ask the architecture-designer skill to review my requirements and propose a scalable architecture with key decisions, trade-offs, and an ADR-ready summary.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema
How do I design scalable system architecture for a new platform?▼

Scalable system architecture is designed by mapping explicit functional and non-functional requirements to high-level structures, enabling you to compare patterns like microservices or serverless and identify operational risks before implementation.

What is the best way to document architectural decisions and trade-offs?▼

Architectural decisions are documented using Architecture Decision Records (ADRs) to capture the rationale, technology selections, and trade-off analysis, ensuring defensible choices for data stores and component boundaries.

How do I compare microservices and monolith architectures for my system?▼

Comparing microservices and monoliths requires a structured trade-off analysis of scalability needs and component boundaries, evaluating modular monolith, serverless, and event-driven approaches against your specific non-functional requirements.

When do I need an architecture review for my software design?▼

An architecture review is needed when your system must grow, change, or undergo a major redesign, requiring explicit failure-mode planning and stakeholder review to turn vague engineering needs into structured designs.

Can I use this approach for technology selection and data store choices?▼

Yes, technology selection and data store choices are supported by applying explicit requirements gathering and trade-off analysis, producing rationale that justifies component boundaries and technology implementations.

Why does system design require non-functional requirement coverage?▼

System design requires non-functional requirement coverage to ensure scalability planning and failure-mode anticipation, allowing you to map vague product needs into defensible architecture with explicit operational risks.

Related Skills

Explore More Software Engineering Skills→
saolalabsaolalab
37

requirements-analysis

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

Official
Advanced
leynosleynos
2

logisphere-design-review

Conduct structured design reviews with a six-expert panel for RFCs and ADRs.

Community
Advanced
vndeevndee
3

system-design

Outlines system boundaries, data flows, API contracts, and risk assessments for software architecture projects.

Community
Advanced
Joncik91Joncik91
29

architect

Creates architectural decision records and evaluates system design options.

Community
Advanced