mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-10 02:24:35 +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>
59 lines
1.9 KiB
Plaintext
59 lines
1.9 KiB
Plaintext
Implement a new feature following project conventions and best practices.
|
|
|
|
## Planning Required
|
|
Before implementing, you MUST:
|
|
1. Study existing code patterns and conventions
|
|
2. Review project architecture and design principles
|
|
3. Plan implementation with error handling and tests
|
|
4. Document integration points and dependencies
|
|
|
|
## Core Checklist
|
|
- [ ] Study existing code patterns first
|
|
- [ ] Follow project conventions and architecture
|
|
- [ ] Include comprehensive tests
|
|
- [ ] Provide file:line references
|
|
|
|
## IMPLEMENTATION PHASES
|
|
|
|
### Analysis Phase
|
|
1. Study existing code patterns and conventions
|
|
2. Identify similar features and their implementation approaches
|
|
3. Review project architecture and design principles
|
|
4. Understand dependencies and integration points
|
|
|
|
### Implementation Phase
|
|
1. Create feature following established patterns
|
|
2. Implement with proper error handling and validation
|
|
3. Add comprehensive logging for debugging
|
|
4. Follow security best practices
|
|
|
|
### Integration Phase
|
|
1. Ensure seamless integration with existing systems
|
|
2. Update configuration files as needed
|
|
3. Add proper TypeScript types and interfaces
|
|
4. Update documentation and comments
|
|
|
|
### Testing Phase
|
|
1. Write unit tests covering edge cases
|
|
2. Add integration tests for feature workflows
|
|
3. Verify error scenarios are properly handled
|
|
4. Test performance and security implications
|
|
|
|
## OUTPUT REQUIREMENTS
|
|
- File:line references for all changes
|
|
- Code examples demonstrating key patterns
|
|
- Explanation of architectural decisions made
|
|
- Documentation of new dependencies or configurations
|
|
- Test coverage summary
|
|
|
|
## Verification Checklist
|
|
Before finalizing, verify:
|
|
- [ ] Follows existing patterns
|
|
- [ ] Complete test coverage
|
|
- [ ] Documentation updated
|
|
- [ ] No breaking changes
|
|
- [ ] Security and performance validated
|
|
|
|
## Focus
|
|
Production-ready implementation with comprehensive testing and documentation.
|