mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-10 02:24:35 +08:00
d8ead86b67
Optimized 7 key CLI prompt templates following best practices: Key improvements: - Prioritize critical instructions at the top (role, constraints, output format) - Replace verbose/persuasive language with direct, precise wording - Add explicit planning requirements before final output - Remove emojis and unnecessary adjectives - Simplify section headers and structure - Convert verbose checklists to concise bullet points - Add self-review checklists for quality control Files optimized: - analysis/01-diagnose-bug-root-cause.txt: Simplified persona, added planning steps - analysis/02-analyze-code-patterns.txt: Removed emojis, added planning requirements - planning/01-plan-architecture-design.txt: Streamlined capabilities, direct language - documentation/module-readme.txt: Concise structure, planning requirements - development/02-implement-feature.txt: Clear planning phase, simplified checklist - development/02-generate-tests.txt: Direct requirements, focused verification - planning-roles/product-owner.md: Simplified role definition, added planning process Benefits: - Clearer expectations for model output - Reduced token usage through conciseness - Better focus on critical instructions - Consistent structure across templates - Explicit planning/self-critique requirements
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.
|