사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/robsonrung/rar-skills --skill macro-architecture시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Macro Architecture
Two complementary system-level tools that work at the same altitude — what shape should this system take?
- Style selection — given a system/service/feature and its driving requirements, which macro architecture style (or hybrid) fits, and what does the book warn about if you pick it? (from Software Architecture Patterns, 2nd ed., Mark Richards.)
- Hard-parts decomposition — once you're decomposing, merging, or re-shaping a system, which way do the trade-offs actually push, anchored in the current code and runtime? (from Software Architecture: The Hard Parts, Ford & Richards.)
Use Style selection when choosing an overall shape for something new (or sanity-checking an existing one). Use Hard-parts decomposition when the decision is whether to pull a system apart or put it back together. They compose: pick a style, then stress-test the decomposition.
Distinct from architecture-lens (code-level trade-offs/connascence and layer placement/cohesion in the code under your hands), domain-driven-design (bounded-context boundaries, ubiquitous language, cross-context integration patterns), and design-patterns (GoF code patterns). This skill picks the MACRO shape; those review the code and contexts within it.
Select the decision
| Need | Read |
|---|---|
| Choose or assess an overall architecture style | references/style-selection.md |
| Split, merge, or reshape services and data ownership | references/decomposition.md |
| Both | Select the style, then assess only its unresolved decomposition tradeoffs |
Use current code, runtime evidence, and the user's constraints. The smallest coherent shape is the one that meets the actual requirements. Name the benefit, cost, and next concrete move. Do not turn a routine code change into a system redesign.
Authority and output
A decision or review request returns the selected method's recommendation. Implement only when the user's request authorizes implementation. Under design-gate, stay read-only and return verdict: proceed|revise, blocking_findings, advisory_findings, and required_changes.
Use all three or no ADR: hard to reverse, surprising without context, and a real tradeoff. Record on settle using the existing ADR convention when all three apply. The decomposition method contains the fallback path and helper command.
Focused knowledge
Load only the material the selected method needs:
- Style details: layered, microkernel, event-driven, microservices, space-based.
- references/traps.md: before a distributed-style recommendation.
- references/other-styles.md: when the main matrix does not fit, or coarse-grained services may suffice.
- references/catalog.md: decomposition, granularity, ownership, transactions, and workflow tradeoffs.
- references/adrtemplate.md: when writing a durable decision.
