deepspace

DeepSpace

DeepSpace is one package for real-time collaborative apps on Cloudflare Workers. It provides auth, RBAC, synchronized records, messaging, integrations, payments, and deploys to <name>.app.space.

This skill is the bootstrap: how to start, how to operate, and how to consult the documentation. The documentation at https://docs.deep.space is the authority for everything else — it is written to be opinionated, so when it recommends an approach, take that as the default rather than one option among many.

One source authority

Every app has exactly one Git authority — DeepSpace source (packaged, commit-first) or GitHub source (manual; deploys ship the local working tree, dirty bytes included) — and as of v0.26.0 it is inferred from use, never declared. A checkout with a GitHub remote deploys as GitHub, no claim step; the first deepspace push (or an unclaimed app's deploy sync) claims DeepSpace source once, permanently — using it is choosing it, so never run deepspace push on a GitHub-centric app unless the user has chosen to adopt DeepSpace source. deepspace app source is read-only (the old setter refuses source_inferred); there are no transfers. Never maintain two sources of truth, and read the source-control and workspaces docs before any source, push, pull, or clone operation — the docs, not this skill, state what each verb does under each authority.

Sharing and handing over an app

Collaborators and ownership transfer (deepspace app collaborators …, deepspace app transfer …) change who can deploy, read secrets, and own the app. Read the app-identity guide before either — it states exactly what each grant confers and what a transfer takes away — and treat both as decisions to surface to the user, not steps to run in passing.

How to read the documentation

Consult the docs BEFORE building in an area, not after something breaks. The reading procedure:

1. Fetch the index once per task area: https://docs.deep.space/llms.txt — generated from the docs on every deploy, so it is never stale — lists every page with a one-line summary.
2. Pick 1–2 pages from it and fetch each as Markdown by appending .md to the page URL (https://docs.deep.space/guides/authentication.md). If the page you picked lacks the answer, do not wander adjacent pages — go to step 3.
3. To prove whether a topic exists at all, fetch https://docs.deep.space/llms-full.txt once (the whole corpus in one file; each page ends with Source: /route.md) and grep it. A confirmed absence means the docs lag the build — fall back to the installed .d.ts or the CLI's own --help.
4. For point lookups within known topics, prefer MCP: https://docs.deep.space/mcp exposes documentation_search and documentation_read. Register it when your harness supports MCP servers, e.g. claude mcp add --transport http deepspace-docs https://docs.deep.space/mcp. Search finds the exact section when the topic exists; it cannot tell you a topic is absent — that is what step 3 is for.
5. For exact type signatures, read the installed package — ls node_modules/deepspace/dist/*.d.ts (in the SDK monorepo itself: packages/deepspace/dist/) — authoritative when any doc lags the installed version.