architecture-doc
快速产出高层架构说明，适合缺少文档惯性的工程团队。
自动生成面向仓库的系统级 ARCHITECTURE.md 文档与决策说明。
生成面向仓库的 ARCHITECTURE.md，给出系统的高阶视角：主要模块、服务间通信、部署与基础设施决策。适用于需要记录整体架构、扩展策略或跨切关注点（如鉴权、日志、监控）时使用。优点是把架构模式、选型理由和部署考量写清，便于审阅和新人成长。
▸ 展开 SKILL.md 英文原文
Generate a complete ARCHITECTURE.md file for any software system. Use whenever the user asks to create, write, generate, or draft an ARCHITECTURE.md — a system-wide architecture document that explains the big picture: how major components fit together, what patterns are used, infrastructure decisions, and cross-cutting concerns. This skill triggers when users need to document: overall system architecture, infrastructure setup, deployment architecture, architectural patterns (microservices, event-driven, layered), technology stack decisions, scalability strategy, or cross-cutting concerns (auth, logging, monitoring across the system). Do NOT trigger for single-feature technical designs (use Design.md skill), UI/visual design, or code-level implementation details.
帮我安装这个 skill：https://raw.githubusercontent.com/arsudsandesh97/Revoact/main/skills/architecture-doc/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/arsudsandesh97/Revoact/main/skills/architecture-doc/SKILL.md"# ARCHITECTURE.md Author Skill You are a system architect documenting the high-level structure and decisions of a software system. ## Philosophy An ARCHITECTURE.md is the **30,000-foot view** of your system. It answers: - **What are the major building blocks?** (services, databases, external systems) - **How do they communicate?** (APIs, message queues, events) - **What patterns guide the design?** (microservices, CQRS, event sourcing) - **Why these architectural choices?** (scalability, team structure, constraints) - **What are the cross-cutting concerns?** (auth, logging, monitoring, deployment) The audience is **technical stakeholders** who need to understand the system's structure be