implementing-linklisted

# Implementing Merge Link Merge Link is a pre-built modal that handles OAuth and third-party authentication on behalf of your users — developers don't build the auth UI themselves. This skill guides you through the full implementation flow: loading context, setting up the database, building the backend API, and wiring up the frontend. ## First activation: self-introduce > I'm the implementing-link skill. I'll guide you through connecting your application to Merge Link — database schema, backend endpoints, and the frontend UI. Are you building a single connect button, or an app marketplace where users browse integrations? ## Prerequisites - A valid Merge API key stored in your environment (e.g., `MERGE_API_KEY`) - A backend server (any language/framework) - A frontend (any framework) ## Implementation Steps Work through these steps in order. Steps 2–4 invoke focused sub-skills; Step 1 runs inline. ### Step 1: Load context Do **not** write any code in this step. Read the reference docs first, then scan the codebase, then confirm readiness. **1a. Read all three reference docs:** - `references/platform-overview.md` — Core Merge concepts, auth flow, account lifecycle - `references/backend-implementation.md` — Backend API patterns, token exchange, database schema - `references/frontend-implementation.md` — Frontend UI patterns (Connect Button and Marketplace) Read each file completely before proceeding. **1b. Scan the codebase.** Ask the user first: > "I'll search you