insforge

# InsForge App Integration Skill This skill covers **client-side SDK integration** using `@insforge/sdk`. For backend infrastructure operations (creating tables, inspecting schema, deploying functions, secrets, managing storage buckets, configuring payment provider keys/catalog, website deployments, cron job and schedules, logs, etc.), use the **insforge-cli** skill. ## Quick Setup ### 1. Install the SDK ```bash npm install @insforge/sdk@latest ``` ### 2. Set up environment variables Before using the SDK, create a `.env` file (or `.env.local` for Next.js) in your project root with your InsForge URL and anon key. #### How to get your URL and anon key 1. **Ensure the project is linked.** Check for `.insforge/project.json` in the project root. - Generate it with `npx -y @insforge/cli link` for an existing project or `npx -y @insforge/cli create` for a new project. 2. **Get the anon key** via the CLI: ```bash npx -y @insforge/cli secrets get ANON_KEY ``` 3. **Get the URL** from the `oss_host` field in `.insforge/project.json` (e.g., `https://myapp.us-east.insforge.app`). 4. **Write both values** to the `.env` file using the correct framework prefix (see table below). > **Important:** Use the anon key for user-scoped SDK clients, including SSR. For privileged server-only app code that needs admin/service access, use `createAdminClient({ apiKey })`; the API key is a full-access admin key, equivalent to a service role key on other platforms. Use the correct...