architecture
Use when designing or changing how a system is structured (service or module boundaries, data stores, events and messaging, durable workflows, caching, consistency, API or schema evolution, failure and overload handling, LLM integration), when writing an architecture decision record or design document, or when reviewing a design. Not for routine coding, bug fixes or refactors inside one module.
Pinned to revision 754e1c52b1cb, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/architecture/SKILL.md
- skills/architecture/references/api-versioning.md
- skills/architecture/references/boundaries.md
- skills/architecture/references/caching.md
- skills/architecture/references/consistency.md
- skills/architecture/references/data-and-events.md
- skills/architecture/references/decisions-and-documentation.md
- skills/architecture/references/domain-design.md
- skills/architecture/references/durable-workflows.md
- skills/architecture/references/failure.md
- skills/architecture/references/llm-systems.md
- skills/architecture/references/observability.md
- skills/architecture/references/operations.md
- skills/architecture/references/overload.md
- skills/architecture/references/queueing-and-capacity.md
- skills/architecture/references/schema-evolution.md
- skills/architecture/references/security.md
- skills/architecture/references/start-simple.md
- skills/architecture/references/testing.md
Every link opens the file at its source, pinned to the revision this page describes.