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

legacy-service

Generate application-layer scaffolds from legacy persistence layers.

Updated Aug 27, 2026
Search Tags:#architecture#persistence#generate#code-generation#application-layer#legacy-query
One-click install
npx skills add https://github.com/ryu-qqq/conventionHub --skill legacy-service
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: legacy-service
Source: https://github.com/ryu-qqq/conventionHub/tree/main/.claude/skills/legacy-service
Command: npx skills add https://github.com/ryu-qqq/conventionHub --skill legacy-service

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy systems often leave behind a messy persistence layer that is hard to evolve; this Skill generates a clean Application Layer scaffold (port, service, manager, assembler) to enable modern, testable domain boundaries.

Core Features & Use Cases

  • Generates a complete application-layer module from a legacy persistence layer produced by /legacy-query.
  • Produces a consistent file structure under application/src/main/java/.../legacy/{web|admin}/{domain} for UseCase, Port, Service, Manager, and Assembler.
  • Use Case: teams can migrate legacy domain models into a structured architecture with minimal manual wiring.

Quick Start

Invoke the legacy-service generator for your target domain to scaffold the complete application layer from the /legacy-query persistence layer.

Frequently Asked Questions about legacy-service

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

FAQPage Schema
How do I generate a clean application layer from a legacy persistence layer?▼

Generating a clean application layer from a legacy persistence layer requires scaffolding structured domain modules. This skill automates creating UseCase, Port, Service, Manager, and Assembler components to establish testable domain boundaries for web and admin prefixes.

What is the best way to structure legacy domain modules for web and admin prefixes?▼

Structuring legacy domain modules involves organizing files under application/src/main/java/.../legacy/{web|admin}/{domain}/. This skill enforces a consistent file layout and class naming conventions like Legacy{Prefix}{Domain} to maintain architectural boundaries across your codebase.

Can I scaffold an application layer without a generated legacy persistence layer?▼

Scaffolding an application layer without a generated legacy persistence layer is not supported. This skill specifically targets projects that already generated their persistence layer via the /legacy-query command and require structured domain modules for migration.

When do I need to generate an application layer scaffold for legacy code?▼

Generating an application layer scaffold for legacy code is needed when migrating messy persistence systems into modern, testable domain boundaries. It applies when your project requires structured domain modules with prescribed component layouts for web and admin prefixes.

What classes are generated when scaffolding a legacy application layer?▼

Scaffolding a legacy application layer generates UseCase, Port, Service, Manager, and Assembler classes. These components establish clean domain boundaries by enforcing consistent class naming and file structure under the legacy directory path.

Related Skills

Explore More Software Engineering Skills→
spacholski1225spacholski1225
2

Code Archaeology

Trace data flow and Git history to explain legacy code structure.

Community
Basic
richardnpaulrichardnpaul

hexagonal-architecture

Enforce hexagonal boundaries with explicit ports and adapters across TypeScript, Java, Kotlin, and Go.

Community
Advanced
jcuervojcuervo

rails-controllers

Automate Rails 8.1 request handling with routing, controllers, and error mapping.

Community
Advanced
geoffjaygeoffjay
8

rust-ui-architecture

Guide Rust GPUI application architecture with a four-layer UI, Application, Service, and Domain structure.

Community
Intermediate