skills.rest
knopki
knopkiCOMMUNITY
Explore all skills by this author →
𝕏@knopkiGitHub

architecture-design

Guide system architecture design with context, requirements, constraints, and alternatives.

1|Updated Jun 18, 2025
Search Tags:#architecture#scalability#system design#maintainability#ADR#technical decisions#software patterns
One-click install
npx skills add https://github.com/knopki/dotfiles --skill architecture-design-knopki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-design
Source: https://github.com/knopki/dotfiles/tree/main/home/private_dot_config/opencode/skills/architecture-design
Command: npx skills add https://github.com/knopki/dotfiles --skill architecture-design-knopki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to designing system architecture, making high-level technical decisions, and planning major system changes, ensuring a focus on long-term strategy and maintainability.

Core Features & Use Cases

  • System Design: Guides users through understanding context, gathering requirements, identifying constraints, and considering alternatives.
  • Decision Documentation: Facilitates the creation of Architecture Decision Records (ADRs) to document key choices.
  • Pattern Application: Explains common architecture patterns like Layered, Hexagonal, and Microservices.
  • Use Case: When starting a new project, use this Skill to define the core components, their interactions, and the technology stack, ensuring a solid foundation.

Quick Start

Use the architecture-design skill to outline the system structure for a new e-commerce platform.

Frequently Asked Questions about architecture-design

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

FAQPage Schema
What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) documents key technical decisions by capturing context, requirements, constraints, and alternatives. You need an ADR when planning major system changes to ensure high-level choices are recorded for long-term strategy and maintainability.

How do I apply software patterns like Hexagonal or Microservices to my system design?▼

Applying software patterns like Hexagonal or Microservices involves structuring your system around core components and their interactions. This approach defines interfaces and component boundaries to achieve specific structural goals and improve overall maintainability.

Can I use this approach to plan major system changes and failure planning?▼

Yes, you can use this structured approach to plan major system changes by defining component structure, interfaces, and failure planning. It guides users through identifying constraints and documenting technical decisions to handle system failures effectively.

What is the best way to document technical decisions for long-term maintainability?▼

The best way to document technical decisions for maintainability is creating Architecture Decision Records (ADRs). ADRs capture the context, alternatives, and constraints of high-level choices, ensuring long-term strategy remains clear during major system changes.

Related Skills

Explore More Software Engineering Skills→
cenjiecenjie

i-shape

Plan UX and UI through a structured discovery interview and design brief synthesis.

Community
Intermediate
abudhahirabudhahir

architecture-documenter

Generate system architecture documentation and Architecture Decision Records.

Community
Advanced
htlin222htlin222
77

architect

Design system architecture, APIs, and component interfaces using established patterns.

Community
Advanced
jagreehaljagreehal
3

system-architecture

Document architecture decisions and trade-offs using ADR patterns.

Community
Basic