For coding agents

Use the repository SKILL.md as the execution policy and these docs as the interface reference.

Connect from the homepage prompt

When a user starts with the prompt copied from opencloud.ai, begin with the product conversation. Ask what they want to build, who it is for, and which single workflow matters most before choosing infrastructure.

When the project is ready for live platform work:

1. Install and checksum-verify the pinned public CLI from github.com/opencloud-ai/cli using the CLI reference.
2. Confirm opencloud --cli-version is 0.6.0, then run opencloud doctor. If this environment cannot execute the CLI, remain offline.
3. Ask for the user's email only if it is not already available. Do not ask them to invent or check an app domain.
4. Run opencloud onboard --email "$USER_EMAIL" --name "$PROJECT_NAME". OpenCloud derives the project slug from the title and adds a random suffix.
5. A new email receives a provisional account grant and first project immediately. The same grant may create additional apps. The user only needs to confirm the email within 24 hours, while the agent can continue building.
6. An existing email receives a confirmation request and no credential. After the user confirms it, run opencloud onboard-complete.
7. Run app list and app get "$APP_ID" before making platform changes.

If a new user does not verify within 24 hours, all apps made by the provisional grant are paused. They show a verification page, stop runtime and cron invocations, and retain all data until verification resumes them.

Never ask the user for an account password, session cookie, bootstrap token, service-role key, database credentials, or a copied connection pack. The CLI keeps its revocable project credential in an ignored mode-0600.opencloud/session.json. Never read or print that file.

Reading order

1. Read the hosted SKILL.md completely.
2. Read the quickstart.
3. Load the control-plane OpenAPI for agent, CLI, deployment, and operations work. Load the separate app runtime OpenAPI for code running inside an app.
4. Read only the capability guides required by the requested product.
5. Read the relevant JavaScript namespace pages before writing frontend calls.
6. Read the manifest, SQL, and verification references before deployment.
7. Keep the development loop, verification contract, and Functions/server library guide open while implementing.

First-turn checkpoint

Create a real opencloud.yaml and non-empty frontend in the first coherent file batch. Run the artifact checker and validate before polishing the UI. Once the first coherent artifact validates, start a development session. Sync each coherent change, inspect the stable preview, invoke Functions only explicitly, and obtain a receipt before promotion. Read Develop safely before production.

Contract rules

• Use runtime.javascriptSdk.module; do not guess SDK URLs or methods.
• Implement new Functions with @opencloud/server and its defineFunction boundary.
• Use browser functions.invoke and functions.invokePublic in production. In dev, Functions remain dormant until app dev invoke or a deliberate preview interaction explicitly calls them.
• Use realtime.channel(...).connect() and onBroadcast(...); there is no Supabase-style .on(...).subscribe() API.
• Treat telemetry absence as unknown or quiet, not healthy.
• Keep credentials and brokered tokens out of files, output, and reports.
• Use a unique version for every deployment.
• Preserve exact operation, deployment, artifact, cron, and backup evidence.

Definition of done

An online app is done only when:

• local product tests and OpenCloud validation pass;
• the durable deployment operation succeeds;
• the isolated dev preview passes and a receipt covers the exact promoted source and migrations;
• the authoritative app verify operation passes;
• the feature-aware verifier passes where configured;
• logs and telemetry were inspected honestly; and
• the canonical HTTPS app remains active.
• app dev promote reported the live URL and stopped the dev session after production verification.

If online credentials are absent, produce an offline-valid deterministic bundle and list the exact remaining live steps.