mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-12 02:37:45 +08:00
f14418603a
重构 ccw cli 模板系统： - 新增 template-discovery.ts 模块，支持扁平化模板自动发现 - 添加 --rule <template> 选项，自动加载 protocol 和 template - 模板目录从嵌套结构 (prompts/category/file.txt) 迁移到扁平结构 (prompts/category-function.txt) - 更新所有 agent/command 文件，使用 $PROTO $TMPL 环境变量替代 $(cat ...) 模式 - 支持模糊匹配：--rule 02-review-architecture 可匹配 analysis-review-architecture.txt 其他更新： - Dashboard: 添加 Claude Manager 和 Issue Manager 页面 - Codex-lens: 增强 chain_search 和 clustering 模块 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
41 lines
1.4 KiB
Plaintext
41 lines
1.4 KiB
Plaintext
Generate comprehensive architecture documentation for the entire project.
|
|
|
|
## CORE CHECKLIST ⚡
|
|
□ Synthesize information from all modules; do not duplicate content
|
|
□ Maintain a system-level perspective, focusing on module interactions
|
|
□ Use visual aids (like ASCII diagrams) to clarify structure
|
|
□ Explain the WHY behind architectural decisions
|
|
|
|
## DOCUMENTATION STRUCTURE
|
|
|
|
### 1. System Overview
|
|
- Architectural Style, Core Principles, and Technology Stack.
|
|
|
|
### 2. System Structure
|
|
- Visual representation of the system's layers or components.
|
|
|
|
### 3. Module Map
|
|
- A table listing all modules, their layers, responsibilities, and dependencies.
|
|
|
|
### 4. Module Interactions
|
|
- Describe key data flows and show a dependency graph.
|
|
|
|
### 5. Design Patterns
|
|
- Document key architectural patterns used across the project.
|
|
|
|
### 6. Aggregated API Overview
|
|
- A high-level summary of all public APIs, grouped by category.
|
|
|
|
### 7. Data Flow
|
|
- Describe the typical request lifecycle or event flow.
|
|
|
|
### 8. Security and Scalability
|
|
- Overview of security measures and scalability considerations.
|
|
|
|
## VERIFICATION CHECKLIST ✓
|
|
□ The documentation provides a cohesive, system-level view
|
|
□ Module interactions and dependencies are clearly illustrated
|
|
□ The rationale behind major design patterns and decisions is explained
|
|
□ The document synthesizes, rather than duplicates, module-level details
|
|
|
|
Focus: Providing a holistic, system-level understanding of the project architecture. |