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 |

Use when planning system architecture to ensure nothing is missed. Provides structured questions covering scalability, security, data, and operational dimensions before implementation. Source: yonatangross/orchestkit.

View raw