Integrate Into Your App
Copy the required public surface while preserving the target application's behavior.
Before You Start
Use a private branch of the target app; confirm its baseline builds. Inspect both repositories' dependencies, routes, aliases, global styles and assets. There is no one-click theme or adapter CLI.
Integrate the Public Surface
- Trace marketing-route imports and copy necessary components, content and assets.
- Reconcile dependencies, aliases, fonts and CSS tokens.
- Resolve route, public-file and metadata collisions intentionally.
- Connect CTAs to real services; preserve existing auth and payment behavior.
- Keep the signed-in
/appshell separate. See Web layout or Cloudflare layout.
Check Your Result
The target app builds; pages and assets load; login, protected routes and payments retain their behavior. Check locale URLs and CSS collisions. Required copy scope depends on the template and target app.
Common Problems
Missing imports: reconcile aliases and dependencies. Broken dashboard: scope marketing styles rather than replacing global CSS. Duplicate routes: rename or merge intentionally.
Next Step
TanStack Start / Flare
For MuseMVP Flare, adapt Next.js routing, image/link APIs and server-component assumptions to TanStack Start. Preserve the Flare authentication and payment boundaries. See Flare components and themes.