Developer documentation

Build apps the team can review and ship here

This platform stays intentionally narrow. The shell handles discovery and presentation, and each app owns its own product logic.

ScaffoldManifestRegister
pnpm new:app stream-overlay-lab "Stream Overlay Lab"

The scaffolder creates the package, writes the starter contract, registers the app, and updates the platform transpilation list.

Manifest anatomy

defineApp({
  manifest: {
    id: "stream-overlay-lab",
    slug: "stream-overlay-lab",
    name: "Stream Overlay Lab",
    tagline: "Short directory pitch",
    description: "Longer explanation for the app page.",
    category: "Experiments",
    status: "preview",
    visibility: "public",
    version: "0.1.0"
  },
  entry: StreamOverlayLab
})

Submission checklist

  • The app runs under /apps/[slug] without modifying shell-level auth or data assumptions.
  • The manifest copy is strong enough for the directory and app detail page.
  • Dependencies are local to the app package unless they are true platform primitives.
  • The app is responsive and consistent with the Fame Game visual language.
  • pnpm typecheck and pnpm build both pass before review.

Shell

Stateless

The platform does not provide global auth or DB conventions.

Review

Team-approved

Apps need to be clean, useful, and platform-compatible before shipping.

Acceptance rules

  • Package the app under packages/apps/<slug> and export one defineApp(...) contract.
  • Keep auth, persistence, billing, secrets, and third-party APIs inside the app package.
  • Ship a clear public manifest: name, slug, description, category, status, and version.
  • Make the app production-clean: no dead routes, no broken states, no placeholder copy.

Repo docs

Canonical docs live in docs/app-development.md and docs/platform-architecture.md.