migration-guide

Classify Mercur 1.x projects and guide migration to Mercur 2.0.

Updated Apr 3, 2026

Search Tags:#workflow #documentation #migration #classification #mercur #mercur-1.x-to-2.0

Ready to run

npx skills add https://github.com/OZVE/cuarta-avenida --skill migration-guide-ozve

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migration-guide
Source: https://github.com/OZVE/cuarta-avenida/tree/main/.claude/skills/migration-guide
Command: npx skills add https://github.com/OZVE/cuarta-avenida --skill migration-guide-ozve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plan and execute migration from Mercur 1.x to 2.0 by classifying project difficulty, reading relevant migration docs, and following stop conditions.

Core Features & Use Cases

Classification of project difficulty (starter, light-custom, heavy-custom)
Guided reading of migration documentation and decision trees
Step-by-step migration workflow with checkpoints and verification

Quick Start

Provide the path to your Mercur 1.x project to begin the migration assessment.

Frequently Asked Questions about migration-guide

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

FAQPage Schema

How do I execute a Mercur 1.x to 2.0 migration?▼

Mercur 1.x to 2.0 migration is guided by classifying project difficulty, reading relevant migration documentation, and following a structured workflow with checkpoints and stop conditions.

How does the Mercur migration classification process work?▼

The Mercur migration classification process assesses your 1.x project to categorize it as starter, light-custom, or heavy-custom, determining complexity to select an appropriate migration plan.

What is the best way to plan a Mercur 2.0 upgrade for heavily customized projects?▼

The best way to plan a Mercur 2.0 upgrade for heavily customized projects is to classify them as heavy-custom and follow the decision-tree workflow to outline concrete porting steps for code, dashboards, and configurations.

What do I need to start migrating my Mercur 1.x project to 2.0?▼

To start migrating your Mercur 1.x project to 2.0, you need to provide the path to your existing Mercur 1.x project so the assessment can begin evaluating complexity and porting requirements.

What concrete steps are involved in porting Mercur code and dashboards?▼

Porting Mercur code and dashboards involves following a checkpoint-driven workflow that outlines concrete porting steps, verifies progress, and applies stop conditions based on the selected migration plan.