Migrate legacy SDR_stochastic modules into the vrp-toolkit three-layer architecture.
npx skills add https://github.com/dudusoar/VRP-Toolkit --skill migrate-module
Please help me install this Agent Skill. Skill: migrate-module Source: https://github.com/dudusoar/VRP-Toolkit/tree/main/.claude/skills/migrate-module Command: npx skills add https://github.com/dudusoar/VRP-Toolkit --skill migrate-module
Migrating legacy SDR_stochastic modules into the vrp-toolkit architecture enables reuse, standardization, and easier maintenance across projects.
Follow the MIGRATION_GUIDE.md and refer to references/migration_map.md to begin migrating a module from SDR_stochastic to vrp-toolkit; start with mapping source to destination, then refactor accordingly.
High-intent search queries and answers about installing and using this skill.
To migrate legacy research code into a three-layer architecture, you move paper-specific logic into generic Problem, Algorithm, and Data layers. This refactoring standardizes modules for reuse and easier maintenance across projects.
The refactoring workflow for SDR_stochastic modules follows a structured process: identify, plan, refactor, implement, and verify. You start by mapping source files to destination layers using a migration map, then apply the refactoring guidelines.
Yes, you can convert research notebooks into educational tutorials during module migration. The process transforms existing notebooks into tutorials that illustrate the three-layer migration pattern with concrete examples.
Yes, you need the migration guide and a migration map file to map source to destination correctly. These references specify the structured migration workflow, file mappings, and documentation requirements needed for standardization.
The best way to standardize paper-specific stochastic code is applying a three-layer migration pattern. Moving logic into generic Problem, Algorithm, and Data layers separates research specifics from reusable architecture.
Migrating modules without following a structured migration map risks breaking the standardization and reuse goals. Skipping the specified file mappings and refactoring guidelines leads to poorly integrated three-layer architecture and maintenance issues.
jokken79Query NotebookLM notebooks for source-grounded, citation-backed answers.
ryan-mahoneyGenerate end-to-end integration tests for cross-module pathways during SpecOps migrations.
coeus-venturesGenerate React UI components with UI-only rendering and hook-based logic separation.
japurcellSimplify recently changed code while preserving behavior and passing tests.
