architecture
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
Author
Category
Business AnalysisInstall
Download and extract to your skills directory
Copy command and send to OpenClaw for auto-install:
Architecture - Architectural Decision Framework
Skill Overview
Architecture is an AI framework focused on system architecture decisions, helping developers with requirements analysis, trade-off evaluation, and ADR document authoring, so they can make informed technical decisions in architecture and system design scenarios.
Applicable Scenarios
1. New Project Architecture Design
When starting a new project, this skill helps teams perform requirements analysis, classify the project (MVP, SaaS, or Enterprise), and—based on the core principle "start simple"—recommend appropriate architecture patterns to avoid over-engineering.
2. Documenting Architecture Decisions
When important architecture decisions need to be recorded, it provides standardized ADR (Architecture Decision Record) templates and a trade-off evaluation framework to ensure the rationale behind decisions is clearly documented for later review and audit.
3. System Architecture Evaluation and Improvement
When analyzing existing systems, it helps identify anti-patterns in the architecture, assess whether new architectural patterns are needed, and how to evolve the architecture incrementally rather than via a big-bang refactor.
Core Features
1. Context Discovery and Project Classification
Quickly understand project requirements through structured questions, classify the project as MVP, SaaS, or Enterprise, and recommend appropriate architecture complexity and pattern choices accordingly.
2. Trade-off Analysis and ADR Documentation
Provide architecture decision record templates and guide how to evaluate the pros and cons (trade-offs) of each decision, ensuring the team's expertise aligns with the chosen patterns and that decision rationales are permanently recorded.
3. Pattern Selection and References
Include decision trees for common architecture patterns and anti-pattern detection, as well as reference implementation examples for different project types (MVP, SaaS, Enterprise) to help avoid common pitfalls.
Frequently Asked Questions
What is an Architecture Decision Record (ADR)? Why use it?
An ADR (Architecture Decision Record) is a lightweight document format used to record important architecture decisions and their rationale. It helps teams understand "why we chose this" as the project evolves, avoids rehashing already-resolved issues, and makes it easier for new members to quickly understand the historical context of architecture decisions.
How do you decide which architecture pattern a project should use?
The Architecture skill recommends starting from the principle of "simplicity first": satisfy current needs first and do not introduce complex patterns for hypothetical future requirements. Use project classification (MVP starts minimal, SaaS considers scalability, Enterprise emphasizes governance) and the trade-off analysis framework to incrementally add complexity rather than applying a full-blown architecture from day one.
How is the "Simplicity First" architecture principle applied in practice?
The core principle is: you can always add complexity, but removing complexity later is much harder. Practical approaches include: start MVP projects as a monolith; only introduce distributed architecture when it’s proven necessary; prefer patterns familiar to the team over trendy technologies; and record a clear trade-off analysis for every architecture decision.