From project-docs
Update ARCHITECTURE.md to document system design and patterns
How this command is triggered — by the user, by Claude, or both
Slash command
/project-docs:architectureThe summary Claude sees in its command listing — used to decide when to auto-load this command
Invoke the `architecture` skill to update the project ARCHITECTURE.md. Review the current codebase and ARCHITECTURE.md (if it exists), then update it to document how the system is designed and why: - System flow diagrams - Data model (entities, attributes, indexes) - API endpoint specs - Workflow details (Step Functions, etc.) - Infrastructure resources - Patterns & Conventions to follow when adding new code This is the "how it's designed and why" document, not the "how to use it" document (that's README.md). Use best judgment to determine whether to do an incremental update or complete ...
Invoke the architecture skill to update the project ARCHITECTURE.md.
Review the current codebase and ARCHITECTURE.md (if it exists), then update it to document how the system is designed and why:
This is the "how it's designed and why" document, not the "how to use it" document (that's README.md).
Use best judgment to determine whether to do an incremental update or complete rewrite based on the scope of changes since last update.
npx claudepluginhub ttorres33/teresa-torres-plugins --plugin project-docs/architectureGenerates Mermaid diagrams of your codebase: system overview, API route map, database ER diagram, and data flow sequences. Renders in GitHub.