先看看示例
作者提供的示例，实际效果取决于你的输入和使用工具。
输入
为一个 5 人团队的中型 SaaS 项目评估是否采用微服务，并写出对应 ADR。
输出
预期交付：架构选型建议、权衡分析表、ADR 决策记录文档。（编辑说明，非实际运行结果）
方法说明
--- name: architecture description: "Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design." risk: safe source: community date_added: "2026-02-27" --- # Architecture Decision Framework > "Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale." ## 🎯 Selective Reading Rule **Read ONLY files relevant to the request!** Check the content map, find what you need. | File | Description | When to Read | |------|-------------|--------------| | `context-discovery.md` | Questions to ask, project classification | Starting architecture design | | `trade-off-analysis.md` | ADR templates, trade-off framework | Documenting decisions | | `pattern-selection.md` | Decision trees, anti-patterns | Choosing patterns | | `examples.md` | MVP, SaaS, Enterprise examples | Reference implementations | | `patterns-reference.md` | Quick lookup for patterns | Pattern comparison | --- ## 🔗 Related Skills | Skill | Use For | |-------|---------| | `@[skills/database-design]` | Database schema design | | `@[skills/api-patterns]` | API design patterns | | `@[skills/deployment-procedures]` | Deployment architecture | --- ## Core Principle **"Simplicity is the ultimate sophistication."** - Start simple - Add complexity ONLY when proven necessary - You can always add patterns later - Removing complexity is MUCH harder than adding it --- ## Validation Checklist Before finalizing architecture: - [ ] Requirements clearly understood - [ ] Constraints identified - [ ] Each decision has trade-off analysis - [ ] Simpler alternatives considered - [ ] ADRs written for significant decisions - [ ] Team expertise matches chosen patterns ## When to Use This skill is applicable to execute the workflow or actions described in the overview. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.