legacy-migrate

Automate six-step migration of legacy APIs to modular admin and web services.

Updated Aug 27, 2026
Ready to run
npx skills add https://github.com/ryu-qqq/conventionHub --skill legacy-migrate
πŸ’¬ Prompt for ChatGPT / Claude Chatβ–Ό
Please help me install this Agent Skill.
Skill: legacy-migrate
Source: https://github.com/ryu-qqq/conventionHub/tree/main/.claude/skills/legacy-migrate
Command: npx skills add https://github.com/ryu-qqq/conventionHub --skill legacy-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

λ ˆκ±°μ‹œ APIλ₯Ό μƒˆ μ•„ν‚€ν…μ²˜λ‘œ μ™„μ „ λ§ˆμ΄κ·Έλ ˆμ΄μ…˜ν•˜λŠ” μžλ™ν™” μ›Œν¬ν”Œλ‘œμš°λ‘œ, 반볡 μž‘μ—…μ„ 쀄이고 λ§ˆμ΄κ·Έλ ˆμ΄μ…˜ μ‹œκ°„κ³Ό λ¦¬μ†ŒμŠ€ λ‚­λΉ„λ₯Ό μ΅œμ†Œν™”ν•©λ‹ˆλ‹€.

Core Features & Use Cases

  • μ—”λ“œν¬μΈνŠΈ λΆ„μ„μ—μ„œλΆ€ν„° DTO λ³€ν™˜, 지속 계측 생성, μ• ν”Œλ¦¬μΌ€μ΄μ…˜ 계측 ꡬ성, 컨트둀러 생성에 이λ₯΄λŠ” 6단계 μ›Œν¬ν”Œλ‘œμš°λ₯Ό 순차적으둜 μ‹€ν–‰ν•©λ‹ˆλ‹€.
  • λͺ¨λ“ˆ κ°„ 경계(Admin, Web λ“±)μ—μ„œ μž¬μ‚¬μš© κ°€λŠ₯ν•œ λ§ˆμ΄κ·Έλ ˆμ΄μ…˜ μ»΄ν¬λ„ŒνŠΈλ₯Ό μƒμ„±ν•˜κ³ , 각 λ‹¨κ³„μ˜ μ‚°μΆœλ¬Όμ„ λ‹€μŒ λ‹¨κ³„λ‘œ μ•ˆμ „ν•˜κ²Œ μ „λ‹¬ν•©λ‹ˆλ‹€.
  • μ‹€νŒ¨ μ‹œ μžλ™ 재개 포인트 μ§€μ •(--step μ˜΅μ…˜) 및 λͺ…ν™•ν•œ 둜그/λ³΄κ³ μ„œλ₯Ό μ œκ³΅ν•©λ‹ˆλ‹€.

Quick Start

Legacy migrate μ›Œν¬ν”Œλ‘œμš°λ₯Ό μ‹œμž‘ν•˜λ €λ©΄ λŒ€μƒ λͺ¨λ“ˆκ³Ό ν•„μš”ν•œ μ‹œμž‘ 단계 μ˜΅μ…˜μ„ ν¬ν•¨ν•˜μ—¬ λͺ…령을 μ‹€ν–‰ν•©λ‹ˆλ‹€.

Frequently Asked Questions about legacy-migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate legacy API migration to a modern architecture?β–Ό

Automating legacy API migration involves a six-step sequential workflow that analyzes endpoints, generates DTOs, creates persistence layers, configures application services, and generates controllers to move legacy APIs to a modern modular architecture.

What is the best way to migrate multi-module legacy services involving endpoints and DTOs?β–Ό

The best way to migrate multi-module legacy services is using an automated workflow that sequentially processes endpoints, DTOs, persistence, service, and controller generation while maintaining clear boundaries across Admin and Web modules.

Can I resume a legacy API migration workflow from a specific step if it fails?β–Ό

Yes, you can resume a failed legacy API migration workflow from a specific step by using the --step option to re-enter the sequential workflow at the desired point without restarting the entire process.

Does the automated migration workflow support code generation for persistence and service layers?β–Ό

Yes, the automated migration workflow supports code generation for persistence and service layers, systematically creating DTOs, persistence components, application service configurations, and controllers during the sequential six-step process.

How are migration errors handled when moving legacy APIs to a new architecture?β–Ό

Migration errors are handled through comprehensive error reporting and clear logs, allowing users to safely pass artifacts between steps and automatically resume the workflow from the exact failure point using the step re-entry option.