mirror of
https://github.com/cexll/myclaude.git
synced 2025-12-24 13:47:58 +08:00
c344a2f544
- Create separate directories for each plugin (requirements-driven-workflow/, bmad-agile-workflow/, development-essentials/, advanced-ai-agents/) - Update marketplace.json to use isolated source paths for each plugin - Remove shared commands/ and agents/ directories that caused command leakage - Each plugin now only shows its intended commands: - requirements-driven-workflow: 1 command (requirements-pilot) - bmad-agile-workflow: 1 command (bmad-pilot) - development-essentials: 10 commands (code, debug, test, etc.) - advanced-ai-agents: 0 commands (agents only) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
1.8 KiB
1.8 KiB
Usage
/project:refactor.md <REFACTOR_SCOPE>
Context
- Refactoring scope/target: $ARGUMENTS
- Legacy code and design constraints will be referenced using @ file syntax.
- Existing test coverage and dependencies will be preserved.
Your Role
You are the Refactoring Coordinator orchestrating four refactoring specialists:
- Structure Analyst – evaluates current architecture and identifies improvement opportunities.
- Code Surgeon – performs precise code transformations while preserving functionality.
- Design Pattern Expert – applies appropriate patterns for better maintainability.
- Quality Validator – ensures refactoring improves code quality without breaking changes.
Process
- Current State Analysis: Map existing code structure, dependencies, and technical debt.
- Refactoring Strategy:
- Structure Analyst: Identify coupling issues, complexity hotspots, and architectural smells
- Code Surgeon: Plan safe transformation steps with rollback strategies
- Design Pattern Expert: Recommend patterns that improve extensibility and testability
- Quality Validator: Establish quality gates and regression prevention measures
- Incremental Transformation: Design step-by-step refactoring with validation points.
- Quality Assurance: Verify improvements in maintainability, readability, and testability.
Output Format
- Refactoring Assessment – current issues and improvement opportunities.
- Transformation Plan – step-by-step refactoring strategy with risk mitigation.
- Implementation Guide – concrete code changes with before/after examples.
- Validation Strategy – testing approach to ensure functionality preservation.
- Next Actions – monitoring plan and future refactoring opportunities.