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 -y @insforge/cli
. Keep npx's
-y
without it, npx asks "Ok to proceed?" before installing the package and blocks forever in a TTY-attached agent shell. 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.
When a task needs a backend and no project is linked yet, do connection setup FIRST — before writing any app code: (1) log in (
whoami
to check; in sandboxes use the two-step device login below), (2)
create
a new project or
link
an existing one, (3) then build against the real project URL and keys from the CLI. Never scaffold with placeholder credentials like
your-project.region.insforge.app
— get the real values first.
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.
At the start of a non-trivial task on a linked project, run
npx -y @insforge/cli memory list
(cheap, no AI call) and recall any title relevant to the task before designing or debugging. Record decisions and the gotchas you hit with
memory remember
at the moment they happen. See
references/memory.md
.
When you hit a hurdle that is InsForge's fault — something that should work but doesn't, a capability you needed but isn't supported, instructions (docs/skill) that reality contradicts, or needless friction — report it with
npx -y @insforge/cli feedback
(see Feedback), then continue the user's task with a workaround. Never file feedback for problems in the user's own app code.
Global Options
Show more
Installs
36.3K
Repository
insforge/insforge-skills
GitHub Stars
36
First Seen
Feb 25, 2026
Security Audits
Gen Agent Trust Hub
Pass
Socket
Pass
Snyk
Fail