migrate-to-multi-artifact

Port existing projects into multi-artifact workspaces with migration templates and verification scripts.

Updated Aug 30, 2025
One-click install
npx skills add https://github.com/Pixoraft/YuvaLab --skill migrate-to-multi-artifact
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-multi-artifact
Source: https://github.com/Pixoraft/YuvaLab/tree/main/.local/secondary_skills/migrate-to-multi-artifact
Command: npx skills add https://github.com/Pixoraft/YuvaLab --skill migrate-to-multi-artifact

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Port an existing project into a multi-artifact workspace so it can host multiple artifacts (web, mobile, slides) alongside the original app.

Core Features & Use Cases

  • Provides canonical port rubrics and task templates for migrating frontend and backend into a multi-artifact structure.
  • Generates follow-up task plans for building new artifacts and maintains references to migration steps and safety checks.
  • Offers verification tooling to ensure assets, copies, and imports are aligned with the original app.

Quick Start

Start a migration by proposing the port task for the current project and then create a follow-up task to build the new artifacts.

Frequently Asked Questions about migrate-to-multi-artifact

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

FAQPage Schema
How do I port an existing project to a multi-artifact workspace?

To port an existing project to a multi-artifact workspace, you propose a migration task to restructure the codebase, enabling it to host multiple artifacts like web, mobile, and slides alongside the original application.

What is a multi-artifact workspace migration?

A multi-artifact workspace migration transforms a single-artifact project structure into one that supports multiple artifacts, utilizing canonical port rubrics and task orchestration to copy frontend and backend assets accurately.

Can I generate follow-up task plans for building new artifacts after the port?

Yes, you can generate follow-up task plans for building new artifacts. The migration process creates plan templates under the .local/tasks directory to orchestrate subsequent development steps safely.

Does the migration process provide verification tooling for copied assets?

The migration process provides reference scripts and verification tooling to ensure that copied frontend and backend assets, along with updated imports, remain perfectly aligned with the original application.

Do I need frontfront-defined metadata to migrate my codebase structure?

Yes, you need frontmatter-defined metadata to migrate your codebase structure. The migration relies on this metadata to properly orchestrate task plans, port rubrics, and asset copying.