legacy-modernization
Modernize legacy systems using proven migration patterns like strangler fig, feature flags, and incremental refactoring. Use when planning system migrations, modernizing monoliths, or managing technical debt.
What this skill does
# Legacy Modernization Expert guidance for safe, incremental modernization of legacy systems, frameworks, and dependencies using proven migration patterns and risk mitigation strategies. ## When to Use This Skill - Planning framework migrations (jQuery to React, Java 8 to 17, Python 2 to 3) - Decomposing monoliths into microservices or modular architectures - Modernizing databases (stored procedures to ORMs, schema migrations) - Reducing technical debt with a phased, low-risk approach - Updating outdated dependencies with backward compatibility concerns - Establishing test coverage for untested legacy code before refactoring - Designing rollback procedures for migration phases - Implementing feature flags for gradual rollout of modernized components ## Quick Reference | Task | Load reference | | --- | --- | | Strangler fig, feature flags, migration checklists, rollback procedures | `skills/legacy-modernization/references/modernization-patterns.md` | ## Workflow ### 1. Assessment Inventory legacy components, risks, and dependencies before changing anything. - Map the dependency graph and identify high-risk areas - Define modernization goals and phased milestones - Establish success metrics (test coverage, performance, defect rate) - Prioritize based on business value and risk ### 2. Safety Net Setup Establish guardrails before any migration work begins. - Add characterization tests for existing behavior - Set up feature flags for gradual rollout - Create compatibility layers and adapter interfaces - Document current behavior and integration points ### 3. Incremental Execution Apply the strangler fig pattern: replace components one at a time. - Route traffic gradually to new implementations - Maintain backward compatibility at every step - Run old and new paths in parallel where possible - Monitor for regressions continuously ### 4. Stabilization Validate the migration and retire legacy paths. - Run full regression suites against new implementations - Monitor adoption metrics and error rates - Deprecate and remove legacy code paths - Document the new architecture and migration decisions ## Common Mistakes - Attempting big-bang rewrites instead of incremental migration - Refactoring without tests covering existing behavior - Removing backward compatibility before all consumers migrate - Skipping rollback planning for each migration phase - Ignoring data migration complexity and state synchronization - Not involving stakeholders in deprecation timelines
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.