migrate-backend

Convert external API route definitions into standardized Express backend domain structures.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/dain-agency/mood-tracker --skill migrate-backend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-backend
Source: https://github.com/dain-agency/mood-tracker/tree/main/.claude/skills/migrate-backend
Command: npx skills add https://github.com/dain-agency/mood-tracker --skill migrate-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually converting external API routes into a structured, consistent Express backend domain with separate routes, controllers, services, and types is time-consuming, error-prone, and leads to inconsistent codebases across development teams.

Core Features & Use Cases

  • Standardized Domain Scaffolding: Automatically generates the complete file structure for an Express domain, including dedicated routes, controllers, services, and type definition files.
  • Enforced Architecture Standards: Imposes consistent middleware chains, Zod-based input validation, tenant-scoped database access, and domain-specific error handling for all endpoints.
  • Use Case: For example, if you are migrating a set of external payment API routes to your internal Express backend, use this skill to scaffold the entire payment domain structure that aligns with your existing codebase conventions, reducing development time and eliminating manual setup errors.

Quick Start

Use the migrate-backend skill to convert your external payment API routes into a structured Express domain at apps/api/src/domains/payment/.

Frequently Asked Questions about migrate-backend

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

FAQPage Schema
How do I migrate external API routes to a structured Express backend?

Scaffolding an Express backend domain converts external API routes into a standardized structure with dedicated routes, controllers, services, and type definition files. It enforces consistent middleware chains and Zod-based input validation to eliminate manual setup errors.

How do I scaffold an Express domain module with Zod validation?

Scaffolding an Express domain module with Zod validation automatically generates the complete file structure for routes, controllers, services, and types. It enforces middleware chains, tenant-scoped database access patterns, and domain-specific error handling for production backend architecture requirements.

What is the best way to standardize legacy API routes in Node.js?

Standardizing legacy API routes in Node.js is achieved by converting them into a standardized Express backend domain structure. This process applies consistent middleware chains, Zod-based input validation, and tenant-scoped database access patterns to maintain codebase consistency across development teams.

Can I use this API migration approach for tenant-scoped databases?

Yes, this API migration approach supports tenant-scoped databases by enforcing tenant-scoped database access patterns within the generated Express backend domain structure. It ensures all endpoints adhere to your production backend architecture requirements during the API migration process.

What are the limitations of automated Express domain scaffolding?

Automated Express domain scaffolding is limited to generating structures for Express backend domains using TypeScript and Zod. It specifically enforces middleware chains and domain-specific error handling, meaning it may not apply to non-Express frameworks or alternative validation libraries.