Skip to content

Project Checklist

Pre-Build Checklist

Input Contract

  • chosen framework/runtime
  • selected package surfaces
  • whether the project includes admin UI, public site, or API only
  • deployment and publishing method

Starter Prompt

text
Run a final pre-build review for a system-core project.

Framework/runtime:
Selected exports:
User-facing surfaces:
Deployment method:

Check for:
- wrong import paths
- duplicated auth/CMS/delivery/storage logic
- missing client metadata packages for browser code
- missing CI/CD or docs versioning steps
  • Decide whether the project needs createSystem() or createApp().
  • Pick the correct HTTP integration adapter.
  • Define required environment variables before bootstrapping.
  • Confirm which package-owned surfaces the app will consume directly.
  • Confirm whether the app needs Prisma-backed CMS features.
  • Confirm whether auth, delivery, storage, and platform services will remain package-owned.
  • Confirm browser/admin surfaces use *-client, theme, sections, and ui-contracts exports rather than server-only runtime code.
  • Confirm deployment uses the package publishing and monitoring model already documented in operations pages.

For AI Agents

Before producing code, answer these questions:

  1. Which exported module owns the target concern?
  2. Which runtime field or package surface should the app call?
  3. Which integration adapter owns request translation?
  4. Is the code about to bypass an existing package boundary?

system-core documentation for maintainers, integrators, and AI build agents.