migrate-lovable
Migrating Lovable to Domo
Converting Generated Apps (Lovable/v0) to Domo
Many developers use AI tools like Lovable, v0, or similar LLM-based generators to create app prototypes. However, these tools typically generate apps with server-side rendering (SSR) that are incompatible with Domo's client-side-only architecture.
The Conversion Challenge
Generated apps often include:
- Server-side rendering (Next.js, Remix, SvelteKit, Nuxt)
- API routes (
pages/api/orapp/api/directories) - Server-side data fetching (
getServerSideProps, loaders, etc.) - Framework-specific routing (Next.js App Router, Remix routes)
Domo apps must be:
- Pure client-side React - No server rendering
- Static file-based - Domo serves static files only
- Domo API integration - Use
domo.get(),Query,AppDBClient, etc. instead of backend endpoints
More from stahura/domo-ai-vibe-rules
domo-js
Use ryuu.js (domo.js) APIs for env, events, navigation, and data calls.
59appdb
Toolkit-first AppDB document CRUD, query operators, and collection wiring.
57html-deck
Build a professional HTML slide deck from source content and convert it to a pixel-perfect PDF. Covers slide architecture, layout patterns, print-safe CSS, Puppeteer PDF conversion, and quality verification. Use when creating presentation decks, converting documents to slide format, or generating PDF decks from HTML.
57data-api
High-level entry skill for Domo data access. Routes detailed query work to dataset-query.
56jsapi-filters
Apply runtime filters to embedded Domo dashboards/cards from the host page via the JS API (MessagePort). Covers dynamic filtering, drill events, filter change listeners, iframe resize, pfilter URL params, overrideFilters, and App Studio appData. Use for any client-side Domo embed interaction. Not for server-side programmatic filters (use programmatic-filters).
56ai-service-layer
Toolkit-first AIClient patterns for generation, text-to-sql, and response parsing.
56