mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-11 02:33:51 +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
49 lines
1.4 KiB
Plaintext
49 lines
1.4 KiB
Plaintext
Generate module documentation focused on understanding and usage.
|
|
|
|
## Planning Required
|
|
Before providing documentation, you MUST:
|
|
1. Understand what the module does and why it exists
|
|
2. Review existing documentation to avoid duplication
|
|
3. Prepare practical usage examples
|
|
4. Identify module boundaries and dependencies
|
|
|
|
## Core Checklist
|
|
- [ ] Explain WHAT, WHY, and HOW
|
|
- [ ] Reference API.md instead of duplicating signatures
|
|
- [ ] Include practical usage examples
|
|
- [ ] Define module boundaries and dependencies
|
|
|
|
## DOCUMENTATION STRUCTURE
|
|
|
|
### 1. Purpose
|
|
- **What**: Clearly state what this module is responsible for.
|
|
- **Why**: Explain the problem it solves.
|
|
- **Boundaries**: Define what is in and out of scope.
|
|
|
|
### 2. Core Concepts
|
|
- Explain key concepts, patterns, or abstractions.
|
|
|
|
### 3. Usage Scenarios
|
|
- Provide 2-4 common use cases with code examples.
|
|
|
|
### 4. Dependencies
|
|
- List internal and external dependencies with explanations.
|
|
|
|
### 5. Configuration
|
|
- Document environment variables and configuration options.
|
|
|
|
### 6. Testing
|
|
- Explain how to run tests for the module.
|
|
|
|
### 7. Common Issues
|
|
- List common problems and their solutions.
|
|
|
|
## Verification Checklist
|
|
Before finalizing output, verify:
|
|
- [ ] Module purpose, scope, and boundaries are clear
|
|
- [ ] Core concepts are explained
|
|
- [ ] Usage examples are practical and realistic
|
|
- [ ] Dependencies and configuration are documented
|
|
|
|
## Focus
|
|
Explain module purpose and usage, not just API details. |