synthesisui 0.16.62 → 0.16.63

package/dist/skill-import.js

@@ -166,29 +166,107 @@ about which one is the page. Read a screen and see.
 **\`fonts\` and \`concept\`** - the voice, and one paragraph on what this product is. The concept
 feeds every recommendation downstream, so a real one beats a generic one by a wide margin.
 
-### 3. Confirm once, then send
+### 3. Walk them through the decisions, one at a time
 
-You have made three decisions on their behalf by now - **where** you measured, **what** it will
-be called, and **which values** carry which meaning. Put all three in one place and ask. Not a
-report that contains a question at the bottom: a question.
+Four decisions are theirs. **Ask them as separate questions with selectable options** - use your
+question tool, one call per decision, so they pick instead of reading a wall and composing a
+reply. A single block containing everything is a report, and a report gets read, not answered.
 
-Offer the alternatives you actually considered, so choosing is a choice and not a veto:
+Every question carries **your recommendation first, marked as such**, and the evidence for it in
+one line. They are choosing, not auditing you.
 
+**3a. Source** - the folder you measure the system out of.
+
+Options are the candidates the CLI already ranked, each with what it would produce, plus the
+whole repo, plus *somewhere else* for a path they type:
+
+\`\`\`
+Where should the system come from?
+
+  packages/ui (recommended)    114 files · 47% of its values already named ·
+                               92 tokens of their own · every app imports it
+  the whole repo               2797 files · 36% · the average of one dark app
+                               and two light ones, which is a diagnosis and
+                               not a system
+  apps/web-dashboard           the heaviest consumer, if you want one app's
+                               vocabulary rather than the shared one
+  somewhere else               a path you name
+\`\`\`
+
+If they name a path you cannot use, say which of the two it is and offer the list again:
+
+- **it does not exist**, or holds no files you can read
+- **it holds no design values** - no colours, no radii, no tokens. A folder of server code or
+  config is not a design system, and measuring it produces a system of nothing.
+
+**3b. Name** - suggest theirs, and let Enter take it:
+
+\`\`\`
+What should it be called?  (SignalUI)
+\`\`\`
+
+Say where the suggestion came from - \`Introduction.mdx\`, the package name, the folder. A name
+they recognise is worth more than a clever one. The slug is derived once and never changes, so
+this is the moment.
+
+**3c. Primary** - and explain the role before offering the choice, because *primary* is our word
+and not necessarily theirs:
+
+\`\`\`
+Primary is the colour that carries action - buttons, links, focus, the thing
+you want pressed. Everything else in the system is measured for contrast
+against it.
+
+  #059aed  ocean-500 (recommended)     your ColorPalette.mdx calls Ocean the
+                                       "Primary branding scale"
+  #1a4ed8  royal-blue-500              your docs label this one secondary
+  #ec4899  vivid-pink-500              half of your signature AI gradient
+  #4A90E2  blue-500                    the most-painted blue in the folder,
+                                       but it sits after your own
+                                       /* End - Signal UI */ marker
 \`\`\`
-I'd create a system from packages/ui, called SignalUI, opening dark.
 
-  from      packages/ui   114 files, 47% of its values already named
-            (apps/web-dashboard, apps/web-review and apps/web-admin
-             are the consumers; measuring all of them gave 36%, which
-             is the average of a light app and two dark ones)
-  called    SignalUI      their own name, from Introduction.mdx
-  brand     #059aed       their docs call Ocean the primary scale
-  opens     dark          data-theme="dark" in the root layout
+Always name the hex AND the token, and always give the reason a value is *not* recommended when
+frequency would have picked it. That last row is the whole point of asking.
 
-This creates it on your account. Go ahead, or change any of these?
+**3d. Default theme** - which face it opens in:
+
+\`\`\`
+  dark (recommended)   data-theme="dark" in the root layout, next-themes
+                       defaultTheme="dark", enableSystem={false}
+  light                the other one, also real here
+\`\`\`
+
+**Two is all there is** - a SynthesisUI system carries one palette and one alternate, and the
+schema is \`"light" | "dark"\`. So this is not "which themes do you support", it is "which one do
+docs and installs open in". If both are real, both get built from their own tokens; this picks
+the face.
+
+**3e. Canvas** - confirm, do not offer a list. The page is measured, not chosen:
+
+\`\`\`
+canvas  #222326  darkgray-500 - what DashboardLayout paints on <main>
+                 (your sidebar sits a step deeper at darkgray-700)
 \`\`\`
 
-Then, and only after they answer:
+Say it and let them object. Offering five near-blacks to pick between is asking someone to
+re-decide something their code already decided.
+
+**3f. Fonts** - do not ask at all. Report and move on:
+
+\`\`\`
+fonts   Figtree for both display and body - the only family declared
+        (--font-sans, and next/font Figtree in all three root layouts)
+\`\`\`
+
+If a project genuinely declares two families, say which is which and why you paired them that
+way. If it declares one, there is nothing to decide.
+
+**A note on colour swatches.** You cannot paint a hex in this conversation, so the token name
+carries the weight - \`ocean-500\` tells someone more than a square would. When they run
+\`npx synthesisui import\` themselves in a terminal, the CLI paints them.
+
+Then, and only after all four are answered:
 
 \`\`\`
 npx synthesisui import --census _synthesisui/census.json --name "<the name>" [--registry <from step 0>]
@@ -196,10 +274,11 @@ npx synthesisui import --census _synthesisui/census.json --name "<the name>" [--
 
 **This is the one real write.** Everything before it is on their disk and costs nothing to redo.
 
-The CLI asks for a name unless \`--name\` is passed, and it does **not** ask about the scheme when
-your reading already answered - a second question would only be a chance to contradict you. So
-if you skip the confirmation above, nobody is asked about the scope at all, and the first time
-they learn where their system came from is when they open it.
+Pass every answer explicitly - \`--name\`, \`--scope\` if they changed it, and the reading rewritten
+with their primary and their theme. The CLI cannot ask anything when you are the one running it:
+it has no terminal, so its own prompts are skipped by design. **Whatever you did not ask, nobody
+asked.** Skip 3a and the first time they learn where their system came from is when they open
+it.
 
 If it refuses, it says which of the three it is: no session, an expired one, or a token issued
 by a different host. All are recoverable from the census on disk; none need a re-measure.

package/package.json

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