migrate-lovable

Convert SSR-heavy Lovable/v0 apps into client-side Domo apps.

19|13|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill migrate-lovable
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-lovable
Source: https://github.com/stahura/domo-ai-vibe-rules/tree/main/skills/custom-apps/migrate-lovable
Command: npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill migrate-lovable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert SSR-heavy Lovable/v0 apps into client-side Domo apps, enabling browser-based execution and easier deployment.

Core Features & Use Cases

  • Migration guidance for Lovable/v0 apps to Domo client-side architecture.
  • Codebase mapping: provides reference structure and patterns to replace server routes with Domo APIs.
  • Use Case: When migrating a dashboard or app that relies on server-side rendering, this guide helps you reframe data fetching and routing for a fully client-side Domo app.

Quick Start

Start by scaffolding a Domo project and comparing it to your Lovable app to plan the conversion.

Frequently Asked Questions about migrate-lovable

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

FAQPage Schema
How do I migrate a Lovable app to a client-side Domo architecture?

To migrate a Lovable app to a client-side Domo architecture, remove server-side rendering and replace API endpoints with Domo APIs. This process involves applying conversion patterns to reframe server routes and data fetching for entirely browser-based execution.

Can I convert an SSR React app from v0 to run entirely in the browser?

Yes, you can convert an SSR React app from v0 to run in the browser by removing server rendering dependencies. The migration reframes server-side data fetching and replaces backend endpoints with Domo client-side APIs.

What is the best way to replace server routes with Domo APIs during migration?

The best way to replace server routes with Domo APIs is by applying specific conversion patterns that map your existing codebase structure to a pure client-side build, ensuring all data fetching executes within the browser.

Do I need to remove server-side rendering for a Lovable to Domo migration?

Yes, you need to remove server-side rendering when migrating Lovable apps to Domo. A pure client-side build requires eliminating server routes and server-side data fetching so the application runs entirely in the browser using Domo APIs.

What artifacts are generated when converting a Lovable app to Domo?

Converting a Lovable app to Domo generates a manifest and a thumbnail required for publishing. These artifacts are produced after specifying requirements for a pure client-side build and applying the endpoint replacement patterns.

When should I not use a client-side migration approach for my React app?

You should not use a client-side migration approach if your React app heavily depends on server-side execution for secure data processing or backend routing. The migration requires replacing all server endpoints with Domo APIs for browser-based deployment.