mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-15 02:42:45 +08:00
refactor: 重组CLI模板系统,采用优先级前缀命名
主要变更: - 模板重命名:采用优先级前缀(01-通用, 02-专用, 03-领域特定) - 目录调整:bug-diagnosis从development移至analysis - 引用更新:5个命令文件中21处模板引用更新为新路径 - 路径统一:所有引用统一使用完整路径格式 模板变更详情: - analysis/:8个模板(01-trace-code-execution, 01-diagnose-bug-root-cause等) - development/:5个模板(02-implement-feature, 02-refactor-codebase等) - planning/:5个模板(01-plan-architecture-design, 02-breakdown-task-steps等) - memory/:1个模板(02-document-module-structure) 命令文件更新: - cli/mode/bug-diagnosis.md(6处引用) - cli/mode/code-analysis.md(6处引用) - cli/mode/plan.md(6处引用) - task/execute.md(1处引用) - workflow/tools/test-task-generate.md(2处引用) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,28 @@
|
||||
Guide component implementation and development patterns.
|
||||
|
||||
## CORE CHECKLIST ⚡
|
||||
□ Define component interface and API requirements clearly
|
||||
□ Identify reusable patterns and composition strategies
|
||||
□ Plan state management and data flow before implementation
|
||||
□ Design a comprehensive testing and validation approach
|
||||
|
||||
## REQUIRED ANALYSIS
|
||||
1. Define component interface and API requirements
|
||||
2. Identify reusable patterns and composition strategies
|
||||
3. Plan state management and data flow implementation
|
||||
4. Design component testing and validation approach
|
||||
5. Document integration points and usage examples
|
||||
|
||||
## OUTPUT REQUIREMENTS
|
||||
- Component specification with clear interface definition
|
||||
- Implementation patterns and best practices
|
||||
- State management strategy and data flow design
|
||||
- Testing approach and validation criteria
|
||||
|
||||
## VERIFICATION CHECKLIST ✓
|
||||
□ Component specification includes a clear interface definition
|
||||
□ Reusable implementation patterns and best practices are documented
|
||||
□ State management and data flow design is clear and robust
|
||||
□ A thorough testing and validation approach is defined
|
||||
|
||||
Focus: Reusable, maintainable component design with clear usage patterns.
|
||||
Reference in New Issue
Block a user