architecture

Name: architecture
Availability: InStock
Author: ttorres33

Update ARCHITECTURE.md after infrastructure, data model, or API changes.

4|Updated Dec 12, 2025

Search Tags:#architecture #documentation #infrastructure #system-design #architecture-docs #data-models

Ready to run

npx skills add https://github.com/ttorres33/project-docs --skill architecture-ttorres33

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/ttorres33/project-docs/tree/main/skills/architecture
Command: npx skills add https://github.com/ttorres33/project-docs --skill architecture-ttorres33

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps ARCHITECTURE.md in sync with how the system is designed, why, and the patterns to follow when adding code.

Core Features & Use Cases

Document changes to infrastructure, data models, API endpoints, and workflows.
Provide a clear rationale and patterns to follow to ensure consistency across the project.
Reference decisions from process-notes to capture trade-offs and history.

Quick Start

Update ARCHITECTURE.md to reflect current system design after infrastructure changes, data-model updates, or new patterns.

Frequently Asked Questions about architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep architecture documentation up to date with system design changes?▼

Architecture documentation stays current by applying a structured update workflow whenever infrastructure changes, data model evolution, or new patterns are established, ensuring ARCHITECTURE.md reflects the latest system design.

What should be documented in ARCHITECTURE.md when infrastructure changes?▼

When infrastructure changes occur, ARCHITECTURE.md should document the updates, provide clear rationale and patterns to follow, and capture trade-offs and decisions to ensure consistency across the project for future developers.

When do I need to update architecture docs for API and data model evolution?▼

Architecture docs need updating after API changes, data model evolution, or when new patterns are established, triggering a structured workflow to keep ARCHITECTURE.md synchronized with the evolving system design and architectural decisions.

What is the best way to document system design rationale and trade-offs?▼

The best way to document system design rationale is to reference decisions from process-notes, capturing trade-offs and history within ARCHITECTURE.md to provide clear reasoning and patterns for future developers adding code.

Does this architecture documentation workflow work without external dependencies?▼

Yes, this architecture documentation workflow operates with no external dependencies, functioning independently to keep ARCHITECTURE.md in sync with evolving system design and architectural decisions.

Can I use this to maintain architecture docs for new infrastructure patterns?▼

Yes, you can use this to maintain architecture docs when new patterns are established, applying a structured update workflow to document rationale, trade-offs, and decisions for future developers working with the infrastructure.