legacy-controller

Generate legacy controllers and ApiMappers for multi-domain migration workflows.

Updated Aug 23, 2026

Search Tags:#rest #migration #codegen #controller #legacy #apimapper

Ready to run

npx skills add https://github.com/ryu-qqq/conventionHub --skill legacy-controller

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: legacy-controller
Source: https://github.com/ryu-qqq/conventionHub/tree/main/.claude/skills/legacy-controller
Command: npx skills add https://github.com/ryu-qqq/conventionHub --skill legacy-controller

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

이 스킬은 레거시 마이그레이션 사이클에서 컨트롤러와 ApiMapper를 자동으로 생성하여 수동 구현의 시간과 오류를 줄입니다.

Core Features & Use Cases

Controller 생성 자동화: 도메인에 대응하는 REST 컨트롤러를 자동으로 구성합니다.
ApiMapper 생성을 통한 변환: 요청/응답 구조를 도메인 객체로 매핑하는 매퍼를 자동으로 생성합니다.
다중 도메인 지원: 여러 엔드포인트와 버전에 대해 일관된 마이그레이션 흐름을 제공합니다.
마이그레이션 종합 시나리오: 기존 단계 출력물과 연동하여 엔드포인트 전체 흐름을 완성합니다.

Quick Start

타겟 도메인과 동작을 지정하여 레거시 컨트롤러와 ApiMapper 생성을 시작합니다.

Frequently Asked Questions about legacy-controller

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

FAQPage Schema

How do I automate REST controller generation for legacy API migration?▼

You can automate REST controller generation for legacy migration by using a code generation skill that scaffolds domain-specific controllers and coordinates them with query layers, eliminating manual implementation errors across multiple endpoint versions.

Why do I need an ApiMapper when migrating legacy REST endpoints?▼

An ApiMapper is needed when migrating legacy REST endpoints because it automatically transforms and maps request and response structures into domain objects. This ensures consistent data transformation across various endpoint versions during the migration workflow.

Can I generate controllers for multiple domains and different API versions simultaneously?▼

Yes, you can generate controllers for multiple domains and different API versions simultaneously. The codegen process supports multi-domain legacy migrations, providing a consistent migration flow across various endpoint versions within the established prerequisites.

What's the best way to scaffold end-to-end legacy controllers without manual coding?▼

The best way to scaffold end-to-end legacy controllers without manual coding is through automated codegen that integrates with existing legacy services and query layers. This finalizes the migration workflow by coordinating controller and mapper creation directly from target domain specifications.

Do I need existing migration prerequisites before generating legacy controllers?▼

Yes, you need existing migration prerequisites before generating legacy controllers. The codegen process coordinates controller and ApiMapper creation within the established migration workflow, relying on prior step outputs to finalize the end-to-end scaffolding and domain-specific mapping.

What are the limitations of automating legacy controller and ApiMapper codegen?▼

The limitation of automating legacy controller and ApiMapper codegen is its dependency on established migration prerequisites and existing query layers. It requires prior step outputs to function, meaning it cannot independently scaffold domains outside the established migration workflow.