system-design-interrogation

SKILL.md

Rushing to implementation without systematic design thinking leads to:

| Scale | How many? | "All users" | | Data | Where stored? | "I'll figure it out" | | Security | Who can access? | "Everyone" | | UX | What's the latency? | "It'll be fast" | | Coherence | What types change? | "No changes needed" |

| Dimensions count | Five (Scale, Data, Security, UX, Coherence) | Covers all critical architectural concerns without overlap | | Process timing | Before any code | Prevents costly rework from missed requirements | | Question format | Structured templates | Ensures consistent coverage, prevents omissions |

누락된 부분이 없도록 시스템 아키텍처를 계획할 때 사용합니다. 구현 전 확장성, 보안, 데이터, 운영 차원을 포괄하는 구조화된 질문을 제공합니다. 출처: yonatangross/orchestkit.

원본 보기