1. Remove Mini App host/runtime coupling.
2. Decide whether any Farcaster-facing functionality should remain.
3. If something remains, keep it isolated from the main app and avoid introducing new vendor dependencies by default.

1. Discovery — Quick scan + quiz to choose a path
2. Analysis — Detailed read-only analysis scoped to the chosen path
3. Conversion — Remove Mini App SDK patterns and isolate any intentionally preserved Farcaster surface
4. Cleanup — Remove dead code, env vars, and dependencies
5. Verification — Type check, build, and summarize

Path B

• Prefer read-only Farcaster data.
• Avoid preserving Mini App host/runtime behavior unless the user explicitly asks for it.
• Keep any preserved Farcaster logic out of the main app shell, shared providers, and primary auth flow.

1. Detect framework from

   package.json

   (

   next

   ,

   vite

   ,

   react-scripts

   ,

   @remix-run/*

   )
2. Count Farcaster packages in

   dependencies

   and

   devDependencies

3. Grep source files (

   .ts

   ,

   .tsx

   ,

   .js

   ,

   .jsx

   ) for:

   • sdk.actions.*

     calls (count total)

   • sdk.quickAuth

     usage (yes/no)

   • sdk.context

     usage (yes/no)

   • .well-known/farcaster.json

     (yes/no)

   • farcasterMiniApp

     /

     miniAppConnector

     connector (yes/no)
   • Total files with any

     @farcaster/

     import

   • @neynar/

     imports or

     api.neynar.com

     fetch calls (yes/no)
4. Identify the blast radius:
   • Are Farcaster references spread across the main app shell?
   • Are they already mostly confined to a route like

     app/farcaster/

     ,

     pages/farcaster/

     , or a small set of components?
   • Are there obvious host-only features such as haptics, notifications,

     openMiniApp

     , or

     sdk.context.client

     ?

Based on my scan, your project has [X] files using the Farcaster SDK with [summary of what is used].

Which outcome do you want?

• (a) Regular app everywhere — remove Farcaster-specific behavior and just keep a normal Base/web app
• (b) Regular app first, plus a separate Farcaster area — keep the main app clean, but preserve a small isolated route/page if really needed

How deeply is the Mini App SDK used today?

• (a) Minimal — mostly

  sdk.actions.ready()

  and a few helpers
• (b) Moderate — some

  context

  ,

  openUrl

  , profile links, or conditional

  isInMiniApp

  logic
• (c) Heavy — auth, wallet connector, notifications, compose flows, or host-specific behavior

What is the smallest Farcaster feature set you actually need to preserve?

• (a) Read-only only — profile or cast display, links out to Farcaster profiles, maybe a small social page
• (b) Some Farcaster-specific interactions — there is a separate page/path that still needs more than read-only behavior
• (c) Not sure — analyze what is isolated already and recommend the smallest keep-surface possible

Does the project already have an isolated Farcaster-only route/page or integration that you want to keep as-is if possible?

• (a) Yes — preserve only that isolated surface
• (b) No — prefer removing it unless there is a very strong reason to keep it

After conversion, what should the main app use for authentication?

• (a) SIWE — wallet-based auth for the regular app
• (b) Existing non-Farcaster auth — keep whatever normal web auth already exists
• (c) No auth — remove auth entirely

Q1 = regular app everywhere

Q1 = regular app first, plus separate Farcaster area

• If the user chose

  Path B

  , prefer read-only preservation unless they explicitly require something else.
• If the scan shows heavy host/runtime coupling but the user wants

  Path A

  , warn them that some features will be deleted rather than recreated.
• If the project already uses Neynar, only keep it if it remains inside the isolated Farcaster surface. Do not expand it into the main app.

Based on your answers, I'll use Path [X]: [Name]. This will [one-sentence description]. I'll now do a detailed analysis of your project.

• fully remove Farcaster features
• preserve only a read-only isolated surface
• quarantine any unavoidable Farcaster-specific logic to a dedicated route/page

package.json

• next

  → Next.js

• vite

  → Vite

• react-scripts

  → Create React App

• @remix-run/*

  → Remix

• @farcaster/miniapp-sdk

  ,

  @farcaster/miniapp-core

  ,

  @farcaster/miniapp-wagmi-connector

• @farcaster/frame-sdk

  ,

  @farcaster/frame-wagmi-connector

• @farcaster/quick-auth

  ,

  @farcaster/auth-kit

• @neynar/*

  (compatibility only; do not assume it stays)

• coinbaseWallet

  connector in wagmi config
• SIWE /

  siwe

  package usage

• connectkit

  ,

  rainbowkit

  , or

  @coinbase/onchainkit

• Existing wallet connection UI

• Root providers or app shell
• Shared hooks or auth middleware
• One-off components
• Dedicated routes/pages like

  app/farcaster/*

• Server routes used only by Farcaster functionality

• remove
• stub
• move behind isolated route/page
• keep only as read-only

• File: [path]
• Current connector: [farcasterMiniApp / miniAppConnector / farcasterFrame / none]
• Other connectors: [list]
• Action: [replace with coinbaseWallet / leave existing wallet setup / remove only]

• File: [path]
• Pattern: [simple / complex]
• Consumers: [files importing from this]
• Action: [stub / remove / isolate]

• Manifest route: [path or N/A]
• Meta tags: [file or N/A]

**Path A additionally includes:**

• Action: remove Farcaster-specific UI and flows from the main app entirely

• Quick Auth used: [yes/no, file]
• Action: replace with SIWE / keep existing non-Farcaster auth / remove

• Package or files: [list or N/A]
• Action: remove entirely unless the user later re-scopes to Path B

• Action: convert the main app into a normal web app first

• Route/page to keep: [path or proposed path]
• Scope: [read-only / mixed / host-specific]
• Recommended target scope: [prefer read-only / quarantine existing behavior / remove]

• Quick Auth used: [yes/no, file]
• Main app action: replace with SIWE / keep existing non-Farcaster auth / remove
• Isolated Farcaster surface action: [remove auth coupling / preserve existing isolated flow only if explicitly requested]

• Package or files: [list or N/A]
• Action: [remove / keep only inside isolated surface]

• Remove from main app: [FC_, FARCASTER_, etc.]
• Keep only if isolated surface truly still needs them: [NEYNAR_API_KEY, etc. or N/A]

**All paths end with:**

• FID used as database primary key
• Farcaster colors in tailwind config

• isInMiniApp

  branches with unique else logic
• Components only meaningful inside Farcaster
• Farcaster code mixed into shared providers or root layout

Ask:

> Does this analysis look correct? Ready to proceed with conversion?

**STOP and wait for user confirmation before Phase 2.**

---

lib/wagmi.ts

config/wagmi.ts

providers/wagmi-provider.tsx

1. Remove import of

   farcasterMiniApp

   or

   miniAppConnector

   from

   @farcaster/miniapp-wagmi-connector

2. Remove the

   farcasterMiniApp()

   /

   miniAppConnector()

   call from the

   connectors

   array
3. If no wallet connector remains, add:
   typescript

   import { coinbaseWallet } from "wagmi/connectors";
   
   coinbaseWallet({ appName: "<app name>" })

4. If

   coinbaseWallet

   already exists, leave it as-is
5. Clean up empty lines and stale imports

'use client'

import React, { createContext, useContext, useMemo } from "react";

interface MiniAppContextType {
  context: undefined;
  ready: boolean;
  isInMiniApp: boolean;
}

const MiniAppContext = createContext<MiniAppContextType | undefined>(undefined);

export function useMiniAppContext() {
  const context = useContext(MiniAppContext);
  if (context === undefined) {
    throw new Error("useMiniAppContext must be used within a MiniAppProvider");
  }
  return context;
}

export default function MiniAppProvider({ children }: { children: React.ReactNode }) {
  const value = useMemo(
    () => ({
      context: undefined,
      ready: true,
      isInMiniApp: false,
    }),
    []
  );

  return <MiniAppContext.Provider value={value}>{children}</MiniAppContext.Provider>;
}

• If many consumers depend on it, stub it first.
• If only a few files use it, remove it and update those imports directly.
• In

  Path B

  , do not let the isolated Farcaster surface keep this provider wired through the root app shell. If needed, make it local to the isolated route only.

• If

  sdk.quickAuth.getToken()

  is used, replace it with SIWE or remove it.
• If a normal non-Farcaster auth system already exists, prefer that over adding new auth.
• Do not introduce new Farcaster or Neynar auth as the default conversion target.

useSignIn.ts

• Remove

  import sdk from "@farcaster/miniapp-sdk"

• Remove

  sdk.quickAuth.getToken()

• Replace with:
  1. Get wallet address from

     useAccount()

     (wagmi)
  2. Create a SIWE message with

     siwe

  3. Sign with

     useSignMessage()

     (wagmi)
  4. Send signature + message to the backend for verification

app/api/auth/sign-in/route.ts

• Remove

  @farcaster/quick-auth

  verification
• Replace with SIWE verification:
  1. Parse the SIWE message
  2. Verify the signature with

     siwe

     or

     viem

  3. Use recovered wallet address as the normal app identity

• Do not auto-change schema
• Add a TODO comment for later migration
• Warn in Phase 4 summary

• If the isolated Farcaster surface already has its own auth or integration flow and the user explicitly wants to keep it, quarantine it there only.
• Do not let that flow remain the default app-wide auth system.

Path B

• sdk.context

  • Remove from the main app
  • For the isolated surface, prefer replacing it with read-only fetched data or explicit route params
  • Remove

    context.location

    ,

    context.client

    , safe area, and other host-derived assumptions unless the user explicitly insists on preserving a host-specific page

• sdk.actions.composeCast(...)

  • Remove from the main app
  • If the user only needs read-only, delete it entirely
  • If they insist on preserving it, keep it isolated behind a dedicated page/path and flag it as a manual follow-up rather than rebuilding it by default

• sdk.actions.openMiniApp(...)

  • Remove from the main app
  • Only keep it in an isolated route if the user explicitly wants a Farcaster-only surface
• notifications / haptics / host buttons
  • Remove from the main app
  • Preserve only if the isolated route truly depends on them and the user has explicitly opted into that complexity

lib/farcaster-readonly.ts

const HUB_URL = "https://hub.farcaster.xyz";

export async function getUserData(fid: number) {
  const res = await fetch(`${HUB_URL}/v1/userDataByFid?fid=${fid}`);
  if (!res.ok) throw new Error(`Hub user data fetch failed: ${res.status}`);
  return res.json();
}

export async function getCastsByFid(fid: number, pageSize = 25) {
  const res = await fetch(`${HUB_URL}/v1/castsByFid?fid=${fid}&pageSize=${pageSize}`);
  if (!res.ok) throw new Error(`Hub casts fetch failed: ${res.status}`);
  return res.json();
}

• Keep these calls inside the isolated route/page only
• Do not thread Farcaster data requirements through the main app shell
• If the project already has a small isolated Neynar-based read-only integration, you may keep it only if removing it would create more churn than it saves
• Do not add new Neynar packages for this by default

.well-known/farcaster.json

• app/.well-known/farcaster.json/route.ts

• public/.well-known/farcaster.json

• api/farcaster-manifest.ts

  or similar helpers

.well-known

• <meta>

  tags with

  property="fc:miniapp*"

  or

  property="fc:frame*"

• Metadata.other

  entries that only exist for Farcaster tags

• generateMetadata

  logic that only produces Mini App metadata

• @farcaster/miniapp-sdk

  ,

  @farcaster/miniapp-wagmi-connector

  ,

  @farcaster/miniapp-core

• @farcaster/frame-sdk

  ,

  @farcaster/frame-wagmi-connector

• @farcaster/quick-auth

  ,

  @farcaster/auth-kit

• @neynar/nodejs-sdk

  ,

  @neynar/react

• any other Neynar packages or helpers

• @neynar/nodejs-sdk

  ,

  @neynar/react

  , and Neynar helpers unless they remain inside the intentionally isolated Farcaster surface

• siwe

  if SIWE auth is introduced and not already present

• Delete

  app/farcaster/

  ,

  pages/farcaster/

  , and Farcaster-only components entirely
• Delete Farcaster-only API routes such as

  /api/farcaster/*

  and

  /api/neynar/*

• Remove any navigation links that point to deleted routes

• Keep the main app route tree clean
• Move preserved Farcaster UI behind one dedicated route/page if it is not already isolated
• Prefer names like

  app/farcaster/

  or

  app/social/

  over spreading Farcaster logic throughout generic shared pages
• Remove any component that has no purpose outside that isolated surface
• Keep any remaining Neynar usage, if any, confined to that isolated route/page and its server helpers only

• @farcaster/miniapp-sdk

  ,

  @farcaster/miniapp-wagmi-connector

  ,

  @farcaster/miniapp-core

• @farcaster/frame-sdk

  ,

  @farcaster/frame-wagmi-connector

• @farcaster/quick-auth

  ,

  @farcaster/auth-kit

• all

  @neynar/*

  packages

• @neynar/*

• siwe

.env*

• NEYNAR_API_KEY

• NEXT_PUBLIC_NEYNAR_CLIENT_ID

• FARCASTER_*

• FC_*

• NEXT_PUBLIC_FC_*

• NEXT_PUBLIC_FARCASTER_*

• FARCASTER_*

• FC_*

• NEXT_PUBLIC_FC_*

• NEXT_PUBLIC_FARCASTER_*

NEYNAR_*

env.ts

env.mjs

• Remove unused imports from modified files
• Remove unused Farcaster types and helper functions
• Remove empty import statements
• Remove dead hooks or API wrappers that only existed for the Mini App SDK

@farcaster
farcasterMiniApp
miniAppConnector
sdk.actions
sdk.quickAuth
sdk.context
fc:miniapp
fc:frame

@neynar
NEYNAR_API_KEY
NEXT_PUBLIC_NEYNAR_CLIENT_ID
api.neynar.com

• verify that remaining

  @neynar

  imports and env vars exist only inside the isolated Farcaster surface and its server helpers

node_modules

• Removed Farcaster Mini App wagmi connector
• Stubbed or removed Mini App provider/context
• Replaced Mini App auth with normal web auth or removed it
• Removed or replaced SDK action calls
• Deleted manifest route
• Removed Farcaster meta tags
• Cleaned up dependencies and env vars

**Path B summary additionally includes:**

• Kept the main app as a normal web app
• Confined remaining Farcaster functionality to a dedicated route/page
• Preferred read-only Farcaster data where possible
• Removed Farcaster host/runtime coupling from shared app infrastructure

**All paths end with:**

• Run

  npm install

• Test wallet connection flow
• If FID migration is needed, migrate from FID-based identity to wallet address
• If Path B preserves a Farcaster-only area, verify it stays isolated from the main app shell

• TypeScript: [pass/fail]
• Build: [pass/fail]
• Remaining Farcaster references: [none / list]

---

• remove it in

  Path A

• keep it only if it remains inside the isolated

  Path B

  surface
• do not add more Neynar usage than already exists unless the user explicitly requests it

• profile links
• read-only profile or cast display
• a dedicated social page

• Validate wallet setup — ensure

  coinbaseWallet

  or the chosen wallet connector is configured correctly
• FID-based identity — requires manual database migration if used as a primary key
• SIWE verification — verify signatures server-side before trusting them
• Preserved isolated surface — do not let a Farcaster-only route/page leak host/runtime assumptions into the main app shell
• Existing Neynar usage — keep API keys server-side only, and only if that isolated surface still depends on them