architecture-documentation

Installation
SKILL.md

Architecture Documentation

Use this skill when

  • Recording component boundaries and decisions
  • Onboarding developers to the system shape
  • Keeping docs truthful and current

Do not use this skill when

  • Line-by-line code docs
  • A single doc that must never change

Instructions

  1. Describe the system shape: components, data flows, boundaries.
  2. Record decisions as ADRs with context and alternatives.
  3. Keep diagrams source-controlled and easy to update.
  4. Note failure modes and operational model.
  5. Mark docs as living; tie to current code.
  6. Add ownership and review cadence.
Installs
1
First Seen
Oct 22, 2026