# Templates Come to the CLI: Let Your Agent Pick One and Build Your Site From It - Creght Blog

> Creght CLI 0.14.0 opens the template gallery to AI agents. Ask "which template fits my site?" and the agent recommends candidates with live preview links; confirm one and it creates the project, adapts the content to yours, and pushes a preview. No command line involved.

[Back to blog](/blogs.md)

Product UpdatesSep 3, 2026

# Templates Come to the CLI: Let Your Agent Pick One and Build Your Site From It

Creght CLI 0.14.0 opens the template gallery to AI agents. Ask "which template fits my site?" and the agent recommends candidates with live preview links; confirm one and it creates the project, adapts the content to yours, and pushes a preview. No command line involved.

![Creght](https://ugc.talizen.com/_assets/site/2061660904709165056/1780797461299__creght_logo.png)

Product Updates

Let your agent pick the template

Creght's gallery of full-site templates used to be for humans only: you browsed the template page yourself, picked one, and clicked "Use". An AI agent building your site couldn't see any of it — it had to start from a blank project and write every page, even though a finished, design-reviewed starting point was sitting right there on the platform.

Creght CLI 0.14.0 opens the gallery to agents. In environments with the Creght skill installed — Claude Code, dsh, and friends — the agent can now browse templates, recommend them against your requirements, and, once you confirm, start a project straight from one.

## Two sentences from template to website

First sentence: say what site you want.

> "I'm building a homepage for an open-source project on Creght — which template fits?"

The agent goes through the gallery and shortlists candidates by name, description, and category, each with its **preview link**. A preview link opens the template as a real rendered website, not a screenshot; if you'd rather not click through them, ask the agent to open the previews itself and report back.

Second sentence: confirm.

> "Use this one — build my site from it."

The agent creates a new project from the template — pages, components, and CMS content copied over — pulls the code locally, swaps in your copy, logo, navigation, and colors, pushes to the preview environment, and hands you the preview link. You never touch a command.

Two decisions always stay with you: **the project is only created after you confirm the template** — the agent won't pick one on your behalf — and **going to production always takes an explicit ask**; after edits, the agent only pushes previews.

## Under the hood: four new commands

The agent runs ordinary commands, and you can too:

> `creght tpl list` to browse ｜ `creght tpl get <id>` for details ｜ `creght tpl categories` for categories ｜ `creght tpl use <id> --name=project` to create a project from a template

Every command takes `--json`. `tpl use` prints the new site's `project_id/site_id`, so a `creght pull` right after starts the editing loop.

## How to get it

Template commands ship with CLI 0.14.0 — upgrade with `npm i -g creght-cli@latest` or `creght update`. In practice the CLI isn't your problem: the skill has agents install and upgrade it themselves. The one thing to do is update the Creght skill package to the latest (re-run the same command you installed it with), and your agent knows the whole flow.

> [Browse the template gallery →](/templates.md) ｜ [Full Creght Skill guide →](/docs/ai/creght-skill.md)

[Aug 4, 2026\
\
Creght's backend: server logic, auth and payments with Func](/blogs/backend-func-auth-payment.md)

> Full page index: [/llms.txt](/llms.txt)