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
- Describe the system shape: components, data flows, boundaries.
- Record decisions as ADRs with context and alternatives.
- Keep diagrams source-controlled and easy to update.
- Note failure modes and operational model.
- Mark docs as living; tie to current code.
- Add ownership and review cadence.