技能 Legacy Modernizer
📦

Legacy Modernizer

安全

Modernize legacy codebases and migrate outdated frameworks

Legacy systems create technical debt that slows development and increases security risks. This skill provides proven strategies for gradual modernization while maintaining backward compatibility.

支援: Claude Codex Code(CC)
🥉 72 青銅
1

下載技能 ZIP

2

在 Claude 中上傳

前往 設定 → 功能 → 技能 → 上傳技能

3

開啟並開始使用

測試它

正在使用「Legacy Modernizer」。 Assess technical debt in a 10-year-old Python 2.7 web application with 50K lines of code

預期結果:

  • Phase 1: Port to Python 3.8+ using 2to3 tool with manual review (4-6 weeks)
  • Phase 2: Update Django from 1.8 LTS to current LTS version (3-4 weeks)
  • Phase 3: Replace deprecated libraries with maintained alternatives (2-3 weeks)
  • Phase 4: Add type hints and modernize code style incrementally (ongoing)
  • Risk mitigation: Maintain parallel Python 2 environment until Phase 2 complete

正在使用「Legacy Modernizer」。 Create migration plan for jQuery to React component conversion

預期結果:

  • Week 1-2: Set up React build system alongside existing jQuery setup
  • Week 3-6: Convert isolated utility components first (forms, modals, tabs)
  • Week 7-10: Migrate page-level components using strangler fig pattern
  • Week 11-12: Remove jQuery dependencies and clean up legacy code
  • Key pattern: Use React portals for gradual integration with existing DOM

安全審計

安全
v1 • 2/25/2026

This is a prompt-only skill containing no executable code. Static analysis scanned 0 files with 0 security patterns detected. The skill provides guidance on legacy code modernization, framework migrations, and technical debt reduction without any file system access, network operations, or external command execution. Safe for publication.

0
已掃描檔案
0
分析行數
0
發現項
1
審計總數
未發現安全問題
審計者: claude

品質評分

38
架構
100
可維護性
87
內容
50
社群
100
安全
74
規範符合性

你能建構什麼

Enterprise Framework Migration

Plan and execute migration from legacy jQuery-based frontend to modern React architecture using strangler fig pattern for gradual replacement.

Legacy Backend Modernization

Transform monolithic Java 8 applications to modular Java 17+ architecture with dependency injection and improved testability.

Database Architecture Upgrade

Migrate from stored procedure-heavy databases to ORM-based architectures with proper abstraction layers and migration scripts.

試試這些提示

Legacy Code Assessment
Analyze this legacy codebase and identify the top 5 areas with highest technical debt. For each area, provide: (1) current state description, (2) risks of not modernizing, (3) recommended modernization approach, (4) estimated effort level. Code: [paste code or describe system]
Framework Migration Plan
Create a phased migration plan for moving from [legacy framework] to [modern framework]. Include: phase breakdown with milestones, backward compatibility strategy, testing approach for each phase, rollback procedures, and feature flag recommendations. Target system: [describe system]
Refactoring with Test Coverage
Help me refactor this legacy function using the 'add tests first' approach. Steps: (1) Write characterization tests that capture current behavior, (2) Identify refactoring opportunities, (3) Apply incremental changes with test verification, (4) Document any behavior changes. Legacy code: [paste code]
Dependency Update Strategy
Design a safe dependency update strategy for this project. Analyze: current dependency versions, available updates with breaking changes, recommended update order, compatibility testing requirements, and rollback plan. Project dependencies: [list dependencies]

最佳實務

  • Always add comprehensive tests before refactoring to capture existing behavior
  • Use the strangler fig pattern - gradually replace functionality, never big-bang rewrites
  • Maintain backward compatibility at each phase with clear deprecation timelines

避免

  • Attempting complete rewrites without incremental migration path
  • Removing legacy code before new implementation is fully tested in production
  • Ignoring backward compatibility requirements during framework migrations

常見問題

What is the strangler fig pattern for legacy modernization?
The strangler fig pattern gradually replaces legacy functionality by intercepting calls and routing them to new implementations. Over time, more functionality migrates until the legacy system can be removed. This approach minimizes risk by allowing rollback at any phase.
How do I maintain backward compatibility during framework migration?
Use adapter layers that translate between old and new interfaces, implement feature flags for gradual rollout, maintain parallel systems during transition, and provide clear deprecation warnings with migration timelines for API consumers.
What is the recommended approach for updating dependencies in legacy projects?
Update one dependency at a time, starting with non-breaking patches. Run full test suites after each update. For major version jumps, review changelogs for breaking changes, update code incrementally, and maintain rollback capability until the update is verified in production.
How do I convince stakeholders to invest in legacy modernization?
Quantify technical debt impact: slower feature delivery, security vulnerabilities, hiring challenges, and operational costs. Present modernization as risk reduction with measurable ROI through improved velocity, reduced incidents, and lower maintenance costs.
When should I refactor versus rewrite legacy code?
Refactor when the business logic is sound but implementation needs improvement. Rewrite only when the fundamental architecture is flawed, technology is unsupported, or technical debt makes incremental changes impractical. Always prefer refactoring with tests over rewrites.
How do I handle database modernization during legacy migration?
Use dual-write strategies during transition, create abstraction layers between application and database, migrate data incrementally with validation at each step, and maintain rollback procedures. Never migrate schema and application code in the same deployment.

開發者詳情

檔案結構

📄 SKILL.md