This project uses InsForge: an all-in-one, open-source Postgres-based backend (BaaS) that gives this app a database, authentication, file storage, edge functions, realtime, an AI model gateway, and payments through one platform.
- Project: perception-learning (API base
https://tzj772sx.us-west.insforge.app) - Skills: these InsForge skills are installed for supported coding agents. Reach for them before implementing any InsForge feature instead of guessing the API:
insforge: app code with the@insforge/sdkclient (database CRUD, auth, storage, edge functions, realtime, AI, email, and Stripe payments).insforge-cli: backend and infrastructure via theinsforgeCLI (projects, SQL, migrations, RLS policies, storage buckets, functions, secrets, payment setup, schedules, deploys).insforge-debug: diagnosing failures (SDK/HTTP errors, RLS denials, auth and OAuth issues) and running security or performance audits.insforge-integrations: wiring external auth providers (Clerk, Auth0, WorkOS, Better Auth, etc.) for JWT-based RLS, or the OKX x402 payment facilitator.find-skills: discovering additional skills on demand.
- Credentials: app code reads keys from
.env.local; the CLI reads.insforge/project.json. Never hardcode or commit keys.
Key patterns:
- Database inserts take an array:
insert([{ ... }]). - Reference users with
auth.users(id); useauth.uid()in RLS policies. - For storage uploads, persist both the returned
urlandkey.