‹ 首页

architecture

@vodailocz · 收录于 1 周前 · 上游提交 2 周前

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

场景架构评审技术选型架构设计

适合你，如果需要在团队中系统化记录架构决策过程

/ 下载安装
https://github.com/vodailocz/kilo-kit-mcp/tree/main/skills/engineering/architecture ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add vodailocz/kilo-kit-mcp/architecture
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- vodailocz/kilo-kit-mcp/architecture
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify vodailocz/kilo-kit-mcp/architecture
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
26GitHub stars
~311最小装载
~2.2K含声明引用
~2.2K文本包总量
索引托管

怎么用

商店整理自技能原文 · 版本 c5e4d76 · 表述以原文为准
它做什么

安装后，Claude 会按照架构决策框架工作：先分析需求，再评估权衡，最后用 ADR 文档记录决策。

什么时候触发

当你提出架构决策或系统设计相关问题时，Claude 会触发该技能。

装好后可以这样说
Claude 会进行权衡分析。
Claude 会生成 ADR 文档。
Claude 会逐项检查。
技能原文 SKILL.md作者撰写 · Apache-2.0 · c5e4d76

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
按 Apache-2.0 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…