nickcrew/legacy-modernization
skills/legacy-modernization/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add nickcrew/claude-cortex legacy-modernizationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 7, 2026, 8:29 PM5.6s2 files scanned
SKILL.md
- name:
- legacy-modernization
- description:
- 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.
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 Skills
nickcrew/product-strategy
development
VerifiedTrustedCommunity
Product vision, roadmap development, and go-to-market execution with structured prioritization frameworks. Use when evaluating features, planning product direction, or assessing market fit.
15SKILL.mdUpdated Apr 7, 2026
nickcrew/agent-loops
development
VerifiedTrustedCommunity
Complete operational workflow for implementer agents (Codex, Gemini, etc.) making code changes and writing tests. Drives all work through atomic commits — each loop operates on the smallest complete, reviewable change. Defines the Code Change Loop, Test Writing Loop, Lint Gate, and Issue Filing process with circuit breakers, severity levels, and escalation rules. Requires `cortex git commit` for all commits. Includes bundled provider-aware review scripts that keep same-model shell-outs as the last resort, plus a fresh-context Codex fallback for code review and test audit. Use this skill when starting any implementation task.
15SKILL.mdUpdated Apr 7, 2026
nickcrew/product-manager
development
VerifiedTrustedCommunity
Use this skill when writing product requirements documents, prioritizing features, creating user stories, defining acceptance criteria, or setting product metrics. Trigger phrases: 'write a PRD for', 'prioritize this feature backlog', 'write user stories for', 'help me define acceptance criteria', 'what metrics should we track for'. Not for writing code, designing UI mockups, or conducting user research interviews.
13SKILL.mdUpdated Apr 7, 2026
nickcrew/playwright-cli
tools
VerifiedTrustedCommunity
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
13SKILL.mdUpdated Apr 7, 2026