nubase

# Nubase Core Skill Nubase turns AI-written code into real apps: the backend **and** deploy layer that a coding agent drives directly to ship a generated app online in minutes. It provides eight capability modules, each with a stable API and (where useful) MCP tools: | Module | What it does | Agent entry | | --- | --- | --- | | Database | Postgres + PostgREST data layer (`/rest/v1`) per project, with RLS | `rest_select`, `sql_execute` | | Auth | Supabase-style users, sessions, OAuth/MFA (`/auth/v1`) | `auth_*` | | Storage | Buckets + signed URLs for user files (`/storage/v1`) | `storage_*` | | Assets | Publish the generated **frontend** to a public CDN (`/assets/v1`) | `assets_*` | | Functions | Deploy backend logic as edge functions (`/functions/v1`) | `functions_*` | | AI Gateway | OpenAI/Anthropic-compatible LLM routing + usage (`/v1`) | `gateway_*` | | Memory | Durable agent/user/project context (`/mem/v1`) | `memory_*` | | cron | Schedule recurring jobs (edge fn / db fn) | `cron_*` | ## Required First Moves When starting a Nubase task: 1. Call `nubase_overview()` first. One call returns the whole backend state — capabilities, database schema, storage buckets, auth users, AI Gateway keys, the permission gates that are on/off, and suggested next steps. 2. Call `memory_context({ "task": "<current task>" })` to recall prior decisions. 3. Identify which capability owns the work and read the matching reference (see References below). 4. Prefer stable Nubase APIs and tool...