contentrain-generate

Skill: Generate SDK Client

Generate the typed Contentrain query client from model definitions using the Prisma-pattern codegen.

---

When to Use

The user wants to generate or regenerate the SDK client, or says something like "generate client", "regenerate types", "set up contentrain imports", "run contentrain generate", "update SDK types".

---

Steps

1. Check Project State

Call contentrain_status to verify:

• .contentrain/ directory exists with config.json.
• At least one model exists in .contentrain/models/.
• Content files exist for the configured locales.

If the project is not initialized, stop and suggest running /contentrain-init first. If no models exist, suggest /contentrain-content to create content first.

2. Verify Prerequisites

Check that the required packages are available:

• @contentrain/query must be installed in the project's package.json (as a dependency).
• The contentrain CLI must be available (via npx contentrain or globally installed).

If @contentrain/query is not installed, install it using the project's package manager:

# Use whichever package manager the project uses
pnpm add @contentrain/query
# or: npm install @contentrain/query
# or: yarn add @contentrain/query

3. Run the Generator

Execute the generation command:

npx contentrain generate

Two ways to invoke the generator:

• contentrain generate — via the contentrain CLI (recommended; requires the contentrain package installed). This is what all examples in this skill use.
• npx contentrain-query generate — directly via the @contentrain/query package's own bin, for projects that depend only on @contentrain/query (programmatic / build-tool flows). Both run the same generator.

If the project uses a non-standard root directory, specify it:

npx contentrain generate --root .

This reads .contentrain/models/ and .contentrain/content/ to produce:

.contentrain/client/
  index.mjs          — ESM entry (query runtime + re-exports)
  index.cjs          — CJS entry (NestJS, Express, legacy tooling)
  index.d.ts         — Generated types (from model schemas)
  data/
    {model}.{locale}.mjs   — Static data modules per model/locale