mirror of
https://github.com/steipete/agent-rules.git
synced 2025-12-16 12:00:09 +01:00
b14f443855
Added comprehensive rules adapted from vincenthopf/claude-code: Development Workflows: - commit.mdc, commit-fast.mdc: Git commit workflows - add-to-changelog.mdc: Structured changelog updates - pr-review.mdc: Multi-role PR review checklist Code Quality: - check.mdc: Multi-language code quality checks - clean.mdc: Auto-fix formatting and linting - code-analysis.mdc: Advanced analysis options Problem Solving: - analyze-issue.mdc: GitHub issue analysis - bug-fix.mdc: Complete bug-fixing workflow - implement-task.mdc: Methodical implementation - five.mdc: Five Whys root cause analysis Documentation: - create-docs.mdc: Comprehensive doc generation - mermaid.mdc: Diagram generation Project Setup: - context-prime.mdc: Load project context - create-command.mdc: Create custom commands Credit: @vincenthopf (https://github.com/vincenthopf/claude-code) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
56 lines
1.3 KiB
Plaintext
56 lines
1.3 KiB
Plaintext
# Implement Task
|
|
|
|
Approach task implementation methodically with careful planning and execution.
|
|
|
|
## Process:
|
|
|
|
### 1. Think Through Strategy
|
|
- Understand the complete requirement
|
|
- Identify key components needed
|
|
- Consider dependencies and constraints
|
|
- Plan the implementation approach
|
|
|
|
### 2. Evaluate Approaches
|
|
- List possible implementation strategies
|
|
- Compare pros and cons of each
|
|
- Consider:
|
|
- Performance implications
|
|
- Maintainability
|
|
- Scalability
|
|
- Code reusability
|
|
- Testing complexity
|
|
|
|
### 3. Consider Tradeoffs
|
|
- Short-term vs long-term benefits
|
|
- Complexity vs simplicity
|
|
- Performance vs readability
|
|
- Flexibility vs focused solution
|
|
- Time to implement vs perfect solution
|
|
|
|
### 4. Implementation Steps
|
|
1. Break down into subtasks
|
|
2. Start with core functionality
|
|
3. Implement incrementally
|
|
4. Test each component
|
|
5. Integrate components
|
|
6. Add error handling
|
|
7. Optimize if needed
|
|
8. Document decisions
|
|
|
|
### 5. Best Practices
|
|
- Write tests first (TDD approach)
|
|
- Keep functions small and focused
|
|
- Use meaningful names
|
|
- Comment complex logic
|
|
- Handle edge cases
|
|
- Consider future maintenance
|
|
|
|
## Checklist:
|
|
- [ ] Requirements fully understood
|
|
- [ ] Approach documented
|
|
- [ ] Tests written
|
|
- [ ] Code implemented
|
|
- [ ] Edge cases handled
|
|
- [ ] Documentation updated
|
|
- [ ] Code reviewed
|
|
- [ ] Performance acceptable |