architecture
WHAT: Define technical solution structure, interfaces, and system boundaries. USE FOR: architecture briefs, API contracts, component topology, integrations, migrations, and material technical proposals. DO NOT USE FOR: product/domain semantics, delivery sequencing, implementation, runtime diagnosis, QA execution, or final acceptance.
- License
- MIT
Pinned to revision 0bef895aff6a, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/architecture/SKILL.md
- skills/architecture/references/api-design/api-design-patterns.md
- skills/architecture/references/architectural-immune-system/lenses-and-report.md
- skills/architecture/references/architecture-design/method-source.md
- skills/architecture/references/architecture-design/references/ADR-FORMAT.md
- skills/architecture/references/architecture-design/references/composition.md
- skills/architecture/references/architecture-design/references/guide.md
- skills/architecture/references/architecture-design/references/original-spec.md
- skills/architecture/references/domain-modeling/method-source.md
- skills/architecture/references/domain-modeling/references/ADR-FORMAT.md
- skills/architecture/references/domain-modeling/references/CONTEXT-FORMAT.md
- skills/architecture/references/domain-modeling/references/original-spec.md
- skills/architecture/workflows/api-design.md
- skills/architecture/workflows/architectural-immune-system.md
- skills/architecture/workflows/architecture-design.md
Every link opens the file at its source, pinned to the revision this page describes.