architecture-author
Write and maintain architecture docs — the documents that say what each system is, where it runs, what it depends on, and the real names of things (cloud projects, clusters, namespaces, hostnames, buckets). The heart of it is an interview that pins down what each system name actually means before anything is written. Use when asked to write, extend or improve architecture documentation, to document a system, or to fill a gap the architecture skill could not answer.
Pinned to revision 4e8964e24a5a, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/architecture-author/SKILL.md
- skills/architecture-author/LICENSE
- skills/architecture-author/references/concerns.md
- skills/architecture-author/references/examples/README.md
- skills/architecture-author/references/examples/atlas/README.md
- skills/architecture-author/references/examples/atlas/database.md
- skills/architecture-author/references/examples/atlas/deployment.md
- skills/architecture-author/references/examples/atlas/events.md
- skills/architecture-author/references/examples/atlas/observability.md
- skills/architecture-author/references/examples/environments.md
- skills/architecture-author/references/examples/observability/README.md
- skills/architecture-author/references/examples/routing.md
- skills/architecture-author/references/examples/storefront/README.md
- skills/architecture-author/references/format.md
- skills/architecture-author/references/homes.md
- skills/architecture-author/references/write.md
Every link opens the file at its source, pinned to the revision this page describes.