Current view

Duplicate Finder

Sandpaper Engine

Duplicate Finder

Deterministic mock duplicate and conflict detection for AI-built apps. This version uses curated groups only, with scoped resolution prompts.

Mock Data

Duplicate groups

4

Deterministic mock conflicts

Critical conflicts

1

Highest-risk consolidation work

Files to merge

7

Useful logic candidates

Files to archive

9

After verification only

Filters

Filter mock duplicate/conflict groups by severity or type.

Duplicate/conflict groups

4 groups shown.

CriticalDuplicate Supabase clients

Duplicate Supabase clients

Files

lib/supabase.tslib/supabaseClient.tslib/supabase/client.tsutils/supabase.ts

Canonical recommendation

Use lib/supabase/client.ts as the browser client and reserve server-only clients for explicit server modules.

Conflict risk

Multiple Supabase client factories can mix anon and service-role behavior, bypass RLS expectations, and create inconsistent session handling.

Recommended action

Inspect all clients, keep the safest canonical client, merge any useful typed helpers, and archive redundant files after build passes.

Files to merge

lib/supabase.ts

lib/supabaseClient.ts

utils/supabase.ts

Files to remove/archive

lib/supabase.ts

lib/supabaseClient.ts

utils/supabase.ts

HighDuplicate chatbot routes

Duplicate chatbot routes

Files

app/api/chat/route.tsapp/api/ai/chat/route.tsapp/api/chatbot/route.ts

Canonical recommendation

Use app/api/ai/chat/route.ts as the canonical AI chat route because it matches the product AI namespace.

Conflict risk

Different chat routes can apply different auth, rate-limit, prompt, and usage-tracking behavior.

Recommended action

Merge useful validation and provider-call logic into the canonical route, then update UI calls before archiving duplicates.

Files to merge

app/api/chat/route.ts

app/api/chatbot/route.ts

Files to remove/archive

app/api/chat/route.ts

app/api/chatbot/route.ts

HighConflicting package managers

Conflicting package managers

Files

package-lock.jsonyarn.lockpnpm-lock.yaml

Canonical recommendation

Use package-lock.json as canonical because the current project was initialized with npm.

Conflict risk

Multiple lockfiles can cause different dependency trees between local development, CI, and Vercel builds.

Recommended action

Confirm npm is the intended package manager, then archive non-canonical lockfiles only after install/build succeeds.

Files to merge

No merge candidates listed

Files to remove/archive

yarn.lock

pnpm-lock.yaml

MediumDuplicate pricing components

Duplicate pricing components

Files

components/Pricing.tsxcomponents/PricingTable.tsxapp/pricing/PricingClient.tsx

Canonical recommendation

Use app/pricing/PricingClient.tsx as the route-owned pricing surface and extract shared presentation only if needed.

Conflict risk

Pricing copy, plan limits, and CTA behavior can drift across duplicate generated components.

Recommended action

Compare pricing details, merge the current plan copy into the canonical component, and update imports where consolidation is required.

Files to merge

components/Pricing.tsx

components/PricingTable.tsx

Files to remove/archive

components/Pricing.tsx

components/PricingTable.tsx