Initial commit
This commit is contained in:
Zhongwei Li
@@ -0,0 +1,112 @@
|
||||
# Command Configuration Patterns
|
||||
# Defines reusable patterns for Claude Code commands
|
||||
|
||||
Command_Categories:
|
||||
Analysis:
|
||||
- analyze-repo-for-claude
|
||||
- estimate-context-window
|
||||
- study-*
|
||||
- validate-*
|
||||
- scan-*
|
||||
|
||||
Development:
|
||||
- create-feature-task
|
||||
- implement-feature
|
||||
- create-test-plan
|
||||
- fix-bug
|
||||
|
||||
Quality:
|
||||
- comprehensive-test-review
|
||||
- validate-code-quality
|
||||
- scan-performance
|
||||
- scan-test-coverage
|
||||
|
||||
Documentation:
|
||||
- generate-primevue-reference
|
||||
- document-api
|
||||
- create-readme
|
||||
|
||||
Operations:
|
||||
- git-*
|
||||
- gh-*
|
||||
- deploy
|
||||
- migrate
|
||||
|
||||
Workflow_Chains:
|
||||
Feature_Development:
|
||||
steps:
|
||||
- create-feature-task
|
||||
- study-current-repo
|
||||
- implement-feature
|
||||
- create-test-plan
|
||||
- comprehensive-test-review
|
||||
- gh-create-pr
|
||||
|
||||
Bug_Fix:
|
||||
steps:
|
||||
- gh-issue-enhance
|
||||
- analyze-issue
|
||||
- fix-bug
|
||||
- test-fix
|
||||
- gh-pr-submit
|
||||
|
||||
Code_Review:
|
||||
steps:
|
||||
- scan-code-quality
|
||||
- scan-performance
|
||||
- scan-test-coverage
|
||||
- generate-review-report
|
||||
|
||||
Context_Sharing:
|
||||
# Define what context flows between commands
|
||||
analyze_to_implement:
|
||||
from: analyze-*
|
||||
to: implement-*, fix-*
|
||||
shares: [findings, patterns, architecture]
|
||||
|
||||
scan_to_fix:
|
||||
from: scan-*, validate-*
|
||||
to: fix-*, improve-*
|
||||
shares: [issues, priorities, locations]
|
||||
|
||||
test_to_deploy:
|
||||
from: test-*, scan-test-coverage
|
||||
to: deploy, gh-pr-*
|
||||
shares: [results, coverage, confidence]
|
||||
|
||||
Cache_Patterns:
|
||||
# How long to cache results from different command types
|
||||
Analysis_Commands:
|
||||
ttl: 3600 # 1 hour
|
||||
invalidate_on: [file_changes, branch_switch]
|
||||
|
||||
Scan_Commands:
|
||||
ttl: 1800 # 30 minutes
|
||||
invalidate_on: [file_changes]
|
||||
|
||||
Build_Commands:
|
||||
ttl: 300 # 5 minutes
|
||||
invalidate_on: [any_change]
|
||||
|
||||
Risk_Assessment:
|
||||
High_Risk_Commands:
|
||||
commands:
|
||||
- deploy
|
||||
- migrate
|
||||
- cleanup-*
|
||||
- delete-*
|
||||
triggers: [confirmation, backup, dry_run]
|
||||
|
||||
Medium_Risk_Commands:
|
||||
commands:
|
||||
- refactor-*
|
||||
- update-dependencies
|
||||
- merge-*
|
||||
triggers: [plan_first, test_after]
|
||||
|
||||
Low_Risk_Commands:
|
||||
commands:
|
||||
- analyze-*
|
||||
- scan-*
|
||||
- study-*
|
||||
triggers: []
|
||||
@@ -0,0 +1,60 @@
|
||||
---
|
||||
title: "Create Feature Development Task"
|
||||
description: "Set up comprehensive feature development task with proper tracking"
|
||||
command_type: "development"
|
||||
last_updated: "2025-11-02"
|
||||
related_docs:
|
||||
- "./use-command-template.md"
|
||||
- "../../references/python-development-orchestration.md"
|
||||
---
|
||||
|
||||
# Create Feature Development Task
|
||||
|
||||
I need to create a structured development task for: $ARGUMENTS
|
||||
|
||||
## Your Task
|
||||
|
||||
Set up a comprehensive feature development task with proper tracking, phases, and documentation.
|
||||
|
||||
## Execution Steps
|
||||
|
||||
1. **Parse Feature Requirements**
|
||||
- Extract feature name and description from $ARGUMENTS
|
||||
- Identify key requirements and constraints
|
||||
- Determine complexity and scope
|
||||
|
||||
2. **Generate Task Structure**
|
||||
- Use the feature task template as base
|
||||
- Customize phases based on feature type
|
||||
- Add specific acceptance criteria
|
||||
- Include relevant technical considerations
|
||||
|
||||
3. **Create Task Documentation**
|
||||
- Copy template from ~/.claude/templates/feature-task-template.md
|
||||
- Fill in all sections with feature-specific details
|
||||
- Save to appropriate location (suggest: .claude/tasks/[feature-name].md)
|
||||
- Create initial git branch if requested
|
||||
|
||||
4. **Set Up Tracking**
|
||||
- Add task to TODO list if applicable
|
||||
- Create initial checkpoints
|
||||
- Set up progress markers
|
||||
- Configure any automation needed
|
||||
|
||||
## Template Usage
|
||||
|
||||
@include templates/feature-task-template.md
|
||||
|
||||
## Context Preservation
|
||||
|
||||
When creating the task, preserve:
|
||||
|
||||
- Initial requirements
|
||||
- Key technical decisions
|
||||
- File locations
|
||||
- Dependencies identified
|
||||
- Risk factors
|
||||
|
||||
## Integration
|
||||
|
||||
**Prerequisites**: Clear feature requirements **Follow-up**: `/development:implement-feature [task-file]` **Related**: `create-test-plan`, `estimate-context-window`
|
||||
@@ -0,0 +1,59 @@
|
||||
# Command Template
|
||||
|
||||
## Purpose
|
||||
|
||||
[Single sentence describing what the command does]
|
||||
|
||||
## Your Task
|
||||
|
||||
[Clear description of what needs to be accomplished with: $ARGUMENTS]
|
||||
|
||||
## Execution Steps
|
||||
|
||||
1. **Phase 1 - Analysis**
|
||||
- [Step 1]
|
||||
- [Step 2]
|
||||
- [Step 3]
|
||||
|
||||
2. **Phase 2 - Implementation**
|
||||
- [Step 1]
|
||||
- [Step 2]
|
||||
- [Step 3]
|
||||
|
||||
3. **Phase 3 - Validation**
|
||||
- [Step 1]
|
||||
- [Step 2]
|
||||
- [Step 3]
|
||||
|
||||
## Context Preservation
|
||||
|
||||
Cache the following for future commands:
|
||||
|
||||
- Key findings
|
||||
- Decisions made
|
||||
- Files modified
|
||||
- Patterns identified
|
||||
|
||||
## Expected Output
|
||||
|
||||
```markdown
|
||||
## [Command] Results
|
||||
|
||||
### Summary
|
||||
|
||||
- [Key outcome 1]
|
||||
- [Key outcome 2]
|
||||
|
||||
### Details
|
||||
|
||||
[Structured output based on command type]
|
||||
|
||||
### Next Steps
|
||||
|
||||
- [Recommended follow-up action 1]
|
||||
- [Recommended follow-up action 2]
|
||||
```
|
||||
|
||||
## Integration
|
||||
|
||||
**Prerequisites**: [What should be done before this command] **Follow-up**: [What commands naturally follow this one] **Related**: [Other commands that work well with this]
|
||||
@@ -0,0 +1,74 @@
|
||||
---
|
||||
title: "Use Command Template"
|
||||
description: "Create new Claude Code command following established patterns"
|
||||
command_type: "development"
|
||||
last_updated: "2025-11-02"
|
||||
related_docs:
|
||||
- "./templates/command-template.md"
|
||||
- "./create-feature-task.md"
|
||||
---
|
||||
|
||||
# Use Command Template
|
||||
|
||||
I need to create a new command using the standard template for: $ARGUMENTS
|
||||
|
||||
## Your Task
|
||||
|
||||
Create a new Claude Code command following our established patterns and templates.
|
||||
|
||||
## Execution Steps
|
||||
|
||||
1. **Determine Command Type**
|
||||
- Parse command purpose from $ARGUMENTS
|
||||
- Identify appropriate category (analysis/development/quality/etc)
|
||||
- Choose suitable command name (verb-noun format)
|
||||
|
||||
2. **Apply Template**
|
||||
- Start with base template from [command-template.md](./templates/command-template.md)
|
||||
- Customize sections for specific command purpose
|
||||
- Ensure all required sections are included
|
||||
- Add command-specific flags if needed
|
||||
|
||||
3. **Configure Integration**
|
||||
- Check [command-patterns.yml](./config/command-patterns.yml) for workflow placement
|
||||
- Identify prerequisite commands
|
||||
- Define what context this command produces
|
||||
- Add to appropriate workflow chains
|
||||
|
||||
4. **Create Command File**
|
||||
- Determine correct folder based on category
|
||||
- Create .md file with command content
|
||||
- Verify @include references work correctly
|
||||
- Test with example usage
|
||||
|
||||
## Template Structure
|
||||
|
||||
The standard template includes:
|
||||
|
||||
- Purpose (single sentence)
|
||||
- Task description with $ARGUMENTS
|
||||
- Phased execution steps
|
||||
- Context preservation rules
|
||||
- Expected output format
|
||||
- Integration guidance
|
||||
|
||||
## Best Practices
|
||||
|
||||
- Keep commands focused on a single responsibility
|
||||
- Use clear verb-noun naming (analyze-dependencies, create-component)
|
||||
- Include at least 3 example usages
|
||||
- Define what gets cached for reuse
|
||||
- Specify prerequisite and follow-up commands
|
||||
|
||||
## Example Usage
|
||||
|
||||
```bash
|
||||
# Create a new analysis command
|
||||
/development:use-command-template analyze API endpoints for rate limiting needs
|
||||
|
||||
# Create a new validation command
|
||||
/development:use-command-template validate database migrations for safety
|
||||
|
||||
# Create a new generation command
|
||||
/development:use-command-template generate Pydantic classes from API schema
|
||||
```
|
||||
Reference in New Issue
Block a user