mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-11 02:33:51 +08:00
- Streamlined analysis templates (architecture, pattern, performance, quality, security) - Simplified development templates (component, debugging, feature, refactor, testing) - Optimized documentation templates (api, folder-navigation, module-readme, project-architecture, project-examples, project-readme) - Enhanced planning templates (concept-eval, migration, task-breakdown) - Improved verification templates (codex-technical, cross-validation, gemini-strategic) - Updated claude-module-unified memory template - Refined workflow-architecture documentation 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
50 lines
1.7 KiB
Plaintext
50 lines
1.7 KiB
Plaintext
Implement a new feature following project conventions and best practices.
|
|
|
|
## CORE CHECKLIST ⚡
|
|
□ Study existing code patterns BEFORE implementing
|
|
□ Follow established project conventions and architecture
|
|
□ Include comprehensive tests (unit + integration)
|
|
□ Provide file:line references for all changes
|
|
|
|
## 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 ✓
|
|
□ Implementation follows existing patterns (no divergence)
|
|
□ Complete test coverage (unit + integration)
|
|
□ Documentation updated (code comments + external docs)
|
|
□ Integration verified (no breaking changes)
|
|
□ Security and performance validated
|
|
|
|
Focus: Production-ready implementation with comprehensive testing and documentation.
|