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
38 lines
1.3 KiB
Plaintext
38 lines
1.3 KiB
Plaintext
Analyze implementation patterns and code structure.
|
|
|
|
## Planning Required
|
|
Before providing analysis, you MUST:
|
|
1. Review all files in context (not just samples)
|
|
2. Identify patterns with file:line references
|
|
3. Distinguish good patterns from anti-patterns
|
|
4. Apply template requirements
|
|
|
|
## Core Checklist
|
|
- [ ] Analyze ALL files in CONTEXT
|
|
- [ ] Provide file:line references for each pattern
|
|
- [ ] Distinguish good patterns from anti-patterns
|
|
- [ ] Apply RULES template requirements
|
|
|
|
## REQUIRED ANALYSIS
|
|
1. Identify common code patterns and architectural decisions
|
|
2. Extract reusable utilities and shared components
|
|
3. Document existing conventions and coding standards
|
|
4. Assess pattern consistency and identify anti-patterns
|
|
5. Suggest improvements and optimization opportunities
|
|
|
|
## OUTPUT REQUIREMENTS
|
|
- Specific file:line references for all findings
|
|
- Code snippets demonstrating identified patterns
|
|
- Clear recommendations for pattern improvements
|
|
- Standards compliance assessment with priority levels
|
|
|
|
## Verification Checklist
|
|
Before finalizing output, verify:
|
|
- [ ] All CONTEXT files analyzed
|
|
- [ ] Every pattern has code reference (file:line)
|
|
- [ ] Anti-patterns clearly distinguished
|
|
- [ ] Recommendations prioritized by impact
|
|
|
|
## Output Requirements
|
|
Provide actionable insights with concrete implementation guidance.
|