[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76HMKQFJSNFRS3KWHTNWVDP":3,"skill-same:01M76HMKQFJSNFRS3KWHTNWVDP":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M76HMKQFJSNFRS3KWHTNWVDP","insforge",null,"Use this skill when writing app code with InsForge or @insforge\u002Fsdk: database CRUD, auth, storage uploads\u002Fstorage RLS, functions, OpenRouter AI, realtime, emails, Stripe or Razorpay payments, or pointing S3-compatible tooling (aws CLI, AWS SDKs, rclone, Terraform, boto3) at InsForge Storage. Trigger on requests like add auth, fetch data, upload files, make a bucket public, add checkout, sell subscriptions, or send email. For infrastructure, SQL migrations, CLI commands, or payment provider setup, use insforge-cli instead.","bg-szy\u002FTOP-SKILLS","bg-szy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F106576190?v=4","01M73A4E8KPV67SFXRY8XZGNBX","ShuZhiyong","01M73A4E96MQ294MHM74TZBVQD",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Finsforge\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: insforge\ndescription: >-\n  Use this skill when writing app code with InsForge or @insforge\u002Fsdk: database CRUD, auth, storage uploads\u002Fstorage RLS, functions, OpenRouter AI, realtime, emails, Stripe or Razorpay payments, or pointing S3-compatible tooling (aws CLI, AWS SDKs, rclone, Terraform, boto3) at InsForge Storage. Trigger on requests like add auth, fetch data, upload files, make a bucket public, add checkout, sell subscriptions, or send email. For infrastructure, SQL migrations, CLI commands, or payment provider setup, use insforge-cli instead.\nlicense: Apache-2.0\n---\n\n# InsForge App Integration Skill\n\nThis skill covers **client-side SDK integration** using `@insforge\u002Fsdk`. For backend infrastructure operations (creating tables, inspecting schema, deploying functions, secrets, managing storage buckets, configuring payment provider keys\u002Fcatalog, website deployments, cron job and schedules, logs, etc.), use the **insforge-cli** skill.\n\n## Quick Setup\n\n### 1. Install the SDK\n\n```bash\nnpm install @insforge\u002Fsdk@latest\n```\n\n### 2. Set up environment variables\n\nBefore using the SDK, create a `.env` file (or `.env.local` for Next.js) in your project root with your InsForge URL and anon key.\n\n#### How to get your URL and anon key\n\n1. **Ensure the project is linked.** Check for `.insforge\u002Fproject.json` in the project root.\n   - Generate it with `npx -y @insforge\u002Fcli link` for an existing project or `npx -y @insforge\u002Fcli create` for a new project.\n\n2. **Get the anon key** via the CLI:\n\n   ```bash\n   npx -y @insforge\u002Fcli secrets get ANON_KEY\n   ```\n\n3. **Get the URL** from the `oss_host` field in `.insforge\u002Fproject.json` (e.g., `https:\u002F\u002Fmyapp.us-east.insforge.app`).\n\n4. **Write both values** to the `.env` file using the correct framework prefix (see table below).\n\n> **Important:** Use the anon key for user-scoped SDK clients, including SSR. For privileged server-only app code that needs admin\u002Fservice access, use `createAdminClient({ apiKey })`; the API key is a full-access admin key, equivalent to a service role key on other platforms.\n\nUse the correct environment variable prefix and access pattern for your framework:\n\n| Framework                     | `.env` file  | Variables                                                   | Access Pattern                              |\n| ----------------------------- | ------------ | ----------------------------------------------------------- | ------------------------------------------- |\n| **Next.js**                   | `.env.local` | `NEXT_PUBLIC_INSFORGE_URL`, `NEXT_PUBLIC_INSFORGE_ANON_KEY` | `process.env.NEXT_PUBLIC_*`                 |\n| **Vite** (React, Vue, Svelte) | `.env`       | `VITE_INSFORGE_URL`, `VITE_INSFORGE_ANON_KEY`               | `import.meta.env.VITE_*`                    |\n| **Astro**                     | `.env`       | `PUBLIC_INSFORGE_URL`, `PUBLIC_INSFORGE_ANON_KEY`           | `import.meta.env.PUBLIC_*`                  |\n| **SvelteKit**                 | `.env`       | `PUBLIC_INSFORGE_URL`, `PUBLIC_INSFORGE_ANON_KEY`           | `import { env } from '$env\u002Fdynamic\u002Fpublic'` |\n| **Create React App**          | `.env`       | `REACT_APP_INSFORGE_URL`, `REACT_APP_INSFORGE_ANON_KEY`     | `process.env.REACT_APP_*`                   |\n| **Node.js \u002F Server**          | `.env`       | `INSFORGE_URL`, `INSFORGE_ANON_KEY`                         | `process.env.*`                             |\n\nExample `.env.local` for Next.js:\n\n```bash\nNEXT_PUBLIC_INSFORGE_URL=https:\u002F\u002Fyour-appkey.us-east.insforge.app\nNEXT_PUBLIC_INSFORGE_ANON_KEY=eyJhbGciOiJIUzI1NiIs...\n```\n\n> **Important:** Keep `.env` files local. Add `.env`, `.env.local`, and `.env*.local` to your `.gitignore` and keep `.env.example` for documenting required variables.\n\n### 3. Initialize the client\n\nNext.js:\n\n```javascript\nimport { createClient } from '@insforge\u002Fsdk'\n\nconst insforge = createClient({\n  baseUrl: process.env.NEXT_PUBLIC_INSFORGE_URL,\n  anonKey: process.env.NEXT_PUBLIC_INSFORGE_ANON_KEY\n})\n```\n\nVite:\n\n```javascript\nimport { createClient } from '@insforge\u002Fsdk'\n\nconst insforge = createClient({\n  baseUrl: import.meta.env.VITE_INSFORGE_URL,\n  anonKey: import.meta.env.VITE_INSFORGE_ANON_KEY\n})\n```\n\nAstro:\n\n```javascript\nimport { createClient } from '@insforge\u002Fsdk'\n\nconst insforge = createClient({\n  baseUrl: import.meta.env.PUBLIC_INSFORGE_URL,\n  anonKey: import.meta.env.PUBLIC_INSFORGE_ANON_KEY\n})\n```\n\nFor trusted server-only code that needs project-admin access:\n\n```javascript\nimport { createAdminClient } from \"@insforge\u002Fsdk\";\n\nconst admin = createAdminClient({\n  baseUrl: process.env.INSFORGE_URL,\n  apiKey: process.env.INSFORGE_API_KEY,\n});\n```\n\n## Module Reference\n\n| Module        | Integration Guide                                            |\n| ------------- | ------------------------------------------------------------ |\n| **Database**  | [database\u002Fsdk-integration.md](database\u002Fsdk-integration.md)   |\n| **Auth**      | [auth\u002Fsdk-integration.md](auth\u002Fsdk-integration.md)           |\n| **Storage**   | [storage\u002Fsdk-integration.md](storage\u002Fsdk-integration.md)     |\n| **Functions** | [functions\u002Fsdk-integration.md](functions\u002Fsdk-integration.md) |\n| **AI**        | [ai\u002Foverview.md](ai\u002Foverview.md)                             |\n| **Real-time** | [realtime\u002Fsdk-integration.md](realtime\u002Fsdk-integration.md)   |\n| **Email**     | [email\u002Fsdk-integration.md](email\u002Fsdk-integration.md)         |\n| **Payments: Stripe** | [payments\u002Fstripe.md](payments\u002Fstripe.md)             |\n| **Payments: Razorpay** | [payments\u002Frazorpay.md](payments\u002Frazorpay.md)       |\n\n### What Each Module Covers\n\n| Module        | Content                                                                                                       |\n| ------------- | ------------------------------------------------------------------------------------------------------------- |\n| **Database**  | CRUD operations, filters, pagination, RPC calls                                                               |\n| **Auth**      | Sign up\u002Fin, OAuth, sessions, profiles, password reset                                                         |\n| **Storage**   | Upload, download, delete files; S3-compatible gateway for CI \u002F backup tooling; write RLS policies for buckets |\n| **Functions** | Invoke edge functions                                                                                         |\n| **AI**        | OpenRouter AI calls for chat, images, video, audio, embeddings, and model discovery                           |\n| **Email**     | Send custom transactional HTML emails (welcome, newsletter, notifications)                                    |\n| **Payments: Stripe** | Stripe Checkout Sessions, subscriptions, and Billing Portal redirects                                  |\n| **Payments: Razorpay** | Razorpay Orders, Subscriptions, Checkout.js, and subscription management                               |\n| **Real-time** | Connect, subscribe, publish events, and track presence snapshots plus join\u002Fleave deltas                       |\n\n### Guides\n\n| Guide                                                                                                          | When to Use                                                                                                                                                                                                                                                                                                                                                                                            |\n| -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |\n| [..\u002Finsforge-cli\u002Freferences\u002Fdatabase\u002Faccess-control.md](..\u002Finsforge-cli\u002Freferences\u002Fdatabase\u002Faccess-control.md) | Backend setup for application-table access control — covers RLS, infinite recursion prevention, `SECURITY DEFINER` patterns, performance tips, and common InsForge patterns                                                                                                                                                                                                                            |\n| [storage\u002Fs3-gateway.md](storage\u002Fs3-gateway.md)                                                                 | Fallback path when the consumer is existing S3 tooling (aws CLI, AWS SDKs, rclone, Terraform, boto3) and adopting `@insforge\u002Fsdk` is impractical — covers endpoint\u002Fregion setup, access-key management, path-style addressing, and supported vs. not-supported S3 operations. **Requires InsForge 2.0.9+.** **Prefer the SDK** ([storage\u002Fsdk-integration.md](storage\u002Fsdk-integration.md)) for app code |\n| [storage\u002Fpostgres-rls.md](storage\u002Fpostgres-rls.md)                                                             | Writing RLS policies for `storage.objects` — owner-only, public-read, path-scoped, team-shared, and the `NULL uploaded_by` caveat for mixed REST + S3 buckets                                                                                                                                                                                                                                          |\n| [..\u002Finsforge-cli\u002Freferences\u002Fdatabase\u002Fvector.md](..\u002Finsforge-cli\u002Freferences\u002Fdatabase\u002Fvector.md)                 | Backend setup for semantic search, recommendations, or RAG — covers the `vector` extension, schema\u002Fdimensions, distance operators, HNSW\u002FIVFFlat indexes, and RPC similarity search                                                                                                                                                                                                                     |\n| [ai\u002Fchat-completions.md](ai\u002Fchat-completions.md)                                                               | Text generation, structured answers, and streaming chat through OpenRouter                                                                                                                                                                                                                                                                                                                             |\n| [ai\u002Fimage-generation.md](ai\u002Fimage-generation.md)                                                               | Image generation\u002Fediting through OpenRouter, then durable storage in InsForge Storage                                                                                                                                                                                                                                                                                                                  |\n| [ai\u002Fvideo-generation.md](ai\u002Fvideo-generation.md)                                                               | Async OpenRouter video jobs, status polling, and storing generated media                                                                                                                                                                                                                                                                                                                               |\n| [ai\u002Faudio.md](ai\u002Faudio.md)                                                                                     | Speech-to-text, text-to-speech, and storing audio assets\u002Ftranscripts with InsForge                                                                                                                                                                                                                                                                                                                     |\n| [ai\u002Fembeddings-and-rag.md](ai\u002Fembeddings-and-rag.md)                                                           | Generating embeddings through OpenRouter, storing them in pgvector, and wiring up a basic RAG pipeline                                                                                                                                                                                                                                                                                                 |\n| [ai\u002Fmodels-list.md](ai\u002Fmodels-list.md)                                                                         | Discovering OpenRouter model IDs, modalities, parameters, pricing, and embedding dimensions                                                                                                                                                                                                                                                                                                            |\n| [payments](..\u002Finsforge-cli\u002Freferences\u002Fpayments\u002Foverview.md)                                                    | Configuring Stripe\u002FRazorpay keys, syncing provider catalog, setting up webhooks, and writing payment RLS before app integration                                                                                                                                                                                                                                                                        |\n\n### Building Payments for a New App\n\nFirst choose the provider. There is no generic app payments guide:\n\n- For Stripe Checkout, subscriptions, and Billing Portal, load [payments\u002Fstripe.md](payments\u002Fstripe.md).\n- For Razorpay Orders, Subscriptions, Checkout.js, and cancel\u002Fpause\u002Fresume flows, load [payments\u002Frazorpay.md](payments\u002Frazorpay.md).\n\nBefore writing app code, check provider setup with the **insforge-cli** payments references:\n\n```bash\nnpx -y @insforge\u002Fcli payments stripe status\nnpx -y @insforge\u002Fcli payments razorpay status\n```\n\nIf the chosen provider is unconfigured, ask the developer\u002Fadmin to configure that provider first.\n\n### Real-time Backend Setup\n\nThe real-time SDK is for frontend event handling and messaging. Configure channel patterns, database triggers, and channel\u002Fmessage RLS with the **insforge-cli** skill; see [realtime](..\u002Finsforge-cli\u002Freferences\u002Frealtime.md).\n\n### Backend Configuration\n\nSupported project config knobs are managed via the CLI — use\n`npx -y @insforge\u002Fcli config export\u002Fplan\u002Fapply` for auth redirect URLs,\nverification flags, password policy, auth SMTP settings, storage upload size,\nrealtime\u002Fschedule retention, and cloud deployment subdomain. OAuth providers,\nexternal app setup, storage buckets, functions, secrets, and deployment env vars\nstill use their dedicated dashboard or CLI flows. See the **insforge-cli**\nskill's Configuration section.\n\n### Risky backend changes? Use a branch first\n\nWhen a code change in this skill depends on a **schema migration**, **new RLS policy**, **OAuth provider config change**, or any other backend change that affects prod behavior, create a backend branch first. Branches share `JWT_SECRET` (existing user JWTs keep working) but get a fresh database + EC2 + `API_KEY` \u002F `ANON_KEY`, so you can test the SDK + backend change end-to-end in isolation.\n\nThe full branching workflow lives in the **insforge-cli** skill — see [branch](..\u002Finsforge-cli\u002Freferences\u002Fbranch\u002Foverview.md) for the decision guide and lifecycle commands. Typical loop:\n\n```bash\nnpx -y @insforge\u002Fcli branch create feat-x --mode schema-only\n# ... apply migrations \u002F change auth config \u002F update RLS on the branch ...\n# ... test the SDK against the branch backend ...\nnpx -y @insforge\u002Fcli branch merge feat-x --dry-run     # review SQL\nnpx -y @insforge\u002Fcli branch merge feat-x               # apply to parent\n```\n\n> ⚠ **After `branch create` or `branch switch`**, update the app's InsForge URL and anon-key env values, then **restart your dev server** (or re-source `.env`) so the SDK talks to the selected branch backend.\n\n## SDK Quick Reference\n\nAll SDK methods return `{ data, error }`.\n\n| Module               | Methods                                                                                              |\n| -------------------- | ---------------------------------------------------------------------------------------------------- |\n| `insforge.database`  | `.from().select()`, `.insert()`, `.update()`, `.delete()`, `.rpc()`                                  |\n| `insforge.auth`      | `.signUp()`, `.signInWithPassword()`, `.signInWithOtp()` \u002F `.verifyOtp()`, `.signInWithOAuth()`, `.signOut()`, `.getCurrentUser()`        |\n| `insforge.storage`   | `.from().upload()`, `.uploadAuto()`, `.download()`, `.remove()`                                      |\n| `insforge.functions` | `.invoke()`                                                                                          |\n| `insforge.ai`        | Deprecated fallback only: `.chat.completions.create()`, `.images.generate()`, `.embeddings.create()` |\n| `insforge.realtime`  | `.connect()`, `.subscribe()`, `.publish()`, `.on()`, `.disconnect()`                                 |\n| `insforge.emails`    | `.send({ to, subject, html, cc?, bcc?, from?, replyTo? })`                                           |\n| `insforge.payments.stripe` | `.createCheckoutSession()`, `.createCustomerPortalSession()` |\n| `insforge.payments.razorpay` | `.createOrder()`, `.verifyOrder()`, `.createSubscription()`, `.verifySubscription()`, `.cancelSubscription()`, `.pauseSubscription()`, `.resumeSubscription()` |\n\n## Important Notes\n\n- **Database inserts require array format**: `insert([{...}])`\n- **Bandwidth-efficient reads**: Name columns and `.limit()` list reads; never poll unbounded `select()` on an interval — subscribe with realtime (paired with a `realtime.publish` trigger) or poll a cheap ordered probe instead. Wasteful query shapes are the top cause of projects exhausting their monthly egress allowance. Probe snippet and full rules: [database\u002Fsdk-integration.md](database\u002Fsdk-integration.md#bandwidth-efficient-reads).\n- **Next.js \u002F SSR auth**: Use `@insforge\u002Fsdk\u002Fssr` helpers (`createBrowserClient`, `createServerClient`, `createAuthActions`, `createRefreshAuthRouter`) and import `updateSession` from `@insforge\u002Fsdk\u002Fssr\u002Fmiddleware` in Proxy\u002FMiddleware. Keep the refresh token httpOnly, run auth mutations through `createAuthActions()` on the server, return only safe app data from Server Actions, and let the browser read the short-lived access token for Storage\u002FRealtime. See [auth\u002Fssr-integration.md](auth\u002Fssr-integration.md)\n- **Storage**: Save both `url` AND `key` to database for download\u002Fdelete operations\n- **Functions invoke URL**: Prefer `insforge.functions.invoke(slug)` — the SDK owns route construction. For raw HTTP: the project base URL serves the compat path `\u002Ffunctions\u002F{slug}`, while the functions deployment host (e.g. `*.function2.insforge.app`) serves the slug at root `\u002F{slug}`\n- **Email delivery**: Auth emails (signup verification, password reset, magic links, invites) ship on **every plan**. Custom email via `insforge.emails.send()` ships on **every paid plan**. Use the platform-managed delivery path; custom sender domain is dashboard config. See [email\u002Fsdk-integration.md](email\u002Fsdk-integration.md).\n- **Payments**: Configure provider keys\u002Fcatalog with `npx -y @insforge\u002Fcli payments \u003Cprovider> ...` first; frontend code uses provider-scoped SDK modules.\n- **Payment RLS**: Before payment UI, add app-specific RLS on provider runtime tables. Stripe uses `payments.stripe_checkout_sessions` and `payments.stripe_customer_portal_sessions`; Razorpay uses `payments.razorpay_orders` and `payments.razorpay_subscriptions`. Durable fulfillment triggers go on `payments.webhook_events`, not success URLs, Checkout callbacks, or `payments.transactions`.\n- **Use Tailwind CSS v3.4**\n- **Always local build before deploy**: Prevents wasted build resources and faster debugging\n- **SDK package**: Use `@insforge\u002Fsdk` directly for all features including authentication.\n- **Deployment**: Include a `vercel.json` in the project root for SPA routing (React, React Router apps). The `download-template` tool includes this automatically.\n- **Branching for risky backend changes**: If your SDK code depends on a new schema, RLS policy, or auth config change, create a branch via `npx -y @insforge\u002Fcli branch create` first — see the **insforge-cli** skill's [branch](..\u002Finsforge-cli\u002Freferences\u002Fbranch\u002Foverview.md) reference. After `branch create` \u002F `branch switch`, update the app's InsForge URL and anon-key env values, then **restart the dev server**.\n- **Hit an InsForge-side hurdle?** When the SDK, backend, docs, or a skill misbehaves — an API that should work but errors (`--type bug`), a capability you need that isn't supported (`--type feature-request`), docs that contradict actual behavior (`--type bug --component docs` with `--doc`\u002F`--expected`) — report it and continue with a workaround: `npx -y @insforge\u002Fcli feedback --json --type \u003Cbug|feature-request|friction> --component \u003Cbackend|sdk|cli|skills|docs> --title \"...\" --detail \"...\"`, adding `--language \u003Clang>` for SDK issues (no login required; PII is redacted locally). See the **insforge-cli** skill's Feedback section for the full flag set and situation→type mapping. Never file feedback for problems in the app code you are writing.\n","# InsForge App Integration Skill\n\nThis skill covers **client-side SDK integration** using `@insforge\u002Fsdk`. For backend infrastructure operations (creating tables, inspecting schema, deploying functions, secrets, managing storage buckets, configuring payment provider keys\u002Fcatalog, website deployments, cron job and schedules, logs, etc.), use the **insforge-cli** skill.\n\n## Quick Setup\n\n### 1. Install the SDK\n\n```bash\nnpm install @insforge\u002Fsdk@latest\n```\n\n### 2. Set up environment variables\n\nBefore using the SDK, create a `.env` file (or `.env.local` for Next.js) in your project root with your InsForge URL and anon key.\n\n#### How to get your URL and anon key\n\n1. **Ensure the project is linked.** Check for `.insforge\u002Fproject.json` in the project root.\n   - Generate it with `npx -y @insforge\u002Fcli link` for an existing project or `npx -y @insforge\u002Fcli create` for a new project.\n\n2. **Get the anon key** via the CLI:\n\n   ```bash\n   npx -y @insforge\u002Fcli secrets get ANON_KEY\n   ```\n\n3. **Get the URL** from the `oss_host` field in `.insforge\u002Fproject.json` (e.g., `https:\u002F\u002Fmyapp.us-east.insforge.app`).\n\n4. **Write both values** to the `.env` file using the correct framework prefix (see table below).\n\n> **Important:** Use the anon key for user-scoped SDK clients, including SSR. For privileged server-only app code that needs admin\u002Fservice access, use `createAdminClient({ apiKey })`; the API key is a full-access admin key, equivalent to a service role key on other platforms.\n\nUse the correct environment variable prefix and access pattern for your framework:\n\n| Framework                     | `.env` file  | Variables                                                   | Access Pattern                              |\n| ----------------------------- | ------------ | ----------------------------------------------------------- | ------------------------------------------- |\n| **Next.js**                   | `.env.local` | `NEXT_PUBLIC_INSFORGE_URL`, `NEXT_PUBLIC_INSFORGE_ANON_KEY` | `process.env.NEXT_PUBLIC_*`                 |\n| **Vite** (React, Vue, Svelte) | `.env`       | `VITE_INSFORGE_URL`, `VITE_INSFORGE_ANON_KEY`               | `import.meta.env.VITE_*`                    |\n| **Astro**                     | `.env`       | `PUBLIC_INSFORGE_URL`, `PUBLIC_INSFORGE_ANON_KEY`           | `import.meta.env.PUBLIC_*`                  |\n| **SvelteKit**                 | `.env`       | `PUBLIC_INSFORGE_URL`, `PUBLIC_INSFORGE_ANON_KEY`           | `import { env } from '$env\u002Fdynamic\u002Fpublic'` |\n| **Create React App**          | `.env`       | `REACT_APP_INSFORGE_URL`, `REACT_APP_INSFORGE_ANON_KEY`     | `process.env.REACT_APP_*`                   |\n| **Node.js \u002F Server**          | `.env`       | `INSFORGE_URL`, `INSFORGE_ANON_KEY`                         | `process.env.*`                             |\n\nExample `.env.local` for Next.js:\n\n```bash\nNEXT_PUBLIC_INSFORGE_URL=https:\u002F\u002Fyour-appkey.us-east.insforge.app\nNEXT_PUBLIC_INSFORGE_ANON_KEY=eyJhbGciOiJIUzI1NiIs...\n```\n\n> **Important:** Keep `.env` files local. Add `.env`, `.env.local`, and `.env*.local` to your `.gitignore` and keep `.env.example` for documenting required variables.\n\n### 3. Initialize the client\n\nNext.js:\n\n```javascript\nimport { createClient } from '@insforge\u002Fsdk'\n\nconst insforge = createClient({\n  baseUrl: process.env.NEXT_PUBLIC_INSFORGE_URL,\n  anonKey: process.env.NEXT_PUBLIC_INSFORGE_ANON_KEY\n})\n```\n\nVite:\n\n```javascript\nimport { createClient } from '@insforge\u002Fsdk'\n\nconst insforge = createClient({\n  baseUrl: import.meta.env.VITE_INSFORGE_URL,\n  anonKey: import.meta.env.VITE_INSFORGE_ANON_KEY\n})\n```\n\nAstro:\n\n```javascript\nimport { createClient } from '@insforge\u002Fsdk'\n\nconst insforge = createClient({\n  baseUrl: import.meta.env.PUBLIC_INSFORGE_URL,\n  anonKey: import.meta.env.PUBLIC_INSFORGE_ANON_KEY\n})\n```\n\nFor trusted server-only code that needs project-admin access:\n\n```javascript\nimport { createAdminClient } from \"@insforge\u002Fsdk\";\n\nconst admin = createAdminClient({\n  baseUrl: process.env.INSFORGE_URL,\n  apiKey: process.env.INSFORGE_API_KEY,\n});\n```\n\n## Module Reference\n\n| Module        | Integration Guide                                            |\n| ------------- | ------------------------------------------------------------ |\n| **Database**  | [database\u002Fsdk-integration.md](database\u002Fsdk-integration.md)   |\n| **Auth**      | [auth\u002Fsdk-integration.md](auth\u002Fsdk-integration.md)           |\n| **Storage**   | [storage\u002Fsdk-integration.md](storage\u002Fsdk-integration.md)     |\n| **Functions** | [functions\u002Fsdk-integration.md](functions\u002Fsdk-integration.md) |\n| **AI**        | [ai\u002Foverview.md](ai\u002Foverview.md)                             |\n| **Real-time** | [realtime\u002Fsdk-integration.md](realtime\u002Fsdk-integration.md)   |\n| **Email**     | [email\u002Fsdk-integration.md](email\u002Fsdk-integration.md)         |\n| **Payments: Stripe** | [payments\u002Fstripe.md](payments\u002Fstripe.md)             |\n| **Payments: Razorpay** | [payments\u002Frazorpay.md](payments\u002Frazorpay.md)       |\n\n### What Each Module Covers\n\n| Module        | Content                                                                                                       |\n| ------------- | ------------------------------------------------------------------------------------------------------------- |\n| **Database**  | CRUD operations, filters, pagination, RPC calls                                                               |\n| **Auth**      | Sign up\u002Fin, OAuth, sessions, profiles, password reset                                                         |\n| **Storage**   | Upload, download, delete files; S3-compatible gateway for CI \u002F backup tooling; write RLS policies for buckets |\n| **Functions** | Invoke edge functions                                                                                         |\n| **AI**        | OpenRouter AI calls for chat, images, video, audio, embeddings, and model discovery                           |\n| **Email**     | Send custom transactional HTML emails (welcome, newsletter, notifications)                                    |\n| **Payments: Stripe** | Stripe Checkout Sessions, subscriptions, and Billing Portal redirects                                  |\n| **Payments: Razorpay** | Razorpay Orders, Subscriptions, Checkout.js, and subscription management                               |\n| **Real-time** | Connect, subscribe, publish events, and track presence snapshots plus join\u002Fleave deltas                       |\n\n### Guides\n\n| Guide                                                                                                          | When to Use                                                                                                                                                                                                                                                                                                                                                                                            |\n| -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |\n| [..\u002Finsforge-cli\u002Freferences\u002Fdatabase\u002Faccess-control.md](..\u002Finsforge-cli\u002Freferences\u002Fdatabase\u002Faccess-control.md) | Backend setup for application-table access control — covers RLS, infinite recursion prevention, `SECURITY DEFINER` patterns, performance tips, and common InsForge patterns                                                                                                                                                                                                                            |\n| [storage\u002Fs3-gateway.md](storage\u002Fs3-gateway.md)                                                                 | Fallback path when the consumer is existing S3 tooling (aws CLI, AWS SDKs, rclone, Terraform, boto3) and adopting `@insforge\u002Fsdk` is impractical — covers endpoint\u002Fregion setup, access-key management, path-style addressing, and supported vs. not-supported S3 operations. **Requires InsForge 2.0.9+.** **Prefer the SDK** ([storage\u002Fsdk-integration.md](storage\u002Fsdk-integration.md)) for app code |\n| [storage\u002Fpostgres-rls.md](storage\u002Fpostgres-rls.md)                                                             | Writing RLS policies for `storage.objects` — owner-only, public-read, path-scoped, team-shared, and the `NULL uploaded_by` caveat for mixed REST + S3 buckets                                                                                                                                                                                                                                          |\n| [..\u002Finsforge-cli\u002Freferences\u002Fdatabase\u002Fvector.md](..\u002Finsforge-cli\u002Freferences\u002Fdatabase\u002Fvector.md)                 | Backend setup for semantic search, recommendations, or RAG — covers the `vector` extension, schema\u002Fdimensions, distance operators, HNSW\u002FIVFFlat indexes, and RPC similarity search                                                                                                                                                                                                                     |\n| [ai\u002Fchat-completions.md](ai\u002Fchat-completions.md)                                                               | Text generation, structured answers, and streaming chat through OpenRouter                                                                                                                                                                                                                                                                                                                             |\n| [ai\u002Fimage-generation.md](ai\u002Fimage-generation.md)                                                               | Image generation\u002Fediting through OpenRouter, then durable storage in InsForge Storage                                                                                                                                                                                                                                                                                                                  |\n| [ai\u002Fvideo-generation.md](ai\u002Fvideo-generation.md)                                                               | Async OpenRouter video jobs, status polling, and storing generated media                                                                                                                                                                                                                                                                                                                               |\n| [ai\u002Faudio.md](ai\u002Faudio.md)                                                                                     | Speech-to-text, text-to-speech, and storing audio assets\u002Ftranscripts with InsForge                                                                                                                                                                                                                                                                                                                     |\n| [ai\u002Fembeddings-and-rag.md](ai\u002Fembeddings-and-rag.md)                                                           | Generating embeddings through OpenRouter, storing them in pgvector, and wiring up a basic RAG pipeline                                                                                                                                                                                                                                                                                                 |\n| [ai\u002Fmodels-list.md](ai\u002Fmodels-list.md)                                                                         | Discovering OpenRouter model IDs, modalities, parameters, pricing, and embedding dimensions                                                                                                                                                                                                                                                                                                            |\n| [payments](..\u002Finsforge-cli\u002Freferences\u002Fpayments\u002Foverview.md)                                                    | Configuring Stripe\u002FRazorpay keys, syncing provider catalog, setting up webhooks, and writing payment RLS before app integration                                                                                                                                                                                                                                                                        |\n\n### Building Payments for a New App\n\nFirst choose the provider. There is no generic app payments guide:\n\n- For Stripe Checkout, subscriptions, and Billing Portal, load [payments\u002Fstripe.md](payments\u002Fstripe.md).\n- For Razorpay Orders, Subscriptions, Checkout.js, and cancel\u002Fpause\u002Fresume flows, load [payments\u002Frazorpay.md](payments\u002Frazorpay.md).\n\nBefore writing app code, check provider setup with the **insforge-cli** payments references:\n\n```bash\nnpx -y @insforge\u002Fcli payments stripe status\nnpx -y @insforge\u002Fcli payments razorpay status\n```\n\nIf the chosen provider is unconfigured, ask the developer\u002Fadmin to configure that provider first.\n\n### Real-time Backend Setup\n\nThe real-time SDK is for frontend event handling and messaging. Configure channel patterns, database triggers, and channel\u002Fmessage RLS with the **insforge-cli** skill; see [realtime](..\u002Finsforge-cli\u002Freferences\u002Frealtime.md).\n\n### Backend Configuration\n\nSupported project config knobs are managed via the CLI — use\n`npx -y @insforge\u002Fcli config export\u002Fplan\u002Fapply` for auth redirect URLs,\nverification flags, password policy, auth SMTP settings, storage upload size,\nrealtime\u002Fschedule retention, and cloud deployment subdomain. OAuth providers,\nexternal app setup, storage buckets, functions, secrets, and deployment env vars\nstill use their dedicated dashboard or CLI flows. See the **insforge-cli**\nskill's Configuration section.\n\n### Risky backend changes? Use a branch first\n\nWhen a code change in this skill depends on a **schema migration**, **new RLS policy**, **OAuth provider config change**, or any other backend change that affects prod behavior, create a backend branch first. Branches share `JWT_SECRET` (existing user JWTs keep working) but get a fresh database + EC2 + `API_KEY` \u002F `ANON_KEY`, so you can test the SDK + backend change end-to-end in isolation.\n\nThe full branching workflow lives in the **insforge-cli** skill — see [branch](..\u002Finsforge-cli\u002Freferences\u002Fbranch\u002Foverview.md) for the decision guide and lifecycle commands. Typical loop:\n\n```bash\nnpx -y @insforge\u002Fcli branch create feat-x --mode schema-only\n# ... apply migrations \u002F change auth config \u002F update RLS on the branch ...\n# ... test the SDK against the branch backend ...\nnpx -y @insforge\u002Fcli branch merge feat-x --dry-run     # review SQL\nnpx -y @insforge\u002Fcli branch merge feat-x               # apply to parent\n```\n\n> ⚠ **After `branch create` or `branch switch`**, update the app's InsForge URL and anon-key env values, then **restart your dev server** (or re-source `.env`) so the SDK talks to the selected branch backend.\n\n## SDK Quick Reference\n\nAll SDK methods return `{ data, error }`.\n\n| Module               | Methods                                                                                              |\n| -------------------- | ---------------------------------------------------------------------------------------------------- |\n| `insforge.database`  | `.from().select()`, `.insert()`, `.update()`, `.delete()`, `.rpc()`                                  |\n| `insforge.auth`      | `.signUp()`, `.signInWithPassword()`, `.signInWithOtp()` \u002F `.verifyOtp()`, `.signInWithOAuth()`, `.signOut()`, `.getCurrentUser()`        |\n| `insforge.storage`   | `.from().upload()`, `.uploadAuto()`, `.download()`, `.remove()`                                      |\n| `insforge.functions` | `.invoke()`                                                                                          |\n| `insforge.ai`        | Deprecated fallback only: `.chat.completions.create()`, `.images.generate()`, `.embeddings.create()` |\n| `insforge.realtime`  | `.connect()`, `.subscribe()`, `.publish()`, `.on()`, `.disconnect()`                                 |\n| `insforge.emails`    | `.send({ to, subject, html, cc?, bcc?, from?, replyTo? })`                                           |\n| `insforge.payments.stripe` | `.createCheckoutSession()`, `.createCustomerPortalSession()` |\n| `insforge.payments.razorpay` | `.createOrder()`, `.verifyOrder()`, `.createSubscription()`, `.verifySubscription()`, `.cancelSubscription()`, `.pauseSubscription()`, `.resumeSubscription()` |\n\n## Important Notes\n\n- **Database inserts require array format**: `insert([{...}])`\n- **Bandwidth-efficient reads**: Name columns and `.limit()` list reads; never poll unbounded `select()` on an interval — subscribe with realtime (paired with a `realtime.publish` trigger) or poll a cheap ordered probe instead. Wasteful query shapes are the top cause of projects exhausting their monthly egress allowance. Probe snippet and full rules: [database\u002Fsdk-integration.md](database\u002Fsdk-integration.md#bandwidth-efficient-reads).\n- **Next.js \u002F SSR auth**: Use `@insforge\u002Fsdk\u002Fssr` helpers (`createBrowserClient`, `createServerClient`, `createAuthActions`, `createRefreshAuthRouter`) and import `updateSession` from `@insforge\u002Fsdk\u002Fssr\u002Fmiddleware` in Proxy\u002FMiddleware. Keep the refresh token httpOnly, run auth mutations through `createAuthActions()` on the server, return only safe app data from Server Actions, and let the browser read the short-lived access token for Storage\u002FRealtime. See [auth\u002Fssr-integration.md](auth\u002Fssr-integration.md)\n- **Storage**: Save both `url` AND `key` to database for download\u002Fdelete operations\n- **Functions invoke URL**: Prefer `insforge.functions.invoke(slug)` — the SDK owns route construction. For raw HTTP: the project base URL serves the compat path `\u002Ffunctions\u002F{slug}`, while the functions deployment host (e.g. `*.function2.insforge.app`) serves the slug at root `\u002F{slug}`\n- **Email delivery**: Auth emails (signup verification, password reset, magic links, invites) ship on **every plan**. Custom email via `insforge.emails.send()` ships on **every paid plan**. Use the platform-managed delivery path; custom sender domain is dashboard config. See [email\u002Fsdk-integration.md](email\u002Fsdk-integration.md).\n- **Payments**: Configure provider keys\u002Fcatalog with `npx -y @insforge\u002Fcli payments \u003Cprovider> ...` first; frontend code uses provider-scoped SDK modules.\n- **Payment RLS**: Before payment UI, add app-specific RLS on provider runtime tables. Stripe uses `payments.stripe_checkout_sessions` and `payments.stripe_customer_portal_sessions`; Razorpay uses `payments.razorpay_orders` and `payments.razorpay_subscriptions`. Durable fulfillment triggers go on `payments.webhook_events`, not success URLs, Checkout callbacks, or `payments.transactions`.\n- **Use Tailwind CSS v3.4**\n- **Always local build before deploy**: Prevents wasted build resources and faster debugging\n- **SDK package**: Use `@insforge\u002Fsdk` directly for all features including authentication.\n- **Deployment**: Include a `vercel.json` in the project root for SPA routing (React, React Router apps). The `download-template` tool includes this automatically.\n- **Branching for risky backend changes**: If your SDK code depends on a new schema, RLS policy, or auth config change, create a branch via `npx -y @insforge\u002Fcli branch create` first — see the **insforge-cli** skill's [branch](..\u002Finsforge-cli\u002Freferences\u002Fbranch\u002Foverview.md) reference. After `branch create` \u002F `branch switch`, update the app's InsForge URL and anon-key env values, then **restart the dev server**.\n- **Hit an InsForge-side hurdle?** When the SDK, backend, docs, or a skill misbehaves — an API that should work but errors (`--type bug`), a capability you need that isn't supported (`--type feature-request`), docs that contradict actual behavior (`--type bug --component docs` with `--doc`\u002F`--expected`) — report it and continue with a workaround: `npx -y @insforge\u002Fcli feedback --json --type \u003Cbug|feature-request|friction> --component \u003Cbackend|sdk|cli|skills|docs> --title \"...\" --detail \"...\"`, adding `--language \u003Clang>` for SDK issues (no login required; PII is redacted locally). See the **insforge-cli** skill's Feedback section for the full flag set and situation→type mapping. Never file feedback for problems in the app code you are writing.\n",{"name":5,"license":15,"description":7},"master","fd76f882a04e445e899d5cfb2732f2105ea054ee","skills\u002Fmarketplace\u002Finsforge",0,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS","https:\u002F\u002Fbg-szy.github.io\u002FTOP-SKILLS\u002F","https:\u002F\u002Fgithub.com\u002Fbg-szy","https:\u002F\u002Fwww.ecust.edu.cn\u002F","a student of East China University of Science and Technology","2026-11-15 03:38:02",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill insforge",{"tool":40,"command":41},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill insforge",{"tool":43,"command":44},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill insforge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Finsforge\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"skill-report.json","REFERENCE","参考文档",319922,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Finsforge\u002Fskill-report.json",[55,64,71,78,85,92],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":63},"01M7DXW9N826PKXK174PVW3038","serpmaven","Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.","MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fserpmaven\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":63},"01M7DXVHSTWDV65475QEQ915M7","revnu-landing-page-audit","Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: \"audit my landing page\", \"why isn't this page converting\", \"review my homepage\", \"my ads get clicks but no signups\", \"people bounce from the pricing page\", \"CRO review\", \"improve conversion rate\", \"is my hero section clear\", \"roast my landing page\", \"rewrite my headline\", \"what's wrong with this page\", \"landing page feedback\", \"make the signup page convert better\". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-landing-page-audit\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":63},"01M7DXV8X2D7B3VTD4HHYYHTGR","revnu-growth-context","Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents\u002Frevnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says \"set up our marketing context\", \"who is our ideal customer\", \"write our ICP\", \"describe the product for marketing\", \"positioning doc\", \"what's our brand voice\", \"remember this about our customers\", \"log what we tried\", \"what have we learned from marketing\", \"we changed pricing, update the context\", \"update our growth notes\", \"summarize the business for the agent\", \"import my product-marketing.md\", \"start a growth doc\", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-growth-context\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":63},"01M7DXV0DGJ1G0A60PAHC6J3C5","revnu-get-listed","Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: \"best X\" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says \"get us listed\", \"which directories should we submit to\", \"how do we get into best-of lists\", \"why does ChatGPT recommend competitors and not us\", \"get mentioned in AI answers\", \"submit to awesome lists\", \"get on G2\", \"where are our competitors listed\", \"pitch listicle authors\", \"find backlink opportunities\", \"launch directories\", \"get into roundups\", \"Product Hunt alternatives\", \"where should we be listed\", \"get cited by Perplexity\". Never submits, pays or posts without a yes. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-get-listed\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":63},"01M7DXTSPMGT9D6DSS0HP9BSTA","revnu-ai-readiness-audit","Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks \"is my site ready for AI search\", \"audit my site for AI answers\", \"AEO audit\", \"GEO audit\", \"why doesn't ChatGPT quote our pricing\", \"make our pages citable by AI\", \"do I need llms.txt\", \"does schema help with ChatGPT\", \"check our structured data\", \"is our content visible without JavaScript\", \"AI SEO audit\", \"optimize our homepage for AI answers\", \"LLM SEO check\", \"why does AI get our product wrong\", \"fix our site for AI Overviews\". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-ai-readiness-audit\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":59,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":63},"01M7DXSZHCVTRS620GC3S97JZV","proxy-troubleshooting","Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fproxy-troubleshooting\u002FSKILL.md",[],[]]