software-design-lifecycle-tech-overview-system-arch-diagramming

# Technical Overview System Architecture Diagramming ## Overview This skill now directly contains the merged specialist doctrine that previously lived in the legacy system-architecture skill. ## Integrated Legacy Specialist Doctrine (Preserved and Merged) # System Architecture Diagramming ## Overview This is the architect-private skill for drawing and reviewing **系统架构图** in the **概要设计** stage. This skill intentionally preserves the **full drawing-detail layer** from the system-architecture-diagram spec instead of compressing it away. It is meant to strengthen architect execution, not merely restate high-level principles. Its role in the architecture lifecycle is anchored in the local source note `软件架构设计生命周期`: - **功能架构图** 负责把设计层、运行层、数据底座与运营支撑拆开。 - **系统架构图** 负责交代内部子系统、外部依赖、通信关系与边界条件。 - **技术架构图** 负责把系统进一步压到具体技术栈、引擎、中间件、数据存储与执行路径。 Core principle: **系统架构图 belongs to overview design, so it should explain subsystem structure, dependency boundaries, and collaboration relationships — not merely list functions, not collapse into流程时序, and not yet dive into full technical-stack implementation detail.** This skill exists because many so-called “系统架构图” fail in one of four ways: - they are really **功能清单/功能分层图**, so they say what the system should do but not what subsystems exist or how boundaries are controlled - they are really **流程图/时序图**, so they show time order instead of stable structure - they are really **技术架构图**, so they jump too early into concrete middleware, engine, hos...