update-architecture
Refresh architecture maps after structural changes.
When & Why to Use This Skill
This Claude skill automates the synchronization between source code and system architecture documentation. It ensures that architecture maps, component profiles, and interaction flows are updated immediately after structural changes, eliminating documentation rot and maintaining a single source of truth for complex system designs.
Use Cases
- Post-Refactoring Documentation: Automatically refresh architecture maps and interaction flows after significant code structural changes to ensure documentation reflects the current state of the codebase.
- Interface & Boundary Updates: Update component profiles and system boundaries when service interfaces or internal dependencies are modified to prevent integration errors.
- Automated Architecture Indexing: Maintain up-to-date ARCHITECTURE.md and agent-specific documentation indexes to facilitate better developer onboarding and AI agent context management.
- Change Logging & ADRs: Record architectural shifts in Architecture Decision Records (ADRs) and action logs to maintain a clear historical record of design evolution and rationale.
| name | update_architecture |
|---|---|
| description | Refresh architecture maps after structural changes. |
Purpose
Keep architecture indexes and maps aligned with code changes.
Steps
- Identify affected entrypoints, components, and flows.
- Update
.agent-docs/architecture/overview.mdbaseline truth. - Refresh interaction and flow maps for impacted areas.
- Update component profiles if interfaces or boundaries changed.
- Refresh
ARCHITECTURE.mdand.agent-docs/architecture.mdindexes. - Record gaps and confidence levels.
- Log notable changes in ADRs and Action Log.
Guardrails
- Keep
ARCHITECTURE.mdindex-only. - Use the architecture mapping checklist for completeness.