Getting Started

Connect your LLM client to the governed deployment platform.

What can I build?

The platform currently supports two kinds of apps. Tell your agent which fits your project and the skills will handle the rest.

Static site

Content-led pages, marketing sites, docs, and portfolios. Built from plain HTML/CSS/JS or a static-site generator. No server, no database — just fast, globally cached assets.

Worker app

Apps that need a server and durable data — product catalogs, blogs, inventory trackers, and similar. Backed by a platform-provisioned D1 database and a Hono API, with a Vite React SPA as the frontend.

1. Install the skills

Download the starter bundle and extract it. You get a ready-to-use gda-app/ folder containing opencode.json (MCP server config), a root AGENTS.md that tells the agent to authenticate before building, and all four platform skills in .opencode/skills/. Open the folder in your editor and you are ready to go.

2. Add the MCP server (optional — already included in the bundle)

If you extracted the bundle above, your opencode.json is already configured. If you are adding the platform to an existing project instead, create or update your project-local opencode.json with the snippet below. Replace the URL with the endpoint your operator provided.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gda": {
      "type": "remote",
      "url": "https://cp.fryan-vibedevplatform.com/mcp"
    }
  }
}

3. Authenticate MCP access

This step is required. Without MCP auth, the agent cannot list templates, create an app, clone the platform-seeded starter, or deploy through the governed control plane. Run the OpenCode auth command; it opens a browser to complete Cloudflare Access login and stores the MCP OAuth grant locally.

opencode mcp auth gda

4. Build and deploy

Describe what you want to build and let the agent take it from there. It uses MCP to choose a supported template, prepares a source repository that is already seeded from the platform-owned starter, adapts the tenant-editable files, pushes source, and runs the governed build — all without leaving your editor. The project instructions and skills keep it on the right path; the MCP tools give it the keys to the platform.

Example prompts
Be direct about what you want — the agent picks the right app type and skill automatically.

"Build a marketing site for Acme Widgets and deploy it."

"Create a product catalog app for a boot store with inventory tracking and deploy it."

5. Approve and go live

The agent stops at preview-ready and hands you a dashboard link. Your app is not publicly live yet — a human approval is required before it is published. Review the preview, then approve the build in the dashboard. Only after approval does the platform promote the build to the live URL.

Head to your app in the dashboard, open the latest build, and click Approve.

Go to dashboard