Skip to main content
A workspace is a zitejs monorepo: one repository holding every app and workflow, the generated types, and a shared design system. Agents build inside it; this page is the map so you (and they) know where everything lives.

Layout

Generated files

The .zite/ directories, at the workspace root and inside each app, are generated and must never be edited. src/main.tsx is generated too. The platform writes .zite/meta.ts; everything else is refreshed by zitejs generate whenever the schema, workflows, or integrations change (the build tools run this for you): zitejs/auth, zitejs/upload, zitejs/pdf, and zitejs/schedules come straight from the zitejs package, with nothing generated. Read them to learn the exact table names, record types, and workflow signatures. Never modify them.

Import conventions

  • Platform SDKs: always via zitejs/* aliases: zitejs/db, zitejs/backend, zitejs/api, zitejs/auth, zitejs/integrations, zitejs/email, zitejs/meta, and the utility modules (zitejs/schedules, zitejs/pdf, zitejs/upload). Never import from .zite/ by relative path.
  • Shared UI: from @project/components/ui/* (e.g. import { Button } from '@project/components/ui/button').
  • Your own files: components, hooks, and utilities you create in an app’s src/, via relative paths (./components/Foo).
  • Nothing else: an app may import its own files, workspace packages under packages/, and the generated .zite/ files. Code shared between apps goes in a package, not in a relative path that reaches outside apps/<dir>/.

Config files

zite.config.json (workspace)

At the workspace root: { "project": { "name": "...", "basePublicIdentifier": "..." }, "integrations": { ... } }. The workspace name, the id of its database, and the integrations every app can use.

zite.config.json (app)

In each apps/<dir>/: id (written by the platform, never change it), accessMode, authentication, integrationSettings, envVars (a mirror of Settings → Secrets, never hand-edited), seoSettings, and pwaSettings. See Authentication and Title, favicon, and link previews.

zite.schema.json

The enriched database schema: table and field SDK names, types, and options. Drives .zite/db.ts.

Context

context/ at the root holds Markdown documents you write for the agent: data model notes, policies, specs, brand guidelines. The agent sees an inventory of them every turn and reads the ones relevant to what it’s building. See Context.