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>
75 lines
1.8 KiB
Plaintext
75 lines
1.8 KiB
Plaintext
# Create Command
|
|
|
|
Guide for creating new custom Claude commands with proper structure.
|
|
|
|
## Process:
|
|
|
|
### 1. Understanding Purpose
|
|
- What problem does this command solve?
|
|
- Who will use this command?
|
|
- What is the expected output?
|
|
- How will users interact with it?
|
|
|
|
### 2. Category Classification
|
|
Determine command type:
|
|
- **Planning**: Project setup, architecture decisions
|
|
- **Implementation**: Code generation, feature development
|
|
- **Analysis**: Code review, performance analysis
|
|
- **Testing**: Test creation, validation
|
|
- **Documentation**: Docs generation, updates
|
|
- **Workflow**: Multi-step processes
|
|
- **Utility**: Helper commands, tools
|
|
|
|
### 3. Pattern Selection
|
|
Study similar existing commands:
|
|
- Analyze structure and flow
|
|
- Note common patterns
|
|
- Identify reusable components
|
|
- Follow established conventions
|
|
|
|
### 4. Command Location
|
|
Choose appropriate location:
|
|
- **Project-specific**: `.claude/commands/`
|
|
- **User-level**: `~/.claude/commands/`
|
|
- Consider reusability and context
|
|
|
|
### 5. Command Structure
|
|
Create with these sections:
|
|
- **Title**: Clear, action-oriented name
|
|
- **Description**: One-line summary
|
|
- **Usage**: How to invoke with parameters
|
|
- **Process**: Step-by-step instructions
|
|
- **Examples**: Concrete usage examples
|
|
- **Output**: Expected results
|
|
- **Notes**: Special considerations
|
|
|
|
## Template:
|
|
```markdown
|
|
# Command Name
|
|
|
|
Brief description of what this command does.
|
|
|
|
## Usage:
|
|
`/command-name [arguments]`
|
|
|
|
## Process:
|
|
1. First step
|
|
2. Second step
|
|
3. Third step
|
|
|
|
## Examples:
|
|
- Example 1
|
|
- Example 2
|
|
|
|
## Notes:
|
|
- Important considerations
|
|
- Limitations
|
|
```
|
|
|
|
## Best Practices:
|
|
- Keep commands focused and single-purpose
|
|
- Include parameter validation
|
|
- Provide helpful error messages
|
|
- Document expected inputs/outputs
|
|
- Consider edge cases
|
|
- Test thoroughly before finalizing |