system-design
Choose and evolve application architecture from product outcomes, existing system evidence and operating constraints. Use after product refinement for a new system or before planning a feature that changes service, data, client or integration boundaries; avoid architecture ceremony for small local edits.
Pinned to revision c37715f7cf0d, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/system-design/SKILL.md
- skills/system-design/references/contextual-attributes.md
- skills/system-design/references/cost.md
- skills/system-design/references/journey-to-slo.md
- skills/system-design/references/maintainability.md
- skills/system-design/references/performance.md
- skills/system-design/references/quality-attributes.md
- skills/system-design/references/reliability-disaster-recovery.md
- skills/system-design/references/reliability.md
- skills/system-design/references/security.md
- skills/system-design/references/terraform-monitoring.md
Every link opens the file at its source, pinned to the revision this page describes.