skills.rest
ryu-qqq
ryu-qqqCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

legacy-convert

Convert legacy-flow analysis results into record-based request and response DTOs.

Updated Aug 27, 2026
Search Tags:#validation#legacy#dto#mapping#code-generation#record#api-migration
One-click install
npx skills add https://github.com/ryu-qqq/conventionHub --skill legacy-convert
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: legacy-convert
Source: https://github.com/ryu-qqq/conventionHub/tree/main/.claude/skills/legacy-convert
Command: npx skills add https://github.com/ryu-qqq/conventionHub --skill legacy-convert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy-flow analysis results are scattered and incompatible with modern API conventions, slowing migration and increasing error risk.

Core Features & Use Cases

  • Convert legacy-flow docs into record-based Request/Response DTOs suitable for new conventions.
  • Generate Admin and Web API DTOs automatically from claudedocs legacy-flow markdown.
  • Example: migrated BrandController and ProductController DTOs without manual rewriting.

Quick Start

Run the conversion with the target admin controller and method to produce DTO records.

Frequently Asked Questions about legacy-convert

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

FAQPage Schema
How do I convert legacy API flows into modern record-based DTOs?▼

To convert legacy API flows into record-based DTOs, this Skill transforms documented legacy-flow analysis results into new Request and Response DTO records. It automatically generates appropriate validation annotations and mapping metadata for seamless API integration.

What is the best way to generate validation annotations for migrated API DTOs?▼

Generating validation annotations for migrated API DTOs is handled automatically during the legacy-flow conversion process. The Skill maps legacy analysis data to modern record-based structures, embedding the required validation rules directly into the generated DTO code.

Can I generate both Admin and Web API DTOs from legacy-flow markdown?▼

Yes, you can generate Admin and Web API DTOs from claudedocs legacy-flow markdown. The Skill supports both API contexts, producing record-based Request and Response DTOs tailored to each specific controller environment.

How to automate DTO generation for legacy controllers without manual rewriting?▼

Automating DTO generation for legacy controllers requires running the conversion with the target admin controller and method. The Skill then produces record-based DTOs automatically, eliminating the need for manual rewriting of legacy analysis results.

Does this legacy DTO conversion handle mapping metadata for API integration?▼

Yes, legacy DTO conversion handles mapping metadata for API integration. Alongside generating record-based Request and Response structures, the Skill produces mapping metadata designed to support seamless integration with modern API conventions.

When do I need record-based DTOs for API migration instead of manual classes?▼

You need record-based DTOs for API migration when your legacy-flow analysis results are scattered and incompatible with modern API conventions. Using automated generation reduces error risk and accelerates the migration process compared to manual class rewriting.

Related Skills

Explore More Software Engineering Skills→
CANTAGESTUDIOCANTAGESTUDIO
3

ux-sequence-diagram

Visualize user-system interaction sequences and API call flows as ASCII diagrams.

Community
Intermediate
SergeuMatyasovSergeuMatyasov

controllers

Enforce a unified ASP.NET Core controller standard for API contracts, routes, DTOs, and OpenAPI.

Community
Advanced
djankiesdjankies

validating-external-data

Validate external data against Zod schemas for runtime type safety.

Community
Advanced
onesmartguyonesmartguy
2

dotnet-minimal-api-templates

Generate ASP.NET Core Minimal API templates with layered structure and CQRS.

Community
Intermediate