Common System Design

Define module boundaries, dependency direction, data ownership, resilience, and distributed-system trade-offs. Use for architecture, service boundaries, coupling, scalability, or failure-cascade decisions; not generic project setup.

tuyv Updated 1 repo stars

File contents

tuyv/ccpm commit a4b3f0df9c

Frequently asked questions

npx get-skill add tuyv/common-system-design