@mccaskie-labs/workbench-config 0.1.39 → 0.1.40

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @mccaskie-labs/workbench-config
 
+## 0.1.40
+
+### Patch Changes
+
+- A skill whose client questions aren't written yet (pdf, email) also gets its "Restyling" section, which now says PDFs and emails take project.css too.
+
 ## 0.1.39
 
 ### Patch Changes

package/dist/skills.js

@@ -144,7 +144,7 @@ export function renderSkill(m, guide) {
         ...beforeBlock(m),
     ];
     if (!o) {
-        out.push("", "## Questions", "", "This tool's questions for the client aren't written yet. Use it with its defaults, tell the client that is what you did, and invent no setting. A choice only the client can make goes to them as a plain question.", "", ...useBlock(m, guide));
+        out.push("", "## Questions", "", "This tool's questions for the client aren't written yet. Use it with its defaults, tell the client that is what you did, and invent no setting. A choice only the client can make goes to them as a plain question.", ...(m.styles ? ["", "## Restyling", "", restyleLine(m.styles.prefix)] : []), "", ...useBlock(m, guide));
         return `${out.join("\n")}\n`;
     }
     out.push("", "## What to say", "", d.choice === "optional"
@@ -162,7 +162,7 @@ export function renderSkill(m, guide) {
 }
 /** How a project restyles what a component draws (docs/capabilities-manifest.md §10). */
 function restyleLine(prefix) {
-    return `Everything this tool draws (on a page, in a PDF or in an email) has a \`${prefix}\` class with a default Workbench style, and its colours and sizes are \`--${prefix}*\` variables. All of them are listed, each with what it is, in \`public/styles/workbench.css\`, which \`npx workbench-ui styles\` generates: never edit it. To match the project's own look, write rules for those classes, or set the variables to the project's own colours, in \`public/styles/project.css\`. It loads after workbench.css and always wins. When the client asks for a different look, change project.css, never the tool's markup.`;
+    return `Everything this tool draws (on a page, in a PDF or in an email) has a \`${prefix}\` class with a default Workbench style, and its colours and sizes are \`--${prefix}*\` variables. All of them are listed, each with what it is, in \`public/styles/workbench.css\`, which \`npx workbench-ui styles\` generates: never edit it. To match the project's own look, write rules for those classes, or set the variables to the project's own colours, in \`public/styles/project.css\`. It loads after workbench.css and always wins, and PDFs and emails take it too (\`src/lib/project-css.ts\`). When the client asks for a different look, change project.css, never the tool's markup.`;
 }
 /** The `workbench-start` skill: every tool introduced to the owner, and how their choices are recorded (§9.6). */
 export function renderStart(manifests) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mccaskie-labs/workbench-config",
-  "version": "0.1.39",
+  "version": "0.1.40",
   "description": "Workbench app configuration: WORKBENCH_ENV, typed variables that fail by name, secrets that are never printed, and the capabilities manifest.",
   "license": "UNLICENSED",
   "type": "module",