synthesisui 0.15.0 → 0.16.1

package/dist/claude-md.js

@@ -86,6 +86,30 @@ async function readManifest(projectRoot, ds) {
         return null;
     }
 }
+/**
+ * The loop that closes itself, and the one paragraph both kinds of system share.
+ *
+ * The contract said what to write and never said to check, so verification
+ * happened days later, by a human, across a whole repo - archaeology rather
+ * than a fix. `doctor <file> --verbose` already existed; nobody was pointing
+ * the agent at it.
+ *
+ * Held in one constant on purpose: the same paragraph typed into two template
+ * literals is two paragraphs that drift.
+ */
+const SELF_CHECK = `
+
+**After writing or editing any UI file, check it before moving on:**
+
+    npx synthesisui@latest doctor <the file you just wrote> --verbose
+
+It names the token for every hardcoded value it finds. Fix what it names, run it
+again, and only then move to the next thing. Do not batch this up for the end -
+a component checked while you still have its context is a two-line fix; the same
+component found in a repo-wide audit next week is an archaeology exercise.
+
+If it reports a value with no token, do NOT invent one. Say which value and what
+you would call it, and let a person decide.`;
 async function renderRegion(projectRoot, installed) {
     if (installed.length === 0) {
         return `${START}\n${END}`;
@@ -111,15 +135,24 @@ async function renderRegion(projectRoot, installed) {
 project's OWN custom properties, exactly as the guide lists them. Do not write raw colours,
 spacings or radii that a token already covers, and do not invent a new token silently - say so
 instead, because a new token is a decision for a person to make. There is no component
-manifest for an adopted system - the tokens ARE the contract. Run \`synthesisui doctor\` to see
-how much of the shipped UI already resolves to them.`
+manifest for an adopted system - the tokens ARE the contract.${SELF_CHECK}`
         : `**When creating or editing components, read the system's GUIDE.md and follow it:** use only semantic tokens
 (\`var(--ds-color-semantic-*)\`, \`--ds-spacing-*\`, etc.), scope the UI with \`data-ds="<slug>"\`,
-and reuse the \`.ds-*\` classes. Do not use raw values outside the system's scale. **Before
-creating any UI element, check the component manifest below - if it exists, use or extend
-it (\`synthesisui component <slug> <name>\` materializes it as your code).** To review a
+and reuse the \`.ds-*\` classes. Do not use raw values outside the system's scale.
+
+**Before creating any UI element, look it up in the manifest below.** If something there
+already covers the purpose, do not write it from scratch - run
+
+    npx synthesisui@latest component <slug> <name>
+
+YOURSELF. It materializes that component as real typed code in this project, and you use and
+extend that. The person who asked you for a feature should never have to know these command
+names or type them; finding the right component is your job, not theirs.
+
+Only write something new when nothing in the manifest covers the purpose - and when you do,
+say which entry you considered and why it did not fit. To review a
 component, create an isolated sample page (e.g. \`app/synthesisui-samples/<component>/\`) - do not
-apply it to real production pages unless asked.`;
+apply it to real production pages unless asked.${SELF_CHECK}`;
     const body = `## Design Systems (via SynthesisUI)
 
 This project uses design system(s) tracked by the \`synthesisui\` CLI. ${rule}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "synthesisui",
-  "version": "0.15.0",
+  "version": "0.16.1",
   "description": "Bring SynthesisUI design systems into any project - tokens, typed components, whole pages and an agent-ready CLAUDE.md manifest.",
   "type": "module",
   "bin": {