Build with AI agents

Systhema agents build client sites through the same tokens, components and Payload APIs that developers use. Install the consumer skills for project conventions and connect the documentation service for API lookup.

Start in the consumer projectLink to this section

Confirm package.json depends on @systhemaui/*, or that the root contains .systhema/ or systhema.config.ts. Do not apply Systhema conventions to an unrelated Tailwind or React project.

A blank folder is expected when the brief explicitly asks you to create a Systhema project. Start with the Build a site tutorial.

Install the CLI and skillsLink to this section

Complete registry access, then:

pnpm add -g @systhemaui/cli
systhema skills install --agent claude,codex,cursor --scope project

This installs the bundled consumer skills for those agents in the current project. Use --scope user when you want them available across client projects. See Skills for the complete list and flags.

Connect documentationLink to this section

The docs server is named systhema-docs. Its connection command is:

systhema mcp add docs

If your installed CLI does not expose mcp, use the manual configuration in Docs MCP server. Skills and MCP are separate installations.

Establish the project factsLink to this section

Run in the app that consumes Systhema:

node -p "require('./node_modules/@systhemaui/core/package.json').version"
systhema info

Read systhema.config.ts, the token index and relevant collection references. If references are missing, run pnpm sync and re-read them.

Use the installed version for docs lookup. A lockfile-resolved 1.7.5 is more precise than a manifest range such as ^1.7.0. Docs for agents covers MCP and HTTP retrieval.

Work from a bounded briefLink to this section

Provide page purposes, languages, CMS needs, design inputs and acceptance checks. Ask the agent to name any missing inputs before it invents content or changes the backend model.

Use Workflows for Figma, brand-book, wireframe, upgrade and QA briefs. Keep the conventions in the project's guidance and review the output against them.

An agent's completion report should state what changed, which docs version it used, what checks passed and what remains unverified. For site launch, use the going-live checklist; for client onboarding, share the Editor guide.