software-design-lifecycle-tech-detailed-technical-arch-diagrammi

# Technical Detailed Technical Architecture Diagramming ## Overview This skill now directly contains the merged specialist doctrine that previously lived in the legacy technical-architecture skill. ## Integrated Legacy Specialist Doctrine (Preserved and Merged) # Technical Architecture Diagramming ## Overview This is the architect-private skill for drawing and reviewing **技术架构图** in the **详细设计** stage. It is deliberately built as a **two-layer skill**: 1. **Full-fidelity drawing grammar is preserved intact** in the reference file: - `references/universal-arch-lifecycle-tech-detailed-technical-arch-diagramming-spec-full.md` 2. **Architect-specific lifecycle method and review gates** are added in this umbrella skill: - where 技术架构图 sits in the architecture lifecycle - what detailed-design questions it must answer - how to separate it from neighboring artifacts - how to convert solution intent into concrete technical realization - how to review stability, operability, security, and runtime collaboration before implementation Core principle: **技术架构图 is not a prettier system diagram. It is the detailed-design artifact that explains how the approved solution is concretely realized through technology stack, runtime units, middleware, storage, project structure, execution paths, and reliability controls.** This skill exists because many so-called “技术架构图” fail in one of five ways: - they are only **system architecture diagrams** with product names sprinkled ...