[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WYN0CCBNRZMX2EM72R3MKQ":3,"skill-same:01M6WYN0CCBNRZMX2EM72R3MKQ":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M6WYN0CCBNRZMX2EM72R3MKQ","legacy-modernizer",null,"Designs incremental migration strategies, identifies service boundaries, produces dependency maps and migration roadmaps, and generates API facade designs for aging codebases. Use when modernizing legacy systems, implementing strangler fig pattern or branch by abstraction, decomposing monoliths, upgrading frameworks or languages, or reducing technical debt without disrupting business operations.","PIXARTSeu\u002FSynapse","PIXARTSeu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F274446381?v=4","01M6RB4XPN9YBZCRY4FVN9PJCT","Pixarts ","01M6RB4XTF8G9KHQEMC21FGDKD",12,"MIT","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Flegacy-modernizer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"legacy modernizer","Legacy","debt","architecture","when","implementing","technical debt","strategies","pattern","maps","master","engineer","dependency","specialized","branch","refactoring","api","analysis","code","modernization","2026-11-10 10:12:30",false,"---\nname: legacy-modernizer\ndescription: Designs incremental migration strategies, identifies service boundaries, produces dependency maps and migration roadmaps, and generates API facade designs for aging codebases. Use when modernizing legacy systems, implementing strangler fig pattern or branch by abstraction, decomposing monoliths, upgrading frameworks or languages, or reducing technical debt without disrupting business operations.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: specialized\n  triggers: legacy modernization, strangler fig, incremental migration, technical debt, legacy refactoring, system migration, legacy system, modernize codebase\n  role: specialist\n  scope: architecture\n  output-format: code+analysis\n  related-skills: test-master, devops-engineer\n---\n\n# Legacy Modernizer\n\n## Core Workflow\n\n1. **Assess system** — Analyze codebase, dependencies, risks, and business constraints. Produce a dependency map and risk register before proceeding.\n   - *Validation checkpoint:* Confirm all external integrations and data contracts are documented before moving to step 2.\n\n2. **Plan migration** — Design an incremental roadmap with explicit rollback strategies per phase. Reference `references\u002Fsystem-assessment.md` for code analysis templates.\n   - *Validation checkpoint:* Confirm each phase has a defined rollback trigger and owner.\n\n3. **Build safety net** — Create characterization tests and monitoring before touching production code. Target 80%+ coverage of existing behavior.\n   - *Validation checkpoint:* Run the characterization test suite and confirm it passes green on the unmodified legacy system before proceeding.\n\n4. **Migrate incrementally** — Apply strangler fig pattern with feature flags. Route traffic via a facade; shift load gradually.\n   - *Validation checkpoint:* Verify error rates and latency metrics remain within baseline thresholds after each traffic increment (e.g., 5% → 25% → 50% → 100%).\n\n5. **Validate & iterate** — Run full test suite, review monitoring dashboards, and confirm business behavior is preserved before retiring legacy code.\n   - *Validation checkpoint:* New code must be proven stable at 100% traffic for at least one release cycle before legacy path is removed.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Strangler Fig | `references\u002Fstrangler-fig-pattern.md` | Incremental replacement, facade layer, routing |\n| Refactoring | `references\u002Frefactoring-patterns.md` | Extract service, branch by abstraction, adapters |\n| Migration | `references\u002Fmigration-strategies.md` | Database, UI, API, framework migrations |\n| Testing | `references\u002Flegacy-testing.md` | Characterization tests, golden master, approval |\n| Assessment | `references\u002Fsystem-assessment.md` | Code analysis, dependency mapping, risk evaluation |\n\n## Code Examples\n\n### Strangler Fig Facade (Python)\n```python\n# facade.py — routes requests to legacy or new service based on a feature flag\nimport os\nfrom legacy_service import LegacyOrderService\nfrom new_service import NewOrderService\n\nclass OrderServiceFacade:\n    def __init__(self):\n        self._legacy = LegacyOrderService()\n        self._new = NewOrderService()\n\n    def get_order(self, order_id: str):\n        if os.getenv(\"USE_NEW_ORDER_SERVICE\", \"false\").lower() == \"true\":\n            return self._new.fetch(order_id)\n        return self._legacy.get(order_id)\n```\n\n### Feature Flag Wrapper\n```python\n# feature_flags.py — thin wrapper around an environment or config-based flag store\nimport os\n\ndef flag_enabled(flag_name: str, default: bool = False) -> bool:\n    \"\"\"Check whether a migration feature flag is active.\"\"\"\n    return os.getenv(flag_name, str(default)).lower() == \"true\"\n\n# Usage\nif flag_enabled(\"USE_NEW_PAYMENT_GATEWAY\"):\n    result = new_gateway.charge(order)\nelse:\n    result = legacy_gateway.charge(order)\n```\n\n### Characterization Test Template (pytest)\n```python\n# test_characterization_orders.py\n# Captures existing legacy behavior as a golden-master safety net.\nimport pytest\nfrom legacy_service import LegacyOrderService\n\nservice = LegacyOrderService()\n\n@pytest.mark.parametrize(\"order_id,expected_status\", [\n    (\"ORD-001\", \"SHIPPED\"),\n    (\"ORD-002\", \"PENDING\"),\n    (\"ORD-003\", \"CANCELLED\"),\n])\ndef test_order_status_golden_master(order_id, expected_status):\n    \"\"\"Fail loudly if legacy behavior changes unexpectedly.\"\"\"\n    result = service.get(order_id)\n    assert result[\"status\"] == expected_status, (\n        f\"Characterization broken for {order_id}: \"\n        f\"expected {expected_status}, got {result['status']}\"\n    )\n```\n\n## Constraints\n\n### MUST DO\n- Maintain zero production disruption during all migrations\n- Create comprehensive test coverage before refactoring (target 80%+)\n- Use feature flags for all incremental rollouts\n- Implement monitoring and rollback procedures\n- Document all migration decisions and rationale\n- Preserve existing business logic and behavior\n- Communicate progress and risks transparently\n\n### MUST NOT DO\n- Big bang rewrites or replacements\n- Skip testing legacy behavior before changes\n- Deploy without rollback capability\n- Break existing integrations or APIs\n- Ignore technical debt in new code\n- Rush migrations without proper validation\n- Remove legacy code before new code is proven\n\n## Output Templates\n\nWhen implementing modernization, provide:\n1. Assessment summary (risks, dependencies, approach)\n2. Migration plan (phases, rollback strategy, metrics)\n3. Implementation code (facades, adapters, new services)\n4. Test coverage (characterization, integration, e2e)\n5. Monitoring setup (metrics, alerts, dashboards)\n\n## Knowledge Reference\n\nStrangler fig pattern, branch by abstraction, characterization testing, incremental migration, feature flags, canary deployments, API versioning, database refactoring, microservices extraction, technical debt reduction, zero-downtime deployment\n","# Legacy Modernizer\n\n## Core Workflow\n\n1. **Assess system** — Analyze codebase, dependencies, risks, and business constraints. Produce a dependency map and risk register before proceeding.\n   - *Validation checkpoint:* Confirm all external integrations and data contracts are documented before moving to step 2.\n\n2. **Plan migration** — Design an incremental roadmap with explicit rollback strategies per phase. Reference `references\u002Fsystem-assessment.md` for code analysis templates.\n   - *Validation checkpoint:* Confirm each phase has a defined rollback trigger and owner.\n\n3. **Build safety net** — Create characterization tests and monitoring before touching production code. Target 80%+ coverage of existing behavior.\n   - *Validation checkpoint:* Run the characterization test suite and confirm it passes green on the unmodified legacy system before proceeding.\n\n4. **Migrate incrementally** — Apply strangler fig pattern with feature flags. Route traffic via a facade; shift load gradually.\n   - *Validation checkpoint:* Verify error rates and latency metrics remain within baseline thresholds after each traffic increment (e.g., 5% → 25% → 50% → 100%).\n\n5. **Validate & iterate** — Run full test suite, review monitoring dashboards, and confirm business behavior is preserved before retiring legacy code.\n   - *Validation checkpoint:* New code must be proven stable at 100% traffic for at least one release cycle before legacy path is removed.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Strangler Fig | `references\u002Fstrangler-fig-pattern.md` | Incremental replacement, facade layer, routing |\n| Refactoring | `references\u002Frefactoring-patterns.md` | Extract service, branch by abstraction, adapters |\n| Migration | `references\u002Fmigration-strategies.md` | Database, UI, API, framework migrations |\n| Testing | `references\u002Flegacy-testing.md` | Characterization tests, golden master, approval |\n| Assessment | `references\u002Fsystem-assessment.md` | Code analysis, dependency mapping, risk evaluation |\n\n## Code Examples\n\n### Strangler Fig Facade (Python)\n```python\n# facade.py — routes requests to legacy or new service based on a feature flag\nimport os\nfrom legacy_service import LegacyOrderService\nfrom new_service import NewOrderService\n\nclass OrderServiceFacade:\n    def __init__(self):\n        self._legacy = LegacyOrderService()\n        self._new = NewOrderService()\n\n    def get_order(self, order_id: str):\n        if os.getenv(\"USE_NEW_ORDER_SERVICE\", \"false\").lower() == \"true\":\n            return self._new.fetch(order_id)\n        return self._legacy.get(order_id)\n```\n\n### Feature Flag Wrapper\n```python\n# feature_flags.py — thin wrapper around an environment or config-based flag store\nimport os\n\ndef flag_enabled(flag_name: str, default: bool = False) -> bool:\n    \"\"\"Check whether a migration feature flag is active.\"\"\"\n    return os.getenv(flag_name, str(default)).lower() == \"true\"\n\n# Usage\nif flag_enabled(\"USE_NEW_PAYMENT_GATEWAY\"):\n    result = new_gateway.charge(order)\nelse:\n    result = legacy_gateway.charge(order)\n```\n\n### Characterization Test Template (pytest)\n```python\n# test_characterization_orders.py\n# Captures existing legacy behavior as a golden-master safety net.\nimport pytest\nfrom legacy_service import LegacyOrderService\n\nservice = LegacyOrderService()\n\n@pytest.mark.parametrize(\"order_id,expected_status\", [\n    (\"ORD-001\", \"SHIPPED\"),\n    (\"ORD-002\", \"PENDING\"),\n    (\"ORD-003\", \"CANCELLED\"),\n])\ndef test_order_status_golden_master(order_id, expected_status):\n    \"\"\"Fail loudly if legacy behavior changes unexpectedly.\"\"\"\n    result = service.get(order_id)\n    assert result[\"status\"] == expected_status, (\n        f\"Characterization broken for {order_id}: \"\n        f\"expected {expected_status}, got {result['status']}\"\n    )\n```\n\n## Constraints\n\n### MUST DO\n- Maintain zero production disruption during all migrations\n- Create comprehensive test coverage before refactoring (target 80%+)\n- Use feature flags for all incremental rollouts\n- Implement monitoring and rollback procedures\n- Document all migration decisions and rationale\n- Preserve existing business logic and behavior\n- Communicate progress and risks transparently\n\n### MUST NOT DO\n- Big bang rewrites or replacements\n- Skip testing legacy behavior before changes\n- Deploy without rollback capability\n- Break existing integrations or APIs\n- Ignore technical debt in new code\n- Rush migrations without proper validation\n- Remove legacy code before new code is proven\n\n## Output Templates\n\nWhen implementing modernization, provide:\n1. Assessment summary (risks, dependencies, approach)\n2. Migration plan (phases, rollback strategy, metrics)\n3. Implementation code (facades, adapters, new services)\n4. Test coverage (characterization, integration, e2e)\n5. Monitoring setup (metrics, alerts, dashboards)\n\n## Knowledge Reference\n\nStrangler fig pattern, branch by abstraction, characterization testing, incremental migration, feature flags, canary deployments, API versioning, database refactoring, microservices extraction, technical debt reduction, zero-downtime deployment\n",{"name":5,"license":15,"metadata":49,"description":7},{"role":50,"scope":27,"author":51,"domain":37,"version":52,"triggers":53,"output-format":54,"related-skills":55},"specialist","https:\u002F\u002Fgithub.com\u002FJeffallan","1.1.0","legacy modernization, strangler fig, incremental migration, technical debt, legacy refactoring, system migration, legacy system, modernize codebase","code+analysis","test-master, devops-engineer","main","c19c0bc0a04d25a849ce749fe88250e688f06437","packages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Flegacy-modernizer",1,"https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse","https:\u002F\u002Fgithub.com\u002FPIXARTSeu","https:\u002F\u002Fpixarts.eu\u002F","2026-09-24 06:30:45",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add PIXARTSeu\u002FSynapse --skill legacy-modernizer",{"tool":70,"command":71},"bunx","bunx skills add PIXARTSeu\u002FSynapse --skill legacy-modernizer",{"tool":73,"command":74},"pnpm","pnpm dlx skills add PIXARTSeu\u002FSynapse --skill legacy-modernizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Flegacy-modernizer\u002FSKILL.md",true,[],[79,109,116,142,164,191],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":91,"publishedAt":44},"01M6X0ECZKGP44NP2JW588B9RG","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[85,90],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[92,93,94,95,96,97,98,99,100,101,102,42,103,104,39,105,106,107,108,28],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","components","react components","guidelines","tasks","Optimization","data","patterns","next","triggers","data fetching",{"skillNo":110,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":115,"publishedAt":44},"01M6X05WCVH879XKZEAQ15PHQX","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Fskill\u002Fvercel-react-best-practices\u002FSKILL.md",[113,114],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[92,93,94,95,96,97,98,99,100,101,102,42,103,104,39,105,106,107,108,28],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":126,"publishedAt":44},"01M6WZ286AR2SYE9GZYVW0CNYG","wordpress-pro","Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fwordpress-pro\u002FSKILL.md",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[127,128,129,97,130,98,42,131,40,132,133,134,135,136,137,138,139,140,141,28],"wordpress","wordpress pro","pro","security","tuning","laravel","reviewer","hooks","filters","expert","query","woocommerce","caching","themes","sanitization",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":150,"publishedAt":44},"01M6WZ1ZVG6PJ4PVN9RTK0BX7Z","websocket-engineer","Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fwebsocket-engineer\u002FSKILL.md",[148,149],{"categoryNo":123,"categoryName":124,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[151,35,152,27,42,153,154,40,133,155,136,156,157,158,159,160,161,162,163,28],"websocket","websocket engineer","messaging","monitoring","fastapi","time","scaling","io","communication systems","presence","updates","socket","invoke",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":44},"01M6WZ1G86ZR73H0WNM6CGNRGF","vue-expert","Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR\u002FSSG projects, sets up Pinia stores, scaffolds Quasar\u002FCapacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fvue-expert\u002FSKILL.md",[170,171,172],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":123,"categoryName":124,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[174,136,175,176,97,177,99,178,179,180,181,182,183,184,185,186,187,188,189,190],"vue","vue expert","frontend","typescript","config","applications","Composition","projects","pinia","use","router","workers","mobile","reusable","worker","apps","hybrid",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":199,"publishedAt":44},"01M6WZ1AP3GFCBAMD712X8KRP7","vue-expert-js","Creates Vue 3 components, builds vanilla JS composables, configures Vite projects, and sets up routing and state management using JavaScript only — no TypeScript. Generates JSDoc-typed code with @typedef, @param, and @returns annotations for full type coverage without a TS compiler. Use when building Vue 3 applications with JavaScript only (no TypeScript), when projects require JSDoc-based type hints, when migrating from Vue 2 Options API to Composition API in JS, or when teams prefer vanilla JavaScript, .mjs modules, or need quick prototypes without TypeScript setup.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fvue-expert-js\u002FSKILL.md",[197,198],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[174,200,136,201,175,176,177,99,42,40,180,181,202,203,204,205,206,207,208,28],"js","vue expert js","coverage","only","up","modules","options","jsdoc","quick"]