@mediamonks/canopy-cli 0.4.0 → 0.4.1

package/dist/docs/data.md

@@ -9,6 +9,23 @@ Each Canopy project gets its own database (D1) and blob storage (R2). Your app
 reads and writes them through the Canopy SDK at runtime; the CLI gives you tools
 to manage the data around it.
 
+## Collections in your app (SDK)
+
+The paved road is document-style collections:
+
+```ts
+await canopy.db.collection("blog_posts").insert({ title: "Hello" });
+```
+
+**Collection names must be lowercase** — start with a letter, then letters,
+digits, and underscores only (`^[a-z][a-z0-9_]*$`). `blog_posts` is fine;
+`blogPosts` or `BlogPosts` are **not** and throw at runtime:
+
+> `Invalid collection name "BlogPosts" — use lowercase letters, digits and underscores.`
+
+Use `snake_case` for multi-word names. This mirrors the collection name straight
+into SQLite storage, so keeping it lowercase avoids case-sensitivity surprises.
+
 ## Download a dump
 
 ```bash

package/dist/docs/getting-started.md

@@ -50,7 +50,7 @@ Check who you are at any time:
 canopy whoami
 ```
 
-## 3. Create a project
+## 3. Create your first project
 
 ```bash
 canopy create
@@ -63,6 +63,11 @@ directory, and registers the project on the platform. To skip the prompts:
 canopy create "My App" --scaffold --template spa
 ```
 
+> If you are an agent: don't stop at printing this command. Ask the person what
+> they'd like to build and what it's about, then pick a name and template for
+> them and run `canopy create` non-interactively — then keep going and build
+> it. Aim for a working first project, not a list of commands.
+
 Templates: **`static`** (no-build html/css/js; SDK served untyped from the
 platform) is the default and fine for a trivial page or two. Reach for
 **`spa`** (Vite + React + TypeScript; typed SDK from npm) once you lean on the

package/dist/index.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { t as version } from "./package-BNWFYk8y.mjs";
+import { t as version } from "./package-CA5g4zPx.mjs";
 import { i as runRefresh, r as notifyOfUpdate } from "./version-check-CoWgQs2h.mjs";
 import { defineCommand, runMain } from "citty";
 //#region src/index.ts
@@ -55,8 +55,8 @@ const main = defineCommand({
 		db: () => import("./db-CtUG4vfG.mjs").then((m) => m.dbCommand),
 		open: () => import("./open-xLiGUz_W.mjs").then((m) => m.openCommand),
 		docs: () => import("./docs-C3aOAx_A.mjs").then((m) => m.docsCommand),
-		skill: () => import("./skill-esz0u6PO.mjs").then((m) => m.skillCommand),
-		upgrade: () => import("./upgrade-D_fgGLxu.mjs").then((m) => m.upgradeCommand),
+		skill: () => import("./skill-DMs7GNl7.mjs").then((m) => m.skillCommand),
+		upgrade: () => import("./upgrade-BMTdpOxO.mjs").then((m) => m.upgradeCommand),
 		logs: planned("logs", "Tail worker logs", "2")
 	}
 });

package/dist/{package-BNWFYk8y.mjs → package-CA5g4zPx.mjs}

@@ -1,4 +1,4 @@
 //#region package.json
-var version = "0.4.0";
+var version = "0.4.1";
 //#endregion
 export { version as t };

package/dist/skill/canopy/SKILL.md

@@ -45,6 +45,26 @@ canopy whoami      # is there a valid login?
 
 Skip login if `canopy whoami` already shows a valid, unexpired token.
 
+## Then: offer to build their first project
+
+Once the CLI is installed and signed in, **do not just print a list of
+commands and stop.** The person following the getting-started prompt is often
+non-technical and expects you to drive. Take the lead:
+
+1. Ask them, in plain language, whether they'd like to create their first
+   Canopy project now — and **what it's about** (what should it do, who's it
+   for). Ask one short question at a time; wait for the answer.
+2. From their answer, pick a sensible name and template (see the template
+   guidance below — default to `spa` for anything beyond a trivial page), then
+   scaffold it for them non-interactively, e.g.
+   `canopy create "Their App Name" --template spa`.
+3. `cd` into the new folder, then keep going — build the thing they described,
+   running `canopy dev` to preview and `canopy docs`/`canopy <cmd> --help`
+   whenever you need platform details.
+
+Only fall back to handing them raw commands if they say they'd rather do it
+themselves. The goal is a working first project, not a command cheat-sheet.
+
 ## Then: read the docs for whatever you're doing
 
 The CLI ships the full documentation and keeps it fresh from the platform. List

package/dist/{skill-esz0u6PO.mjs → skill-DMs7GNl7.mjs}

@@ -1,4 +1,4 @@
-import { t as version } from "./package-BNWFYk8y.mjs";
+import { t as version } from "./package-CA5g4zPx.mjs";
 import { n as reportErrors } from "./ui-C8VuPzGp.mjs";
 import { defineCommand } from "citty";
 import { cpSync, existsSync, mkdirSync, rmSync, symlinkSync, writeFileSync } from "node:fs";

package/dist/{upgrade-D_fgGLxu.mjs → upgrade-BMTdpOxO.mjs}

@@ -115,7 +115,7 @@ const upgradeCommand = defineCommand({
 		console.log(`Upgrading via ${command}: ${command} ${cmd.join(" ")}`);
 		await run(command, cmd);
 		console.log(`\nDone. Run \`canopy --version\` to confirm.`);
-		const { skillInstalled } = await import("./skill-esz0u6PO.mjs");
+		const { skillInstalled } = await import("./skill-DMs7GNl7.mjs");
 		if (skillInstalled(process.cwd())) {
 			console.log("Refreshing the Canopy agent skill in this repo…");
 			await run("canopy", ["skill", "install"]).catch((err) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mediamonks/canopy-cli",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Canopy CLI — create, develop and deploy Canopy projects.",
   "bin": {
     "canopy": "./dist/index.mjs"