synthesisui 0.16.73 → 0.16.74

package/dist/skill-import.js

@@ -134,6 +134,22 @@ Open the project and answer the questions below. Then add a \`reading\` object t
   "roles": { "canvas": "#050505", "foreground": "#f9fafb", "primary": "#4A90E2" },
   "fonts": { "display": "Inter", "body": "Inter" },
   "concept": "one paragraph on what this product is",
+  "rules": [
+    {
+      "text": "A RootWrapper is what makes the app-shell components position correctly - never render a Sidebar or Topbar outside one",
+      "applies": ["RootWrapper", "Sidebar"],
+      "kind": "implementation",
+      "files": 3,
+      "evidence": "all three app shells wrap them; none renders them loose"
+    },
+    {
+      "text": "MetricCard is only used inside a grid, never on its own",
+      "applies": ["MetricCard"],
+      "kind": "limit",
+      "files": 1,
+      "evidence": "one dashboard page; may just be how it happened"
+    }
+  ],
   "components": {
     "MetricCard": {
       "parts": [
@@ -175,6 +191,49 @@ 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.
 
+**\`rules\` - how this company BUILDS, which is half of what they actually made.**
+
+A design system that arrives as tokens and recipes is only the vocabulary. The other half is the
+grammar: that a wrapper exists so the thing inside it works, that state arrives through a
+particular hook, that a card is never used loose. That is how the developer already thinks, and
+writing it down is what makes it survive them.
+
+Two dimensions, and they are independent:
+
+\`\`\`
+applies  []       the whole system
+         [a]      that component
+         [a, b]   a RELATION - two components that only work together
+
+kind     limit           a boundary, which the doctor can measure
+         implementation  how it is built, which no linter checks and an agent
+                         must be told
+\`\`\`
+
+The relation is the valuable one. \`[RootWrapper, Sidebar]\` says something neither name says
+alone, and it is exactly what an agent needs in order not to assemble it wrongly.
+
+**Report \`files\` honestly - it decides whether the rule governs.** Three or more files is a
+habit and the rule arrives active; one file is a coincidence and it arrives as a candidate,
+inactive, waiting for the person to promote it. You do not make that call; you report the
+evidence and a threshold makes it. So a pattern you saw once should say \`"files": 1\` even when
+you are confident - being wrong about a law is worse than being slow about one.
+
+**Write \`evidence\` as what you actually saw.** "All three app shells wrap them; none renders
+them loose" lets somebody disagree with a fact. "Best practice" lets them disagree only with
+you.
+
+Things worth looking for, none of them guessable from tokens:
+
+- a wrapper or provider whose whole purpose is to make something else work
+- an environment law - "this is Next, so the state comes through this hook" - which travels
+  with the system and only applies where that environment is
+- a component that is never used alone, or never used outside something
+- an axis that is always passed the same way in one place and never in another
+
+If you cannot say where a rule came from, do not send it. An invented law is worse than a
+missing one, because it will be obeyed.
+
 **\`components[Name].parts\` - what each component is MADE OF.** This is the field that decides
 whether a component previews as itself or as a grey box with a sentence in it, and only you can
 fill it.

package/package.json

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