You already have an agent. What's missing is somewhere to ship.
The Creght Skill lets Codex, Claude Code, and Cursor build Creght sites directly: pull the source, edit, preview, publish — one chain, start to finish. No server, database, or asset host to set up.
Direct answer
What are the Creght CLI and Skill for?
The CLI pulls a site's source (including Func backend code) into a local workspace, pushes local changes back with three-way merge and conflict resolution, and can open previews, publish, manage versions, read and write CMS content, forms, and data tables, and upload static assets. The Creght Skill is the instruction set an agent reads, so Codex, Claude Code, OpenClaw, or Cursor can work on a Creght project directly.
If you already work through an agent, the value is the infrastructure you skip: no server or certificate to buy and configure (publishing is hosting), no database to stand up (projects ship with JSON data tables), no asset host to wire (creght upload returns a usable URL). You also get an interface your non-technical colleagues can use: the visual editor, CMS, auth, and payments.
The problem
Your agent can write the code. Then what?
Getting an agent to generate a site is the easy part. Where it runs, where the data lives, where images go, and who maintains the content afterwards are the rest.
| Without Creght | With Creght |
|---|---|
| The agent finishes, and you still buy a server and configure Nginx and TLS. | creght push to preview, creght publish to go live. Certificates are automatic. |
| Storing data means a database, a connection string, and migrations. | Projects ship with JSON data tables that Func reads and writes. |
| Images need object storage, bucket policy, and a CDN. | creght upload returns a usable URL right away. |
| After launch, every copy change comes back to you. | The same site has a visual editor and CMS your colleagues can use. |
How it works
What you actually get
Build inside your own agent
creght pull brings the site source — including Func backend code — into a local workspace for the agent to edit. creght diff shows what changed, creght push sends it back with three-way merge, and creght resolve handles conflicts. The Skill works in Codex, Claude Code, OpenClaw, and Cursor.
› Rework the pricing section into three tiers and publish
creght pull→ 24 files
edit page/Index.tsx→ pricing updated
creght diff→ 1 change
creght push→ pushed to preview
✓ Preview updated — run creght publish when it looks right
Pull, edit, diff, and push all happen inside your own agent session.
No server, database, or asset host to configure
Pushing is hosting, and the platform issues the HTTPS certificate. Projects ship with JSON data tables managed through creght table. Static assets go up with creght upload, which returns a usable URL. Three pieces of infrastructure you no longer buy or maintain.
Three things you don't configure
Pushing is hosting; the platform issues and renews HTTPS.
Projects ship with JSON data tables Func reads and writes.
Upload a local file and get a usable URL back.
Auth and payments are already there
Site users, email login, and Google and GitHub OAuth are runtime resources of the site; Alipay web payments have a full guide; forms and Func backend logic are manageable from the CLI too. What you skip is not only deployment but the parts you would otherwise rewrite every time.
/backend/func/checkout.ts
export async function pay(input, ctx) {
const user = ctx.auth.requireUser()
const order = await ctx.db.insert('orders', {
userId: user.id, amount: input.amount,
})
return buildAlipayUrl(order)
}The signed-in user comes from ctx.auth, the order goes into ctx.db, and the Alipay signature is built inside Func — no service to stand up.
Beyond code, an interface for your team
The same site has a visual editor and a CMS: you write structure in the agent, colleagues change copy and content in the browser. Version history can even be used as a read-only git remote (creght git).
You, in the agent
› creght push
→ pushed to preview, 3 files
Your team, in the browser
One site: you push code, your team edits content in the CMS — neither blocks the other.
Plug Creght into your agent.
Install the Skill and let Codex or Claude Code pull, edit, and publish your site.