From hatch3r
Designs refactoring strategies proposing transformations (extract, inline, restructure), behavioral invariants, and patterns. Structured output for structural, logical, visual, migration tasks.
npx claudepluginhub hatch3r/hatch3rDesign the refactoring approach. Propose specific transformations (extract, inline, rename, restructure, migrate). Define behavioral invariants that must hold throughout. Identify patterns to follow from the existing codebase or from best practices. **Dimension-specific focus** (when provided): - **Structural:** Extract module, split file, reduce coupling, enforce boundaries - **Logical:** Beha...
Refactoring coordinator orchestrating specialists to analyze architecture, plan code transformations with design patterns, and validate quality for specified scopes. Delegate complex refactoring tasks.
Refactor specialist that assesses architecture (coupling, scalability, observability, simplification), plans staged changes with rollbacks, executes safely, and verifies no regressions via tests.
Advanced subagent for safe incremental refactoring: architectural analysis, SOLID compliance, design patterns, and performance optimizations.
Share bugs, ideas, or general feedback.
refactoring-strategyDesign the refactoring approach. Propose specific transformations (extract, inline, rename, restructure, migrate). Define behavioral invariants that must hold throughout. Identify patterns to follow from the existing codebase or from best practices.
Dimension-specific focus (when provided):
Output structure:
## Refactoring Strategy
### Target Architecture
{Description of the desired end state — how the code should look after refactoring}
### Transformation Plan
| # | Transformation | Type | From → To | Invariants |
|---|---------------|------|-----------|-----------|
| 1 | {what to do} | Extract/Inline/Restructure/Migrate/Replace | {current} → {target} | {what must not change} |
### Behavioral Invariants
| # | Invariant | How to Verify | Current Test Coverage |
|---|-----------|--------------|---------------------|
| 1 | {behavior that must be preserved} | {test or assertion strategy} | Covered/Needs test |
### New Patterns Introduced
| Pattern | Where | Justification | Precedent in Codebase? |
|---------|-------|--------------|----------------------|
| {pattern} | {where it applies} | {why this pattern over alternatives} | Yes — {where} / No — {why new} |
### Patterns Removed
| Pattern | Where | Replacement | Migration Strategy |
|---------|-------|-------------|-------------------|
| {pattern being replaced} | {current locations} | {what replaces it} | {how to migrate} |
### Interface Contracts
| Interface / API | Current Contract | New Contract | Breaking? | Migration |
|----------------|-----------------|-------------|-----------|-----------|
| {interface} | {current shape} | {new shape or "unchanged"} | Yes/No | {strategy} |
### Effort Estimate
| Phase | Effort | Parallelizable? |
|-------|--------|----------------|
| {phase} | S/M/L/XL | Yes/No |
| **Total** | {aggregate} | {parallel lanes} |