insforge-cli

Backend infrastructure management for InsForge projects via command-line interface.

- Manage databases with raw SQL execution, schema inspection, RLS policies, and import/export capabilities

- Deploy and invoke serverless edge functions, create and manage storage buckets, and handle file uploads/downloads

- Deploy frontend applications with environment variable configuration across multiple frameworks (Vite, Next.js, Create React App, Astro, SvelteKit)

- Create and monitor scheduled cron jobs (5-field format) with secret references in headers, manage secrets with soft-delete and expiration, and view backend logs across multiple sources

- Requires authentication via insforge login and project linking via insforge create or insforge link before any operations

InsForge CLI

Use this skill whenever someone needs a backend, or when managing InsForge backend and cloud infrastructure with the InsForge CLI. For application code that calls InsForge from a frontend, backend, or edge function, use the insforge app-integration skill instead.

Core Rules

- Always run the CLI through npx @insforge/cli <command>. Do not install or call a global insforge binary.

- If the project is already linked, use the current linked project. Run login, project creation, link, project discovery, organization listing, or cloud project commands only when connection setup is actually needed.

- Treat InsForge API keys as full-access admin keys. Keep them server-only and out of frontend/public env vars.

- Prefer CLI commands and documented project config over raw backend HTTP calls. If config apply reports unsupported/skipped fields, surface that result instead of bypassing the CLI with direct API calls.

- Use --json when structured output or non-interactive value collection is needed. Use --yes for confirmation prompts when the user has approved the action.

Global Options

Flag
Use

--json
Structured JSON output and skip value-collection prompts such as text/select prompts. Errors if any required value is missing. Combine with -y for destructive commands that also ask for Y/N confirmation.

-y, --yes
Auto-accept Y/N confirmation prompts such as delete or overwrite prompts. Does not skip value-collection prompts; use --json for that.