@the-smithy/create-hearth-site 0.29.0 → 0.31.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@the-smithy/create-hearth-site",
-  "version": "0.29.0",
+  "version": "0.31.0",
   "description": "Start a new client website powered by Hearth: pnpm create @the-smithy/hearth-site",
   "type": "module",
   "license": "SEE LICENSE IN LICENSE",
@@ -30,7 +30,7 @@
   ],
   "devDependencies": {
     "vitest": "^5.0.3",
-    "@the-smithy/hearth-schema": "^0.29.0"
+    "@the-smithy/hearth-schema": "^0.31.0"
   },
   "scripts": {
     "test": "node --test \"test/**/*.test.js\" && vitest run test/blocks.test.ts test/overrides.test.ts",

package/template/AGENTS.md

@@ -170,6 +170,9 @@ Do these before writing code, and tell the developer what you found:
    `node_modules/@the-smithy/hearth/llms.md` for the SDK. It also installs Drift and any skills Hearth offers this site
    (see "Skills" below), so run it again when they're missing. These aren't committed, so some assistants' search skips
    them: open them by their exact path, or from the terminal if your tool won't.
+   Hearth's MCP server (`/api/mcp` on Hearth, read-only, with the site's API key) answers the same questions without
+   the files, if the developer has connected it: each block's fields, slots and starting classes, the tokens, and the
+   published content. For design work, its `get_design_workflow` tool is the way to carry a design from Figma.
 3. **"Nothing is published"** means every page is a 404 until editors publish in Hearth. That's not a code
    problem: say so, and don't add placeholder content to work around it.
 4. **Then style the site** as above, checking with `pnpm dev` against the published pages, on a phone width too.

package/template/README.md

@@ -64,6 +64,11 @@ Once your API key is in `.env.local`:
    - *"The gallery looks plain. Make it a masonry grid using its slots in the theme, keeping it accessible."*
    - *"Run `pnpm hearth:update`, then check every published page still looks right."*
 
+**Without the code, or for design work:** Hearth also has an MCP server, so an agent can read the site's blocks, design
+system and published content from anywhere, read-only. Hearth's **API & webhooks** page shows how to connect it. Ask a
+connected agent to start with `get_design_workflow` to design the site in Figma and bring the design back into
+`src/theme/`.
+
 Keep the API key out of chat: the agent never needs to see it, only `.env.local` does. If it asks for content
 (page text, menus, contact details), the answer is to add or publish it in Hearth, not to write it into the code.
 

package/template/scripts/hearth.mjs

@@ -246,9 +246,9 @@ async function drift() {
 
   // Drift's skill follows its version, so like Hearth's skills it's installed rather than committed.
   for (const dir of SKILL_DIRS) listSkills(dir, listedSkills(dir));
-  const install = spawnSync(bin, ["install", "."], { encoding: "utf8" });
+  const install = spawnSync(bin, ["install", ".", "--hook"], { encoding: "utf8" });
   if (install.status !== 0) fail(`Drift couldn't install its skill: ${install.stderr?.trim() || install.error?.message}`);
-  console.log(`✓ Installed Drift's skill in ${SKILL_DIRS.map((d) => `${d}/`).join(" and ")}.`);
+  console.log(`✓ Installed Drift's skill in ${SKILL_DIRS.map((d) => `${d}/`).join(" and ")}, and its Claude Code hook in .claude/settings.json.`);
 }
 
 /** The files in a zip archive, by name. */